Found by the post-rebrand review (#137). Two continuity gaps when a repo upgrades with state on the old prefix:
- In-flight issues escape the invariants. The one-branch / one-pull-request / one-state-label guards are keyed to the label prefix (internal/app/app.go:237, internal/forge/gh/gh.go:33). An issue mid-flight as
sc:working on branch sc/9 is invisible to a v0.4.0 run, which starts over as ax/9 with a second PR while sc:working sits next to ax:review.
- Ledger history reads as lost. BranchStore's default moved from
simplycubed/ledger to aixgo/ledger (internal/ledger/branch.go:35) with no read-back, so post-upgrade audits find an empty ledger before the upgrade date; prior history sits orphaned on the old branch.
The v0.4.0 changelog now tells adopters to finish in-flight issues first and where the old ledger lives. This issue tracks doing better than documentation: recognizing old-prefix state (or migrating the ledger branch) instead of ignoring it.
Found by the post-rebrand review (#137). Two continuity gaps when a repo upgrades with state on the old prefix:
sc:workingon branchsc/9is invisible to a v0.4.0 run, which starts over asax/9with a second PR whilesc:workingsits next toax:review.simplycubed/ledgertoaixgo/ledger(internal/ledger/branch.go:35) with no read-back, so post-upgrade audits find an empty ledger before the upgrade date; prior history sits orphaned on the old branch.The v0.4.0 changelog now tells adopters to finish in-flight issues first and where the old ledger lives. This issue tracks doing better than documentation: recognizing old-prefix state (or migrating the ledger branch) instead of ignoring it.