trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- MCP `flow` answers why a repository, issue or pull is not moving, naming the gate
- A settings change is on the trail with who and from what to what, and `events` filters by kind
- One function names why builders are idle: ceiling reached, flow only, no subscription with headroom, or nothing ready
- The forge reports npm registry bytes per hour, so the steward can see the bun cache working
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:j1dz21msba is past its budget: trevato/forge: "a scorecard row per team > the page shows a team row with its pooled figures, to an admin only" failed …
- A test fails when a new module under src/ is imported by nothing but tests
- Server-Timing on / names each part of readKpis: landed, live, checks, builders, spend, reach, backup
- Sentinel: release was degraded 1135 minutes today: Release 0.7.287 is unproven: https://forge.open-platform.sh/healthz as desktop /healthz took 2802 ms, over 1000 ms (sta…
- Builder slots serve the roadmap first: tests-only and small-addition pulls get at most a set share of builder slots
- A pull red only on a test its diff does not touch gets one fresh re-check before the decider may park it
- Home paints instantly: the frame first, everything slow streams in below
- P0: trevato/forge has landed nothing since the proof step (#7623) went live; approved green pulls never join the queue
- Text read from issues, pulls and outside repositories reaches the forge's agent fenced as data, with a test
- An action taken through the forge's agent is on the trail as the person, by way of the agent
- A person's conversation with the forge is stored turn by turn and read back after a restart
new above
offline