fix: clarify browser routing and repair relocated skill links

2026-09-20 19:53:44 -04:00
parent 89474017e1
commit 773c628512
5 changed files with 135 additions and 16 deletions
@@ -19,7 +19,7 @@ Treat [`config/pi-links.json`](../../../config/pi-links.json) as the source of t
 1. Run commands from the repository root.
 2. Read the manifest entry and the resource's `SKILL.md` or `index.ts` when diagnosing a mismatch.
 3. Resolve manifest validation errors before applying changes. Require unique skill names and existing entry points.
-4. Preserve collisions. The manager refuses regular files, directories, and links whose targets are outside this repository; report these for a human decision instead of replacing them manually.
+4. Preserve collisions. The manager refuses regular files, directories, and links whose targets are outside this repository; report these for a human decision instead of replacing them manually. For an explicitly approved repository relocation, use `sync --dry-run --migrate-from /absolute/old/root`, inspect the repairs, then `sync --migrate-from /absolute/old/root`. This only repairs manifest-declared destinations whose old target exactly matches the same repository-relative source under that old root. It does not migrate stale/unlisted links or local packages, and cannot be used with `prune`. Finish with a normal `check` without the migration option.
 5. Apply the authorized operation through `scripts/pi-links.mjs`.
 6. Run `./scripts/pi-links.mjs check` again. Completion requires exit code zero.
 7. Tell the user to run `/reload` when skill or extension exposure changed in the active Pi session.