trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- docs/MCP.md names every ui:// card the server draws, and a test fails when a card is drawn but not described
- test/rehearsal-real.test.ts is admitted: ten green flake-hunt runs on the check host, or its red names what did not come up and that is fixed
- /search?q=a answers under 300 ms on a fixture of production's size, pinned by a test that reads its Server-Timing phases
- The egress proxy pauses a fast upstream for a slow reader instead of cutting it, so a big tarball installs whole
- `runs` answers with a ui://forge/runs card: each run's kind, state, issue or pull, and duration, newest first, linked to its log
- A forge answers every request in its first ten minutes: no 503 "Waking up" on a POST, and no unclean restart after it is made
- Plans are a setting: free, small, medium and large, each with a size, a monthly price, a monthly crew credit and a forge count
- The home page sells forges today: three plans, each with a button to its paym…
- Billing is a seam with two providers, none and stripe; with none, every forge is free within its plan
- A new forge follows the topmost forge on its own: its forge repository takes updates by default, and a clean update merges itself
- An app inside a child forge reaches a payment provider when its forge.json declares it
- The board's money line names the Economics slider's position, linked to Settings → Economics
- `asks` answers with a ui://forge/asks card: each decision waiting on the owner as one line with its one action
- `now` answers with a ui://forge/crew card: who, on what, since when, cost, a waiting planner first
- `releases` answers with a ui://forge/release card: each kept release's version, when it rolled, how many pulls it carried and whether it is proven
- A `.env.example` in a repository opens as the variables an app needs: name, example value and its comment per row
- Crew runs on a forge admin's org repos use the forge's model account (every child made for an org fails its first run today)
- Every background timer on the forge runs inside `during`, so no loop stall is blamed on `unknown`
- No background job holds the loop longer than 50 ms in one synchronous slice on a busy fixture, and a test times each one
- /search?q=a answers under 300 ms on production, so the release proof stops reading it as degraded
- /system and /map answer at first sight: standing notes become a word or a glyph, and the how-to moves behind one `?`
- An OpenAPI document in a repository opens as its operations: method, path and summary per row, grouped by tag