trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A pull serves flow when its issue carries the `flow` label, not only when it is on a hard-coded list
- Terminal: open the private repository a writer fixes a sealed report in
- The OpenAPI document describes accepting and dismissing a report, confirming a wait, a milestone's limb and proposal tokens
- A repository's runs page filters by state: `?state=failed` lists only failed runs, under a row of state links
- Each line of a repository's waves list says the wave's date: `0.7.12 · 2026-10-20 · headline · 4 pulls`
- A pure read says the median hours from a crew pull's opening to its first review verdict, over the last 24 hours
- Sentinel: Crew runs in trevato/forge keep failing at the push or the sandbox
- A pure read counts the issues the crew parked in the last 24 hours and 7 days, and names the newest three
- One test proves every flow read with `publicOnly` hides a private repository
- A pure read lists open crew pulls with no push for 72 hours, oldest first
- A pure read sorts the open crew pulls into one count per state: red, conflicted, changes asked, approved and waiting, awaiting review
- A pure read says the crew's build yield over 24 hours: build runs finished, how many pushed, and how many of those pulls landed
- An issue body's `Files:` line, when present, is the only list of files the hot-file hold reads
- CI lockups: main can never silently go red (pre-push check + auto-revert), bisect by halves, reserved gate capacity, every red names its test, gate logs kept
- The picker uses the governor's slots, and the feed and tick line say when it lowers them
- Home's "N waiting on you" counts exactly the rows /review lists, and asks older than 30 days fold into "N stale, archive?"
- The app's terminal prints production's address and the newest open preview, gated like the pill
- A connected account's repository picker leaves origins.ts for src/web/pages/origin-repos.ts
- A reviewed-pull post says the verdict, approved or changes asked, and the reviewer's first sentence
- The crew settings page and its forms leave settings.ts for src/web/pages/crew-settings.ts
- /llms.txt lists every MCP tool from the generated tool index, and a test fails when one is missing
- A fired flow alarm is one line at the top of home and on /boards, with one notification to the owner
- The inbox's decision forms leave asks.ts for src/web/studio/decisions.ts
- A red merge batch is searched by disjoint halves, never by nested prefixes holding the same suspects
new above
offline