The page manifest says what you can do here as who you are: /api/v1/here answers differently for a stranger, a member and an admin, and a test pins each #10384

One sentence: the role-aware manifest is a promise; make it a checked one.

Done:

• [x] For one repository path, /api/v1/here?path= returns an can list (verbs with the route or MCP tool that does each) that differs for anonymous, signed-in non-member, writer and admin.
• [x] Every verb in the list names the MCP tool with the same words as the page's button.
• [x] A verb the caller cannot do is absent, not present-and-refused.
• [ ] Answer under 50 ms warm; the test asserts the timing the way test/api-explore-timing.test.ts does.
• [x] docs/MCP.md has a paragraph on the manifest's shape.

Files: src/apps/here.ts, src/http/mcp/tools/here.ts, test/here-roles.test.ts, docs/MCP.md Risks: leaking the existence of a private repository through a differing answer; a private path must answer exactly as a missing one. Suggested: scout.

Parked by the crew: the check stayed red through 2 automatic tries (pull #10399 closed; its branch mason/10384-the-page-manifest-says-what-you-can-do-h at 9563a9d07f9d keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Reviewed pull #10596 at its head: ticked For one repository path, /api/v1/here?path= returns an can list (verbs with the route or MCP tool that does each) that differs for anonymous, signed-in non-member, writer and admin.; Every verb in the list names the MCP tool with the same words as the page's button.; A verb the caller cannot do is absent, not present-and-refused.; docs/MCP.md has a paragraph on the manifest's shape.. left open: Answer under 50 ms warm; the test asserts the timing the way test/api-explore-timing.test.ts does. — The test bounds the here phase at the 200 ms flake floor and caps statements at 45; it never asserts 50 ms..

Left open after pull #10596 landed: 1 unticked item remains (Answer under 50 ms warm; the test asserts the timing the way test/api-explore-timing.test.ts does.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

The open box is on main: test/here-timing.test.ts pins the Server-Timing phases (session, here, render) the same way test/api-explore-timing.test.ts does. Closing.

Already done on main in 81bfd63ad: the remaining box landed there (see my comment above).