Add a migration inventory with checksums and sequence gaps
Two branches introduced migrations with the same sequence number.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- CLI design · SQL
Estimated field mix
- Developer tooling60%
- Database engineering40%
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 subscription service has accumulated migration scripts with unclear lock risks and no consistent rehearsal output.
Setup prerequisites
- Create a disposable local database with synthetic subscriptions and a separate scratch database; author all fixtures locally.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List migration order and file digests.
- Reject duplicate sequence identifiers.
- Report missing predecessors without executing SQL.
Implementation constraints
- Read migration files as text only.
Verification to include
- Inventory a valid sequence.
- Detect duplicate IDs and an edited historical file.
Deliverables
- Inventory command.
Rollout and recovery
Adopt read-only checks first; resolve history discrepancies before applying migrations.
Value of the work
For the engineer: Practice migration tooling, lock reasoning, and clear developer feedback.
For the team: Provide reviewers with repeatable migration checks and explicit recovery limits.
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.