The hollow work check counts only callers that run: an action called from a page function no route names is hollow #739

Pillar: P0 Trust (umbrella #586). One small pull, follows #615 (merged as #681). Found in its review.

Outcome (what a person sees). Nothing changes on the page. The hollow work check stops counting a caller nobody can reach: an action called only from a page function that no route names is hollow, and the gate says so.

Today. scripts/hollow.ts starts reach at every declaration under src/http, src/web, src/crew, src/cli and src/tui. A function in src/web/pages that no route registers is such a declaration, so an action only it calls passes.

Acceptance.

• [ ] Reach starts at what runs: each module's own top-level statements (src/main.ts, the CLI and terminal mains, the hook entry), and follows names from there, so a route's handler is reached through the table that registers it, an MCP tool through the tool list, the crew through its dispatch.
• [ ] Tests: an action called only from an unrouted function under src/web/pages is named; the same action is not named once a route registered from the entry point names that function; a route table nothing calls reaches nothing.
• [ ] On today's main the audit names nothing beyond the allow-list (measured on 1e4ebce: it does not), or each new name is fixed or allowed under an issue.
• [ ] The messages and the docs say "nothing that runs reaches it" in place of the five directories.

Done means reachable

• Page: does not apply
• API or MCP: does not apply; the check is bun scripts/hollow.ts and test/hollow.test.ts
• Test: above
• Look: does not apply

Start from: scripts/hollow.ts (hollowActions), test/hollow.test.ts.

Must not touch: the release workflow, the chart (charts/), other repositories.