Skip to content

fix: keep Skillbox recovery journals outside active skill roots - #10

Draft
leojkwan wants to merge 2 commits into
mainfrom
agent/skillbox-recovery-journals
Draft

fix: keep Skillbox recovery journals outside active skill roots#10
leojkwan wants to merge 2 commits into
mainfrom
agent/skillbox-recovery-journals

Conversation

@leojkwan

Copy link
Copy Markdown
Collaborator

What changed

  • Moves retirement journals to Skillbox-owned recovery storage outside active host skill roots.
  • Migrates old in-root journals during sync --no-pull and blocks doctor until migration is complete.
  • Preserves relative symlink recovery safely and guards against replacement races.

Why

Grok recursively discovers active skill roots. When retired aliases were parked inside those roots, Grok could still load them, so retirement did not create a real cutover.

Validation

  • python3 tests/test_unit.py — 44/44 passing
  • bash tests/run_all.sh — all 19 test files passing
  • Live local migration check: the parked legacy alias no longer appears in Grok inspection while its recovery link remains intact.

This is a draft PR only; merge remains protected-branch review work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant