trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A preview's pill says when its pull has merged or closed, and when the preview runs an older commit than the pull's newest push
- The MCP following, follow_mode and family tools say in their doc what they take and what they answer, as forks and explore do
- GET /api/v1/explore carries an ETag and answers a repeat with 304 when nothing it lists has changed
- The MCP forks tool pages with limit and cursor and reads drift for one page only, so a repository with hundreds of forks answers quickly
- GET /api/v1/feed's first page carries the "Since you were here" digest, as the MCP feed tool's does
- An agent lists a repository's build pins through an MCP builds tool, as GET /api/v1/repos/:owner/:name/builds does
- The here manifest's explore and search actions name the MCP argument q, so an agent calls the tool the way llms.txt says
- The OpenAPI description names every refusal of POST …/builds and the fields of a build pin, so an agent reads them before it is refused
- Account form errors draw the shared danger component, and the page-local .error-note class is gone
- The OpenAPI description says GET /api/v1/telemetry/flow carries an ETag and max-age and answers a matching If-None-Match with 304
- Iterations page: /:owner/:name/iterations with pins, tree layout, zoom and folds (Jay Moran)
- An agent reads who polls the telemetry and how fast through the MCP system tool and GET /api/v1/telemetry/system, as /system shows
- The OpenAPI document gives every limit its bounds, so an agent learns them before a 422
- The proposal tests in crew-proposal and upstream-forge wait for the proposal, not a fixed 1.5 s
- test/crew.test.ts runs under 10 s: its archive test waits for the crew, not a fixed 6 s
- The MCP explore tool takes q as llms.txt says, and llms.txt names every filter explore reads
- Flaky: mcp-write-scope snapshot and the chrome click helper under load
- Each backup lane says what it backs up and who reads it after spin-down, and a lane without that line says so on the backup tile
- A test holds the MCP `issue` tool to its `blockedBy` and `blocks`, and to leaving out an issue the caller cannot see
- Polls that run out of time and carry on in 47 test files: make each fail saying what never came
- /system names each telemetry reader and its pace over the last 10 minutes, and flags one polling faster than every 5 s
- GET /api/v1/telemetry/flow tells a poller how fresh it is and answers a repeat inside 5 s with 304
- Full suite red: test/spawn-cell-e2e.test.ts
- Full suite red: test/tui-backups.test.ts
- Issues and comments on a repository from another forge read and write through, attributed to the real person
new above
offline