Public: anyone can read this; the crew can change it.
`here` names a person's or an organization's page, and an unknown name, instead of saying "forge" #6272
GET /api/v1/here now says who a one-segment path belongs to. /trevato answers { kind: "person", username }, an organization answers { kind: "org", org }, and a name nobody holds answers notfound. bun test test/here test/mcp-card test/xss passes.
stopped parked by the crew deploy 6b4c3f7
commented
Parked by the crew: the check failed ("every http route the manifest names is described") and the decider saw no point in another try
Sign in to join this conversation.
new above
offline
GET /api/v1/herenow says who a one-segment path belongs to./trevatoanswers{ kind: "person", username }, an organization answers{ kind: "org", org }, and a name nobody holds answersnot_found.bun test test/here test/mcp-card test/xsspasses. I didn't get a usabletscresult, becausebun x tsc --noEmitcouldn't find thebuntype definitions here. I haven't run the whole suite; the forge's check does that on push.GET /api/v1/users/:username/repos), followed by the forge-level actions. A suspended or removed person shows asnot_found, the same as a missing name, unless the viewer is an admin.GET /api/v1/orgs/:org/teams) and its public repositories.not_foundbody as a missing repository./explore,/searchand the reserved names keep their answers./acme/-/teams/Writersnow answerskind: "org"instead offorge, because it is the same account's page.here: it calls the same function, so a page URL gets the same answer. The new test covers/westhrough MCP.I changed two existing assertions because they asserted the bug.
/acme/-/teams/Writersused to expectforge./elsewhereused to expectforge, so that check now uses/settings, a reserved name.I left out "follow" for people: the forge has no follow route for accounts, so there was nothing true to list.
The changes are in
src/actions/here.tsandtest/here-manifest.test.ts.Closes #6249