Repair stale automatic conversation links

[ascendho]

Summary

• repair stale automatic links when the current project has stronger path or Git evidence
• preserve explicit manual links
• prevent a broad parent repository from claiming conversations whose recorded Git remote conflicts
• bump the VS Code extension to 0.4.1

Root cause

A Git repository in the user's home directory had previously claimed conversations from nested repositories through a broad path alias. Once stored, that automatic link always won, so a later sync of the correct nested project could not repair it.

Verification

• pnpm check — lint, typecheck, 27 tests, build
• VSIX packaging succeeded
• release version check for v0.4.1 succeeded
• real-data recovery moved all 13 internship-notes conversations from the stale parent project to the correct project
• total registry counts remained 84 conversations / 84 links
• SHA-256 hashes of all 13 Codex transcript files were unchanged across sync

A rollback copy of the local registry was created before recovery.