trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
P13 Maintainers
26 of 30 done
4 open · 23 merged in 7 days · moved
About 2 days at this week's pace: 24 closed in 7 days, 4 open.
Limbs
Blocked
Merged in 7 days
- /flow says in one sentence what is clogging the lane, and names a failing test shared by three pulls
- The crew page says in one line what the slot governor last did and why
- /flow shows hand-overs to a person in the last day, pulls one review round away from one, and the five pulls to rebase first
22 more merged
- MCP system {kind:"routes"} answers the slowest routes against their budgets, as the performance watcher sees them
- Route p95 per hour is kept for seven days, so a slow week can be told from a slow minute
- /flow lists approved pulls waiting on the merge queue, stale crew pulls to fold back, and work a crew fork never proposed
- small: the unreached audit names the two files that are entries by design, and the allow list shrinks by two
- A maintenance duty stops at its budget, runs per day and dollars per day, and its last run row says it stopped there
- A maintenance duty pauses and resumes from the board and over the API, and pauses itself after three errors in a row, saying why
- Rule watcher: gate-only reds, rule breakers with exact fixes, flaky and load-sensitive budget tests
- Flow keeper: stuck, conflicted and wrongly held pulls, rebase loops, lulls and forge-down, acted on instead of alarmed
- Batch doctor: on a red merge batch, find the culprit, tell load reds from real ones, hold with the exact failing test
- A maintenance duty registered in one file runs on its interval and leaves a maintenance_run row with its findings and the probe behind each
- The crew has a maintainer role: an agent can be made one, the crew page names it, and it has no path to merge or push main
- /maintenance shows, for each duty, when it last ran and what it found, in one line each
- A nightly off-box backup older than 26 hours is a card on /flow with the one action that retries it
- `flow` brings a drifting pull up to date with one action, once the drift list is on main
- A pull drifting far behind main is flagged on /flow with the one action that rebases it
- `system` over MCP names the last hour's main-thread stalls and the route or job behind each
- A park note says what each failed try of the pull changed
- Boards can chart the machine: CPU, memory and load as a source
- /flow says how many crew runs declined in the last day, and why
- The machines page shows one quiet line per disk, with the rated figures on open
- Disk readings are kept per machine, with a 30-day write rate and a projected date for rated TBW
- Disk health rules: a spec catalog and alerts only on what the drive itself reports