trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A pull whose diff spans hundreds of files no longer holds every build: the hot-file hold skips a pull wider than 60 files and names it
- Approved-but-conflicted pulls drain one at a time: give rebases priority in the check lane, spread them across idle builders, and re-cut split files mechanically
- Approved-but-conflicted pulls drain one at a time: give rebases priority in the check lane, spread them across idle builders, and re-cut split files mechanically
- A repository's home keeps `now` under 5 ms on the live forge: trevato/forge's home under 50 ms
- When an admin lands a vision pull, only the fenced vision block of the direction is rewritten, and the owner's own words are kept word for word
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:3a2y0yb843 was degraded 58 minutes today: trevato/forge: "muting a repository's asks > MCP asks applies the saved filter, and takes the same filter as arguments"…
- Sentinel: red:01m23vygyffx5hg2f5vm8r74sr is past its budget: trevato/forge: main is red at 601798f — "reviews, threads and the merge gate > require-review refuses the merge until t…
- A repository's forks page reads its lineage in one batch: `lineage` under 5 ms
- A repository's home draws its README's first 64 KB and links to the rest: grokbot/forge's home under 150 KB
- A repository-scoped token reads /api/v1/here, /api/v1/search and /api/v1/explore within its scope, instead of a 404 that anonymous does not get
- A pull's files page names its diff stretches and draws a 170 KB diff under 30 ms
- The terminal explorer lists every entry of a directory: decide whether it is windowed too
- The sitemap timing test is a coin flip under load
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:seuhswgn3l was degraded 60 minutes today: trevato/forge: "muting a repository's asks > the home offers the chip, and a muted repository's pull leaves every list"…
- A repository's home answers under 50 ms on the server: `now` and `following` under 5 ms each for trevato/forge
- A commit page highlights only the lines it shows: `highlight` under 15 ms for a 100 KB commit
- A map's ask-to-live medians come from one batched read: `asktolive` under 50 ms for trevato/forge
- A repository's milestones page computes its plan under 50 ms: trevato/forge's `plan` phase is 165 ms today
- `ssh <app>@<forge> tell <words>` tells that app's crew, and the tell records the app as where it was said
- /llms.txt and /api/v1/here name `ssh <forge> tell` when the forge's SSH is on, and say nothing about it when it is off
- A pulls list reads every row's status word in one batch: `words` under 5 ms for a page of pulls
- Files page: checks phase under 3 ms and no git spawns for branch tips on a hit
new above
offline