Skip to content

fix: resolve relative extra paths from config root - #72

Merged
iHildy merged 5 commits into
mainfrom
ian/fix-relative-extra-paths
Aug 31, 2026
Merged

fix: resolve relative extra paths from config root#72
iHildy merged 5 commits into
mainfrom
ian/fix-relative-extra-paths

Conversation

@iHildy

@iHildy iHildy commented Aug 29, 2026

Copy link
Copy Markdown
Owner

Summary

Verification

  • bun run check
  • bun test (110 tests, 245 assertions)
  • bun run build
  • unrelated-CWD two-home exercise passed for config and secret files/directories under independent machine A/B XDG config roots; repository paths stayed contained and machine B replaced all four payloads
  • full isolated GitHub E2E passed: machine A init and two pushes, machine B link and pull, active tree unchanged, and ephemeral repository deleted

The full harness emitted its known local-materialization warning: machine B live AGENTS.md did not refresh after the final pull, while its isolated sync clone contained the second sentinel, confirming repository replication. Loopback servers also emitted the expected unsecured-server warning in the isolated sandbox.

Scope

Portable extra-path manifests remain separate from this fix; this change keeps the existing absolute manifest source-path format.

Closes #43

@iHildy
iHildy merged commit 10a3a83 into main Aug 31, 2026
3 checks passed
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.

extraConfigPaths / extraSecretPaths relative paths resolve against CWD instead of configRoot

1 participant