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
- ..
- access.test.ts
- access.ts
- aliases.test.ts
- aliases.ts
- billing-actions.server.ts
- chart.test.ts
- chart.ts
- costs-route.server.ts
- costs.test.ts
- costs.ts
- credits.test.ts
- credits.ts
- deleted-accounts.test.ts
- deleted-accounts.ts
- deleted-workspaces.test.ts
- deleted-workspaces.ts
- forms.test.ts
- forms.ts
- guard.ts
- incidents.test.ts
- incidents.ts
- invites.test.ts
- invites.ts
- latency.test.ts
- latency.ts
- ledgers.test.ts
- ledgers.ts
- money.test.ts
- money.ts
- nav.test.ts
- nav.ts
- postmortem.ts
- pricing.test.ts
- pricing.ts
- review.ts
- sales-actions.server.ts
- services.server.ts
- settle.ts
- signals.test.ts
- signals.ts
- staff.ts
- suspension.test.ts
- suspension.ts
- terms.test.ts
- terms.ts
- time.test.ts
- time.ts
- workspaces.test.ts
- workspaces.ts