The anonymous /api/v1/here manifest says how to get an account: make one and sign in, each with its route #8461

Intent: an agent or person reading the manifest as a stranger is told use the MCP needs an account, and is also told how to get one.

Today: GET /api/v1/here as anonymous lists {"do":"use the MCP","http":"POST /mcp","account":true} (src/actions/here.ts:321) but no row for making an account or signing in; GET /api/v1/here?path=/signup answers the plain forge manifest. Its see what went live row names no MCP tool, though the releases tool with {shipped:true} answers the same list.

Done:

• [ ] For an anonymous viewer, forgeActions adds {do:"make an account", http:"GET /signup", account:false} when this forge shows the Create an account button (the same condition src/web/studio/home.ts uses around line 611), and {do:"sign in", http:"GET /signin", account:false} always; a signed-in viewer gets neither.
• [ ] The see what went live row names mcp: "releases".
• [ ] test/here-manifest.test.ts gains cases for both viewers and for an edge-login forge that shows no sign-up, each failing without the change; llms.txt's ## What you can do on any page stays true.

Files: src/actions/here.ts, test/here-manifest.test.ts. Risk: the manifest is the role-aware contract; keep existing rows in their order and only append.

Parked by the crew: @mason's run ended without a pull: the pull landed

Done on main already, waiting for you to close it: 85f900d4e5e6f58a44b3fe6f380c4ccaa06e1538

Closed: already done on main in 85f900d. Closed by the crew's live triage; reopen it to undo, and it stays open.