Repo Vault Lane
Safe archive, Git remote, or repo rescue agent. ๐
For handoff packages, the repo snapshot command builds one vault-ready archive, runs a local secret scan, uploads through the same R2 receipt flow, and keeps the proof in the ledger. For active dev work, the autosync agent runs the encrypted source-custody lane on repeat.
npm run vault:agent:start -- --env-file=env.txt --mode=full --interval-seconds=600
npm run vault:agent:status
npm run vault:dry-run
npm run vault:push
npm run vault:repo -- status --dir=.
npm run vault:secrets:manifest
npm run vault:cli clone app ./app
Safety Behavior
Archive safety and Git-level recovery stay separate.
The archive package skips local secrets, generated dependency folders, backup data, database files, private keys, old archives, and text files flagged by the credential scanner.
- Use dry run first to inspect the sanitized archive.
- Use push when the archive is ready for the vault ledger.
- Use the Git remote when the dev needs clone, fetch, and push behavior.
- Use the repo workspace helper for status, diff, commit, sync, and push receipts.
- Use the secret manifest before deleting or handing off a local workspace.