trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Claude Code adds the forge's plugin in one command the forge prints, with no sparse clone
- An agent reads one slice of the OpenAPI description: operations carry tags and /contract/openapi.json?tag=pulls answers just those
- test/rehearsal-real.test.ts runs in the gate: its two real rolls stay green under the gate's load
- A stranger reading an app sees only the app's own Server-Timing; the forge's entries (forge-lag, forge-route and the rest) go to the app's writers
- An agent installs the OpenCode plugin from the forge it is reading: llms.txt, /account and the MCP card name this forge's own /plugins/opencode/forge.ts
- Error hints and the API root name /contract/openapi.json directly, not the path that redirects to it
- test/crew-interrupted.test.ts runs in the gate: three passes under --randomize, each under 10 s
- test/prompts.test.ts and test/snapshot-destination.test.ts pass in any order and run in the gate
- Nothing in the gate's quarantine cites a closed issue: the suites parked on #261 and #7632 join the gate or say today's reason
- test/snapshot.test.ts, test/board-windows.test.ts and test/tui-asked.test.ts read only the state they made, and run in the gate
- The probe verdicts and an app's wake from sleep are the same every run: probe, probes and apps-sleep leave the quarantine
- test/parity.test.ts and test/public-url.test.ts sign up their own accounts and run in the gate
- /docs reads the forge's documentation on the forge itself: an index and each doc rendered, with no hop to the code host
- asks, now and milestones answer with their ui:// card, like apps, flow and waves already do
- A talk build is reachable through MCP: `say` starts it, reads its versions and diffs, restores and publishes
- /agents answers at first sight: the make-my-forge form and three steps, with the long how-to behind one `?`
- An lcov coverage file in a repository opens as a table: each source file's line and branch coverage, worst first, linked to the file
- A JUnit XML test report in a repository opens as its results: pass, fail and skip counts, then each failing case with its message
- A loop stall over 200 ms is named by what ran: route or job, its ms, the last hour's worst on /system
- The board shows this month's money in one line: cost, revenue and the gap, with a link to Economics
- test/snapshot-destination.test.ts passes: a failed test-connection is one sentence and the backups page shows a snapshot in progress without a refresh
- An Instagram prompt keeps its first line: test/prompts.test.ts passes
- Sentinel: release was degraded 28 minutes today: Release 0.7.524 is unproven: https://forge.open-platform.sh/search?q=a as desktop /search?q=a took 1779 ms, over 1000 m…
- test/crew-interrupted.test.ts runs in under 10 s
- Twelve quarantined suites that pass alone run in the gate again
new above
offline