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:2tt6qpm3j9 is past its budget: trevato/forge: "flow panel cache > an agent never sees an admin's figures" failed on 4 pulls in the last hour — the lan…
- A test pins the forge's own share card at /og/site.svg: an SVG with the security headers, and the forge's name escaped
- /llms.txt folds public forks under their root, counting only forks a stranger can see
- A test pins removing a secret from Settings: a forge admin only, same-origin only, and the value never echoed
- A test pins giving a hand-over back to the crew over the API: a writer's, with a read-write token
- A test pins "Test" and "Bring level now" on Settings → Backups: a forge without a mirror says so, and only an admin may press them
- A test pins saving and clearing the sealed backup mirror from Settings → Backups, a forge admin's only
- The flags a forge admin sees on /settings/flags are one plain-data read: name, why, default, owning issue, live value
- Builder routing: rebases go to a builder who can't push (0/5 ok), and the picker sends 23 of 23 picks to Scout (5 slots run 1 builder)
- A repository's report routes leave api.ts for src/http/api/reports.ts
- MCP `pins`: list, pin and unpin the caller's pinned repositories, with the same rules as the API
- MCP `here` takes an app URL and answers what its /__forge/ door shows: app, environment, pull, who is working, and the links home
- MCP `sync`: sync a mirror now, or reconnect its origin, with the same rules as the API
- Issues one author opens within two minutes fold into one feed post: "planned 10 issues in trevato/forge", each one a line under it
- Home's builders tile says why builders are idle: the ceiling, no ready issue, or no subscription with headroom
- A repository's following routes leave api.ts for src/http/api/following.ts
- The terminal's Flow screen reads the same panel cache as /boards
- A test pins the terminal's history: the log pages through a real "load more" row, and a commit opens its diff
- A test pins the terminal's file finder: every file in the revision, one read, and the query narrows it
- MCP `hooks` and `repo_labels` should page like the routes they mirror
- The flow panel's figures come from one short-lived cache, so a second /boards load inside 30 s runs none of its reads
- A test pins opening a pull from the terminal: a fork's base defaults to its parent
new above
offline