Each scheduled tool shows its last run, how it went and its next run, on Settings › Features and in the features tool #10050

For: the owner sees that a feature's schedule is alive without opening logs. The scheduler it reads is on main: src/apps/feature_schedule.ts and the fire record from migration 20261109050000-feature-fire.

Done when:

• [ ] On Settings › Features, an absorbed app with a schedule shows one line per entry, like scan every 1h · last 10:02, ok · next 11:02, or the error's sentence when it failed. The line uses the page's existing row and the time() clock, reads the stored fire record, and adds no new class.
• [ ] The features MCP tool with slug returns schedule: [{ tool, every, lastAt, ok, error, nextAt }], with nextAt from due's rule. The terminal's Features palette entry shows the same line.
• [ ] docs/features/absorb.md no longer lists the schedule under 'Not done yet', and 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, and test/mcp-size.test.ts ceilings are not raised.

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

This replaces #9927 and has nothing in front of it. The work it reads (src/apps/feature_schedule.ts and the feature-fire migration) is on main. The map still shows it as parked because #9926 was dropped, and neither a new title nor a new body clears that. A person can lift the park, and then it is ready to start.

Split into #10200 (Settings › Features line) and #10201 (MCP tool and terminal, after the page's shared function).