fix: ensure_hub_seed always resets origin before push — eliminates stale tracking no-op (issue #62 Phase 4)
Phase 3's JSON-parse fix left a deeper bug: when bench-seed-m is deleted and recreated, the local seed's remote tracking ref (origin/main → sha256:<tip>) still matches the local branch tip. muse push sees local == tracking and sends nothing. The fresh hub repo never receives any commits and keeps its initial 'init-sha256:<repo-id>' branch head.
Replace the conditional 'add if absent' block (and its JSON parse) with unconditional remove + add — the same pattern bench_push already uses on its per-run copies. No JSON parse needed; no stale tracking possible.
Retired TestEnsureHubSeedRemoteParse (tested superseded conditional behaviour). Added TestEnsureHubSeedRemoteReset with RED→GREEN coverage of the new contract.
sha256:ab2a6a9ecf2440e0e840c3a66bbcb52a42c92c060cb1f6cb247385185119cb1c
sha
sha256:f2ad900e483afb5f23e9daf0589e6cb64711b12c1e353188916ae13397d09797
snapshot
Older
bench: wire_hash cache invalidation, safety guards, hard-delete test
sha256:99886fab7ef33cf51ae0075b9eb28d837b76d91b2c14c5a3c2eda955dee78610
All commits
Newer
fix(wire): rename delta frame key base_id → base; fix repo_id in…
sha256:b4fb9db2858c35127b2dee273737d049c228a6f6d13ff8d671ad1c6dec5d5cae
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:ab2a6a9ecf2440e0e840c3a66bbcb52a42c92c060cb1f6cb247385185119cb1c --body "your comment"
No comments yet. Be the first to start the discussion.