trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Home's spend tile shows the forge's own ceiling and the time it was hit, and the terminal dashboard says the same
- A pull's opened, reviewed and merged posts fold into one timeline post that shows its latest state
- The owner's `/` answers under 300 ms warm on a forge with 200 repositories and 100 open asks, every phase named
- Sentinel: disk-red was degraded 18 minutes today: The check machine's disk was full when 8 checks failed: 10% free, under the 10% floor — the machine's red, not the pull…
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:ky51wt3erj is past its budget: trevato/forge: "tools/list stays under 40 KB, with 3 KB of headroom (37,000 bytes)" failed on 4 pulls in the last hour …
- A repository's title is named in a new docs/design/areas/repo-head.md, and .repo-title leaves §5d
- The front page's admin controls are named in a new docs/design/areas/front.md, and .front-admin and .front-pick leave §5d
- The OpenAPI document describes a repository's milestones, reports, commits and a pull's reviews
- A note's status says "Shipped in <release>", or "Shipped on <date>" until a release includes it
- The Apps card links each app to its page on the forge, and its production URL when it has one
- The OpenAPI document describes an issue's and pull's assignee, an issue's labels, teams and dependencies, and making an issue private
- The OpenAPI document describes making and deleting a repository, its branches, and listing and committing contents
- A repository's map page names its Server-Timing phases, and `/alice/forge/map` leaves the sweep's UNNAMED list
- The OpenAPI document describes editing a pull and approving it here
- The home's timeline list is named in docs/design/areas/feed.md, and .feed leaves §5d
- `bun scripts/home-read.ts <url>` prints a page as the eye reads it, with its characters, words and fetch time, so the #5735 cold read starts from the same text every time
- The Working-now card links each run to its log on the forge
- MCP `backups`: where snapshots go and the last ones taken, for a forge admin
- The OpenAPI document describes a repository's waves: the list and one wave
- The Wave card links each milestone limb to its page on the forge
new above
offline