Pin the required-check contract before optimizing the pipeline
Branch protection expects names that differ from the workflow after a recent rename, leaving one required check permanently pending.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- CI contracts · Configuration validation
Estimated field mix
- DevOps70%
- Developer tooling30%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Declare stable check identities and their owning commands
- Map every protected check to exactly one terminal report
- Unknown or duplicated check names fail workflow validation
Implementation constraints
- The local simulator must not call a real repository or modify branch protection.
Verification to include
- Complete every declared check and reconcile its final status.
- Rename and duplicate a check, then confirm validation blocks the workflow.
Deliverables
- Required-check manifest and consistency test
Rollout and recovery
Publish the manifest before changing job topology.
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.