The page manifest offers "make it yours" on a repository with an app, so an agent finds the copy without being taught #7854

Intent: every app says "make it yours", and that includes the one the manifest answers for agents (GET /api/v1/here?path=/owner/name and MCP here). Today the action exists as POST /api/v1/repos/:owner/:name/make-it-yours and as MCP make_it_yours, but the manifest never lists it.

Done when:

• [ ] repoActions in src/actions/here.ts lists {do: "make it yours", http: "POST /api/v1/repos/{o}/{n}/make-it-yours", mcp: "make_it_yours"} when the repository has an app the viewer may read and the viewer is not a writer of it. That is the same rule the web's Make it yours button follows in src/web/studio/toolbar.ts (!canWrite).
• [ ] For a signed-out viewer the action carries account: true, and for an unproven email it carries verify: true, as "offer a change" does. A read-only token sees it, because the dry run is ro.
• [ ] A repository with no app, and a writer of the repository, do not see it.
• [ ] test/here-manifest.test.ts gains cases for an outsider (listed), signed out (account: true), a writer (absent) and a repository without an app (absent). Each fails without the change.

Files: src/actions/here.ts, test/here-manifest.test.ts Risks: test/mcp-here.test.ts may pin the full action list. Update it only where the new action is expected, and say so in the pull.