syntaqxThe docs say how the merge queue blames a failure: a state is held while entries ahead of it are still being tested, smaller combinations narrow down which entries ahead a change breaks with within three builds, who is told and with what (the timeline, the issue, the session, an integration_failure decision and integration.failed), and that a fixed pull request rejoins the queue by itself once its checks pass. Sessions and why-blame gains decision records (their kinds and confidences, what g1t records itself, record_decision and list_decisions) and why over the API; the webhooks guide lists integration.failed, integration.passed and decision.recorded; the MCP reference, bring your own agent and llms.txt name the new actions.b548a9aHistory
- ..
- backup-restore-drill.mjs
- backup-restore-drill.test.mjs
- fork-storage-test.mjs
- gitstore-namespaces.mjs
- gitstore-namespaces.test.mjs
- gitstore-usage.mjs
- platform-usage.mjs
- platform-usage.test.mjs
- restore-to-gitstore.mjs
- restore-to-gitstore.test.mjs
- runner-errors.mjs
- runner-errors.test.mjs
- smoke.mjs
- smoke.test.mjs
- sudo.mjs
- vapid-keys.mjs