trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The flow vitals carry gate minutes and the red-batch rate, and a rate over 30% is named as a miss
- A repository's description wears §5's muted small text, and `.repo-desc` leaves the stylesheet
- A test pins the terminal's aligned columns: `drawRows` lines up, drops and never shrinks below `min`
- A test pins `readReturns`' refusals: a bad window, no viewer, and a repository the viewer may not read are refused the same way a missing one is
- A test pins that ref links never smuggle a path: `pathCrumbs` and `refMenu` encode refs and escape names
- A test pins what a person's attached look accepts: `readImage` and `cleanNote` at their edges
- The crew's one-line reasons are cut with `clip`: a parked reason ending in an emoji keeps it whole
- A test pins which app environment names are accepted and which are reserved
- `.menu-item` is a named part of the menu, and leaves the §5d list of page-local classes
- A test pins that a fleet operation is undone at most once: `claimUndo` and `releaseUndo`
- A check's summary, test row and error line are cut with `clip`, so a failing test named with an emoji reads whole
- A test pins `validCapacity` and `isCapacityKey`: a capacity setting takes only what its kind allows
- The home's "What you asked for" bar leaves: the Asked tab is the one door to /asked
- A test pins `navigationBranch`, the release smoke's read of the service worker's navigate branch
- "Since you were here" also lists releases, failed checks, and private repositories the viewer can read
- The terminal dashboard and MCP `feed` show the same three digest lines as home
- P0: the merge queue records and names the tests that failed each gate (not just the count), with a gates API, so a red batch can be acted on
- 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)
- 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
- Public page defects for guests: /flow redirects to a /boards 404, doubled forge title suffix, JSON 404 on the releases page, slow openapi.json
- 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
- 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
new above
offline