trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Batch doctor: on a red merge batch, find the culprit, tell load reds from real ones, hold with the exact failing test
- A terminal screen adds its own palette entry from its own module, so a new screen no longer edits src/tui/forge.ts
- P0: a real Anthropic key is refused when spawning a forge — accept any key as pasted (cherry-pick steward/model-key-accept)
- P0: the home page takes ~7 s: the KPI/panel caches never hit (keyed on the write stamp) and readKpis costs 4.4 s on every load
- Builder slots serve the roadmap first: tests-only and small-addition pulls get at most a set share of builder slots
- Data browser core: read any SQLite file a viewer may see — the forge's own (admins) and each app's per environment (its writers) — tables, rows, read-only SQL, secrets masked
- Release keeper: cut on cadence, verify under page load, roll back to the named known-good version, hold with a reason
new above
offline