trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
LaterP0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP2 ExplorerP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suiteoutsidered-only-in-full-suite
- README is 300 bytes from its 60 KB budget, so every README addition turns its pull red: move Develop and What works today into docs/ (target 45 KB) Later
- Public page defects for guests: /flow redirects to a /boards 404, doubled forge title suffix, JSON 404 on the releases page, slow openapi.json Later
- releases.json misses the tag-based releases 0.7.272 to 0.7.274, so standings and the behind watch can't see new releases Later
- During a rollout an app's host briefly serves forge pages (title forge, forge 404s) beside the app; app hosts must never fall through to the forge router Later
- A rollout must not turn in-flight gates red: an interrupted gate re-runs as the same candidate, and red (check) retries once before bisecting Later
- A test pins leave-to-run: a grant names one head, a new push waits for a new grant, and a grant is never a review P0 Trust
- A test pins `previewOf`, the answer behind MCP `preview`: a preview host names its pull, check and first failure, and anything else is refused plainly P6 Never lost
- A test pins `mergeForCheck`: the check runs on the merge with today's base, in the pull's own repository, and a conflict is said as the change's fault P0 Trust
- A test pins that a thought is read back only by its author: newest first, `since` respected, text exactly as kept P7 Steering
- A test pins which pulls wait on "changes requested": the newest crew verdict on any head, never an origin's imported review P0 Trust
- A test pins the rate limiter's sliding window: no double burst across a minute boundary, refused requests not counted, admin allowance and the off switch P0 Trust
- "Since you were here" also lists releases, failed checks, and private repositories the viewer can read P1 Feed
- Land "Since you were here" from pull #6684's branch, with its duplicate `pull_merged` index taken out P1 Feed
- A test pins `revertCommit`: undoing a shipped commit keeps later changes, reports a real conflict, and refuses a merge commit with two parents P0 Trust
- A test pins which finished runs the feed folds as quiet: nothing pushed, opened or said in the run's window, and never a run the record cannot find P1 Feed
- A test pins the forge's daily crew ceiling: no cap, under, exactly at, and which run carried spend across it P0 Trust
- A test pins a repository's events page: hidden events never shift a page, and a mostly hidden outbox comes back short with a cursor that resumes P5 Open to every agent
- A test flips pulls, user standing and the front page's weights and finds the explorer's rank-inputs hash follows each P2 Explorer
- A test pins `reviewStats`: green crew pulls awaiting a verdict, the median wait for one, and verdicts per reviewer in the window P0 Trust
- A test pins `readConflictedFiles`: diff3 markers from a real two-sided change, one merge for many paths, and nothing for a clean or missing path P3 Fork tree
- A test pins `Stamped`, the memo every cached page reads through: stamp change, max age and least-recently-used eviction P0 Trust
- Posts that arrive live while you read wait behind one "N new posts" button at the top of the home timeline P1 Feed
- A live region marked `data-live-hold` is not swapped while the reader is scrolled into it; the client hands the fresh markup to the page instead P1 Feed
- src/web/studio/held_posts.ts: pure reads of which live posts are new and what the button says P1 Feed
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1jysrp6ra0 is past its budget: trevato/forge: "readPlan of 2,000 closed and 300 open issues under 10 pillars fits a 30 ms budget" failed on 4 pulls in… P0 Trust
new above
offline