Prepare manifests and notes as one recoverable file operation
An interrupted process updated two manifests but left the changelog untouched. Preparation needs a journal so the next invocation can identify exactly which planned writes completed.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Filesystem transactions · Recovery · Concurrency safety
Estimated field mix
- Developer tooling60%
- Storage systems40%
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.
Acceptance criteria
- Validate every target and render every new file before replacing any repository file.
- A journal records expected before and after hashes for each target and completed replacements.
- Recovery restores only files still matching the recorded after hash and refuses to overwrite user edits.
Implementation constraints
- Keep staging and target files on the same filesystem.
- Resolve paths inside the selected repository and reject symlink escapes.
Verification to include
- Inject failure after the first replacement and recover the original bytes.
- Edit a prepared file before recovery and confirm a conflict is reported while the edit is preserved.
Deliverables
- Preparation journal, recovery command, and failure-injection fixtures
Rollout and recovery
Enable writes only after preview and recovery pass locally; use the journal to undo an interrupted preparation.
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.