trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1z027gr9t2 is past its budget: trevato/forge: "image blob pages > a PNG's header size reserves the box before the bytes arrive" failed on 3 pulls in t…
- A tick starts one builder run per free slot, not one issue per tick
- A Deploy to… page and link for a pinned forge (follow-up to #8697)
- A red that main passes is the pulls' own: no sentinel issue a builder can only decline
- A crew run's state is worked out from what it did: silence shows, and a plan says where it is
- Pinned forge: canary deploy on a real DigitalOcean account in under 10 minutes (follow-up to #8697)
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1vuo2hdxpt is past its budget: trevato/forge: "the flow report counts stale reds and the keeper names them as a cause" failed on 3 pulls in the last h…
- Crew briefs point at docs/PRINCIPLES.md instead of restating it
- The signup Email hint reads plainly: “Optional. If you add one, we send a link to confirm it.”
- A /talk conversation resumes its own session across a real forge restart
- design-lint holds the quiet-page rules a machine can check, so new pages get them
- The crew's now list says the reviewer is paused when its seat is set to 0, not that there is no reviewer
- Finish the crew settings review: file holds, team dials and subscriptions each kept, folded or deleted
- Bets: the owner backs a few named wholes with a share of the week, and the crew finishes them
- Drop the flow_only column and the flow_only_watch table: nothing reads them since d34910d4
- freePort copies in src/snapshot/boot.ts and src/release/boot.ts race the same way as apps/process.ts did
- Flow: the week's budget as pipes I can see and turn, and the system does exactly that
- A box pass on an already merged pull reviews the merge's own diff, never “(no diff available)”
- The reviewer seat's cap is proven end to end: at 1, a second agent pull waits until the first review ends
- Revert "The no_release alarm fires on any repository's oldest merge, so it always claims nothing has gone live"
- Pulls closed as already on the base before 4e481725 stop counting as landed in the vitals and home KPIs
- Home's Now line and the account menu's Repositories go where they say
new above
offline