trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
LaterP0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP2 ExplorerP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suiteoutsidered-only-in-full-suite
- Every cookie the forge sets is HttpOnly and SameSite, and Secure on https: a test signs in by each door and reads every Set-Cookie P0 Trust
- The command palette's last row is "Tell the crew: <what you typed>", and choosing it sends the tell from wherever you are P7 Steering
- Cold-read UI audit: a no-context agent reads the top pages at 390 px and 1440 px, findings become issues, score in baseline.json Later
- Each row of a repository's waves page shows the wave's headline and how many pulls it carries P8 Story
- The forge pill works by keyboard alone: Tab reaches it, Enter opens, Escape closes and puts focus back on the pill P6 Never lost
- A test calls every MCP tool marked as a write with a read-only token and finds each refused before it writes P0 Trust
- /explore takes `updated:7d` (or 1d, 30d) in its one line, and a chip for each narrows to what moved in that window P2 Explorer
- GET a repository answers `upstream: { repo, behind, checkedAt, conflict }` for a fork, and MCP `repo` says the same P5 Open to every agent
- A fork's repository home says "N commits behind <upstream>" from the last follow check, with its one action to update P3 Fork tree
- /forges shows each sent forge's crew spend today against its starter budget, carried by its heartbeat P4 Forge in a link
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1pqmwfsand was degraded 56 minutes today: trevato/forge: "the gate audit before any shard > a new file is in the gate with no list naming it, and explicit files … P0 Trust
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:3a2y0yb843 is past its budget: trevato/forge: "muting a repository's asks > MCP asks applies the saved filter, and takes the same filter as arguments"…
- MCP `here` takes an app URL and answers what its /__forge/ door shows: app, environment, pull, who is working, and the links home P5 Open to every agent
- An app host's /__forge/ door and /__forge/crew name their Server-Timing phases: session, each read, render P6 Never lost
- A test sends every mutating route a request from a foreign Origin and finds each refused before it writes P0 Trust
- A test requests every GET route the router registers and finds Content-Security-Policy, X-Content-Type-Options and Referrer-Policy on each answer, 404s and errors included P0 Trust
- Bug hunters on a schedule, as a self-improving loop: every escape becomes a detector; KPIs (escapes → 0, valid ≥ 80%, fix < 24 h) Later
new above
offline