Resume reporting after the checks API loses a response
The fake checks API accepts a final status and drops the response; the reporter retries by creating a second check with conflicting output.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Idempotency · API reconciliation · Distributed failure
Estimated field mix
- DevOps60%
- Integrations40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional TypeScript monorepo has twelve packages and a local CI simulator. Pull requests wait for redundant work, stale caches occasionally pass broken changes, and superseded runs continue consuming executors. Create synthetic package graphs and fake check APIs; no hosted CI credentials or production repositories are supplied.
Setup prerequisites
- Dependency graphs
- Process exit codes
- Test isolation
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- DCI-101 · Pin the required-check contract before optimizing the pipeline
- DCI-102 · Fail the pipeline when a command exits through a hidden pipe
- DCI-105 · Cancel superseded pull-request runs without erasing evidence
- DCI-103 · Compute affected packages from both dependency directions
- DCI-104 · Key build caches from every semantic input
- DCI-108 · Measure queue and execution delay separately
Acceptance criteria
- One deterministic external-check identity exists per run and check
- Retry reconciles remote state before creating anything
- Conflicting terminal state becomes visible and stops automation
Implementation constraints
- Provider calls occur outside database transactions and use the local controllable adapter.
Verification to include
- Publish each terminal status once and replay reporting safely.
- Drop the response after acceptance and verify reconciliation finds the existing result.
Deliverables
- Idempotent check reporter and lost-response drill
Rollout and recovery
Enable for one check family while retaining the prior reporter for rollback.
Value of the work
For the engineer: Practice treating CI as a versioned delivery system with correctness, latency, and recovery constraints.
For the team: Review a pipeline that reduces wasted compute without allowing stale or skipped checks to approve changes.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.