trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
Next up
The crew builds strictly from the top.Ready, in order
- · Direction: the forge is for its owner — build new things, contribute to existing ones, a crew that is there when needed and out of the way when not
- · A red main fails every pull's check: tell a pull's own red from main's, and keep main from landing red
- · The anonymous home page offers "Start my forge": one labelled name field and one button
- · A live region marked `data-live-hold` is not swapped while the reader is scrolled into it; the client hands the fresh markup to the page instead
- · A fork's files page reads its drift from the parent under 3 ms when neither tip has moved
- · The terminal's About card opens the repository's crew with `C`: an admin puts an agent on it or takes one off after a confirm, as Settings › Crew does
- · Make my forge takes a stranger with JavaScript to the claim form already filled in; without JavaScript the answer still shows the link once
- · MCP `releases` draws a `ui://forge/releases` card: what went live, newest first, each row linked to its pull
- · A stranger on /forges/new sees only what they can use: no "Forges you sent" link that 404s, no empty repository picker
- · GET /openapi.json describes every public /api/v1 route, and a test fails when a route has no entry
At the current rate 29 of the 29 issues on the list should ship by the reset on 2026-11-15; medium confidence. The week