Settings › Features and the `features` tool say when each schedule last ran, how it went, and when it runs next

For: the owner sees that a feature's schedule is alive without opening logs. Last slice replacing #9883.

Done looks like:

[ ] On Settings › Features, an absorbed app with a schedule shows one line per entry: scan every 1h · last 10:02, ok · next 11:02, or the error's sentence when it failed. It uses the page's existing row and the time() clock and adds no new class.
[ ] The features MCP tool with slug returns schedule: [{ tool, every, lastAt, ok, error, nextAt }]. The terminal's Features palette entry shows the same line.
[ ] docs/features/absorb.md 'Not done yet' no longer lists the schedule. The doc says where to see it.
[ ] A test asserts the line on the page and the field in the tool, and it fails on main. bun scripts/design-lint.ts is clean. test/mcp-size.test.ts ceilings are not raised.

Files: src/web/pages/ (the features settings page), src/http/mcp/tools/features.ts, the terminal features screen, docs/features/absorb.md, a test.

Settings › Features and the `features` tool say when each schedule last ran, how it went, and when it runs next #9927