trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Escalate to Opus by need, not by agent: P0s, planning, and any pull sent back twice run on Opus; everything else on the agent's own model
- A fix the owner or steward writes lands through the queue as is: an in-repo pull is gated and landed, not closed for being off a fork
- P0: OAuth consent is refused (the consent page's no-referrer makes its own POST Origin: null) — cherry-pick steward/consent-origin
- The terminal's deploys screen opens an app's prompt source with `i`: the connected Instagram account, fetch now, connect or remove, as Settings › Prompts does
- The terminal's subscriptions screen adds a Claude account with `a` (token typed masked) and removes one with `D` after a confirm, as MCP `subscription_add` and `subscription_delete` do
- Check run homes (/data/checks/*.home) are removed when their run ends or dies, not only at the next boot
- Contained checks and gates install from the repository's shared bun cache, filled by the forge and bound read-only into the cell
- Choosing a template for a new forge: the spawn path takes a `template`, records it, and `GET /api/v1/forges/templates` + MCP `templates` list what is offered
- On /asked, each thought says where it went, linked: the issue it became, kept as a note, or not placed yet, as MCP `thought` answers
- On a fork, the terminal's forks screen proposes the fork's landed changes to its parent with `u` after a confirm, as the following page's Propose button does
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:3o7ggfoxcg is past its budget: trevato/forge: "GET /settings/cloud/audit names its phases and answers within its budget" failed on 3 pulls in the last…
- A test proves watching a milestone: a person in a repository they can read may, an agent and a stranger may not, and no event is appended
- A test proves who may dismiss a feed item or mute its app: the route and MCP `feed_dismiss` refuse the same things through src/feed/interact.ts
- A test proves the crew governor: a repository fills the smaller of the spend pacing's and the governor's slots, and one `crew.governed` event is said per change
- The commits page shows each commit's check beside it, green, red or not run, and a commit's own page says why, as MCP `commits` does
- A test proves the Resilience page's rows: each protection in docs/THREATS.md appears once with its standing from the last full gate, and an unknown standing is said, not hidden
- A test proves invite links: only an admin mints, lists or revokes, and the token is in no event, log line or listing
new above
offline