trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- /llms.txt is token-efficient for a stranger: the 170-line MCP tool list is folded to what they can use, plus one line for the rest
- A shared-red sentinel issue names the pulls that failed the test and quotes the failure, so a builder can reproduce it
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:38g10d7hu5 was degraded 49 minutes today: trevato/forge: "the walked repository pages exist" failed on 3 pulls in the last hour — the lane's red, not theirs; the…
- Every app host answers GET /__forge/toolbar-<hash>.js with the forge pill's script
- MCP `preview` says whether the environment is serving: running, starting, failed with its error, not running or gone
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:6ryojgfus8 is past its budget: trevato/forge: "the proxy adds under 5 ms (median) and 20 ms (p95) with the toolbar rewrite" failed on 7 pulls in the l…
- A proxied page's Server-Timing says where forge-upstream went: connect, first byte and body
- test/render-media.test.ts is never red on a pull whose diff it does not touch
- An admin sets the repository's description from the terminal's About card with `w`, as Settings does
- An admin pauses and resumes a webhook from the terminal's webhook list with `p`, and a paused hook gets no deliveries
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1qxrcl4xqv is past its budget: trevato/forge: "the forge over MCP > map and wait_for are the plan's own actions" failed on 4 pulls in the last hour — …
- A resumed turn of the forge's agent does not repeat a write that finished unreported
- A turn of the forge's agent runs in an empty directory of its own, not the data dir
- The feed, the pulls list and the TUI say check, review, land or live for each pull
- Measure each step of the path: time and red rate, posted as the map in #7703
- A check result already proven for the same tree is reused, not rerun
- A crash outside any test re-runs that shard alone once before it can fail a check
- The full suite runs as a scheduled report that files what it finds and never blocks a landing
- A red pull never sits: the forge reworks or closes it, and it stops holding its issue
new above
offline