chore(muse#38): delete deprecated sequential-domain-integer migration
The index-domain migration converted pre-Phase-1 sequential domain integers (0-6, excluding 5 -- never assigned) in HD paths to the current hash-derived namespace. The only valid domains today are hash-derived. Per the workspace's No Legacy / Delete on sight rule, this migration machinery is fully removed:
- muse/core/domain_migration.py - muse/cli/commands/migrate_cmd.py (the 'muse migrate domain-integers' command -- its only subcommand; the entire top-level 'muse migrate' namespace is gone, unrelated to and not to be confused with 'muse code migrate', which is untouched) - tests/test_migrate_domain_integers.py - registration + doc references in muse/cli/app.py
Safety check before deletion: confirmed no real identity uses a legacy sequential-domain HD path -- checked ~/.muse/identity.toml (both entries use hash-derived domain 1660078172) and the registered staging identity via 'muse auth show' (same). No registration path in current code ever writes a legacy-format path, so no live identity could plausibly need this migration.
Resolved the ticket's open question: the module's own docstring already correctly stated index 5 was 'excluded' (never assigned), not removed -- the ticket's confusion was in stale summary prose elsewhere, not the code.
Verified: muse migrate now errors as an unrecognized command; muse code migrate is unaffected. 171 migrate-related tests pass; muse code test (scoped to the changed app.py) reports 27/27 passed, full coverage.
Semantic Changes
262 symbols
0 comments
muse hub commit comment sha256:15bff0adad139dcfd2b91a6270e3f678529685b428e597b46866080b8ad190ce --body "your comment"
No comments yet. Be the first to start the discussion.