Public: anyone can read this; the crew can change it.
Every gate keeps its log, so a red gate can be read without re-running the pull #6366
Every gate now keeps its log, whatever repository it ran in, and a red gate's landing note links it. The new tests and test/landing.test.ts pass, and the branch is pushed. I could not run bun x tsc --noEmit: it stops at "Cannot find type definition file for 'bun'" because @types is missing from nodemodules.
stopped parked by the crew deploy 4fffab0
3 earlier comments
Every gate now keeps its log, whatever repository it ran in, and a red gate's landing note links it. The new tests and test/landing.test.ts pass, and the branch is pushed. I could not run bun x tsc --noEmit: it stops at "Cannot find type definition file for 'bun'" because @types is missing from node_modules. The forge's check will be the first type check of this change.
- Kept log:
src/checks/gate_log.tsis new.gateCandidatecalls it after every gate. It writeschecks/gates/<owner>/<name>/<id>.jsonunder FORGE_APP_DATA with the green/red verdict, the per-file results and the last 200 lines. It keeps the newest 20 per repository, so the 21st gate drops the oldest. - Ids and names: the id is
nowplus the commit, andnowis passed in. Owner, name and id are validated before they become a path. /resilience:keepForgeGateandgate-last.jsonare untouched, so it reads the forge repository's record as before.- Landing note:
landVerdicttakes an optional log link, and a red note, with or without named tests, ends with "The gate's log: …". The link points at a new route,GET /api/v1/repos/:owner/:name/gates/:id/loginsrc/http/api.ts. It returns plain text, only to people who can read the repository, and returns 404 otherwise. - Tests:
test/gate-log.test.tscovers four things:- a red gate outside
forgeRepoleaves a log with a 200-line tail; - the 21st gate drops the oldest;
- odd owner or id values are refused;
- the landing note names the failing tests and links the log.
- a red gate outside
What I left out: there is no web page or MCP tool listing the kept gates, and no route to read the per-file results on their own. listGateLogs exists for that. The route returns the log tail with a one-line header, not the JSON.
To try it, push a pull whose gate goes red. The pull's landing comment will link /api/v1/repos/<owner>/<name>/gates/<id>/log.
Every gate now keeps its log, and a red gate's landing note links it. This update fixes the failing check. The security-floor route test fixes each route's seed placeholder, and the new route GET /api/v1/repos/:owner/:name/gates/:id/log is not one it can fill. The test now names the route with a reason: it needs a kept gate log, which is written only when a full gate runs on land. test/security-floor-routes.test.ts and test/gate-log.test.ts pass locally. The other three failed shards in the check log were exit 143 with no test named, which I read as fail-fast cut-offs, so I didn't touch them. I haven't run the full check, so the forge's run on this push will show whether they were cut-offs.
- Kept log: after each gate,
src/checks/gate_log.tswrites the verdict, per-file results and last 200 lines underchecks/gates/<owner>/<name>/in FORGE_APP_DATA. It keeps the newest 20 per repository, so the 21st gate drops the oldest. /resilience:gate-last.jsonandkeepForgeGateare untouched, so it still reads the forge repository's record.- Landing note: a red note ends with "The gate's log: …", linking the new route. The route returns plain text to anyone who can read the repository and 404s otherwise.
- Tests:
test/gate-log.test.tscovers a log left outsideforgeRepo, the 21st gate dropping the oldest, refusal of odd names and ids, and the note naming the failing tests and linking the log.
I could not run bun x tsc --noEmit here because the bun types are missing from node_modules, so the check's type pass is the first one. I also left out any page or MCP tool that lists the kept gates, and a route for the per-file results alone.
To try it, push a pull whose gate goes red and open the link in its landing comment.
Every gate now keeps its log, and a red gate's landing note links to it. This push fixes the last failing check, the OpenAPI coverage test. The kept-gate log route had no OpenAPI row, so I added getApiV1ReposOwnerNameGatesIdLog.ts and exported it from the routes index. Locally, openapi-coverage, openapi, security-floor-routes and gate-log pass.
I did not run the full check, so I can't say whether it now passes. In the last check log, the other three failed shards exited 143 without naming a test. I read those as fail-fast cut-offs after the red shard. bun x tsc --noEmit is still not run here because the bun types are missing from node_modules, so the forge's check is the first type pass.
What changed
- Kept log:
src/checks/gate_log.tsis new. After each gate it writes the verdict, per-file results and the last 200 lines underchecks/gates/<owner>/<name>/in FORGE_APP_DATA. It keeps the newest 20 per repository, so the 21st gate drops the oldest. /resilience:gate-last.jsonandkeepForgeGateare untouched, so it reads the forge repository's record as before.- Landing note: a red note names the failing tests and ends with "The gate's log: …". That points at
GET /api/v1/repos/:owner/:name/gates/:id/log, which returns plain text to anyone who can read the repository and 404s otherwise. - Route registration:
test/security-floor-routes.test.tsnames the new route as one the seed cannot fill, with a reason. The route also has the OpenAPI row described above. - Tests:
test/gate-log.test.tscovers a red gate leaving a log outsideforgeRepo, the 21st gate dropping the oldest, refusal of odd names and ids, and the note naming the tests and linking the log.
Left out: a page or MCP tool that lists the kept gates, and a route for the per-file results alone.
To try it: push a pull whose gate goes red, then open the link in its landing comment.
Parked by the crew: the check stayed red through 2 automatic tries
Every gate now keeps its log, whatever repository it ran in, and a red gate's landing note links it. The new tests and
test/landing.test.tspass, and the branch is pushed. I could not runbun x tsc --noEmit: it stops at "Cannot find type definition file for 'bun'" because@typesis missing fromnode_modules. The forge's check will be the first type check of this change.src/checks/gate_log.tsis new.gateCandidatecalls it after every gate. It writeschecks/gates/<owner>/<name>/<id>.jsonunder FORGE_APP_DATA with the green/red verdict, the per-file results and the last 200 lines. It keeps the newest 20 per repository, so the 21st gate drops the oldest.nowplus the commit, andnowis passed in. Owner, name and id are validated before they become a path./resilience:keepForgeGateandgate-last.jsonare untouched, so it reads the forge repository's record as before.landVerdicttakes an optional log link, and a red note, with or without named tests, ends with "The gate's log: …". The link points at a new route,GET /api/v1/repos/:owner/:name/gates/:id/loginsrc/http/api.ts. It returns plain text, only to people who can read the repository, and returns 404 otherwise.test/gate-log.test.tscovers four things:forgeRepoleaves a log with a 200-line tail;What I left out: there is no web page or MCP tool listing the kept gates, and no route to read the per-file results on their own.
listGateLogsexists for that. The route returns the log tail with a one-line header, not the JSON.To try it, push a pull whose gate goes red. The pull's landing comment will link
/api/v1/repos/<owner>/<name>/gates/<id>/log.Closes #6351