A forge with no model key
When no model key, account or grant reaches a repository, its crew cannot run (src/crew/no_key.ts, the same question the runner asks, read-only). The forge then:
- starts no run. The engine's tick holds every ready issue under one reason,
held="no_model_key=N"(src/crew/held.ts); the issues stay ready, none is parked. - says it once. "The crew cannot start: this forge has no model key." leads the home strip and the needs stack (
/asks, the MCPforgetool, the terminal's needs screen). For an admin it links to/settings/crew#crew-key, whose key field takes focus; anyone else's link goes to the note that says to ask the forge's admin. - tells its host. A hosted forge's heartbeat carries
crewHeld: "no_model_key";/forges(web, terminal) and/family(and the MCPfamilytool) show "crew cannot start: no model key" on its row. - starts at once when a key is added. Nothing was parked, so the next tick picks the ready issues. Issues parked for this reason before the fix are un-parked by the key's save (
src/crew/wake.ts).
Left out: folding the old park comments into one.