Resume a publish rehearsal after the registry response disappears
The fake registry accepts a package and then drops the connection. A blind retry may conceal a different artifact already registered at that version. Reconcile remote state before resuming.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Idempotency · Distributed failure · Artifact integrity · State machines
Estimated field mix
- Developer tooling50%
- Distributed systems30%
- Integrations20%
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 team maintains six related packages. Release notes, version changes, and tags are copied between a spreadsheet and a terminal; a failed upload recently left two packages ahead of their dependents. The exercise uses temporary repositories and a fake registry.
Setup prerequisites
- Create a temporary Git repository with three related fixture packages.
- Use a local registry double; no publishing credentials are required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CLI-101 · Print package versions without depending on the current directory
- CLI-103 · Include dependent packages in the proposed version bump
- CLI-104 · Make a dirty checkout a deliberate release decision
- CLI-105 · Turn change fragments into package-specific release notes
- CLI-106 · Prepare manifests and notes as one recoverable file operation
- CLI-107 · Prevent a second release process from using the same checkout
Acceptance criteria
- Each planned package records its version and artifact digest before the fake publish call.
- An existing version with the same digest is treated as completed; a different digest blocks the entire resume.
- Resume respects dependency order and leaves a durable record of ambiguous, reconciled, and completed steps.
Implementation constraints
- Use a local registry port with deterministic lost-response behavior.
- A release record is append-only; do not overwrite the original failed attempt.
Verification to include
- Drop the first response after acceptance and verify resume makes no duplicate upload.
- Preload the same version with different bytes and confirm dependents remain unpublished.
Deliverables
- Resumable rehearsal workflow and ambiguity incident walkthrough
Rollout and recovery
Keep the registry adapter local for this exercise; require a reviewed digest reconciliation policy before a real adapter.
Value of the work
For the engineer: Practice CLI contracts, graph reasoning, filesystem safety, and recovery from partial work.
For the team: Review how an engineer makes release changes inspectable and recoverable before they affect consumers.
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.