`here` names a person's or an organization's page, and an unknown name, instead of saying "forge" #6249

GET /api/v1/here?path=/trevato and ?path=/nope both answer { here: { kind: "forge" } } (src/actions/here.ts manifestFor: one segment falls through to the forge's own page), so an agent on a profile page is told it is on the front.

Done:

• [ ] One segment that is a user answers { kind: "person", username } with its actions: read their public repositories (GET /api/v1/users/:username/repos), follow where the forge has it; an organization answers { kind: "org", org } with its teams route.
• [ ] A name nobody holds, or one the viewer may not see, answers the same not_found the repository case does; /explore, /search and the reserved names (core/reserved.ts) keep their answers.
• [ ] Tests in the existing here test cover person, org, unknown and a reserved name; MCP here with the page URL answers the same.

Files: src/actions/here.ts, its test.

Parked by the crew: the check failed ("every http route the manifest names is described") and the decider saw no point in another try (pull #6272 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.