Deploy sync mirrors the workspace into a folder you choose, incrementally (changed files only), with no zip download. Two modes:
full (default) — the portable project: code, frozen tests, the .supergit substrate (ledger, spec, manifest, lessons), and the git history with its trailer-linked commits. Because the substrate travels with the artifact, the folder is re-attachable: any later RHA session can open it (📁 Attach project folder), verify its integrity — the ledger parses, every frozen suite matches its freeze hash — and continue the same provenance chain: new prompts add features, edits recompute subtrees, RHA heals, all appending to the same ledger. A single-writer lock (.supergit/lock) prevents two sessions from writing one project; stale locks from dead sessions are reclaimed automatically.
deployable — a production push: code and tests only, no scaffolding, no git. That copy runs anywhere but is dead to the pipeline — editing it outside RHA breaks the chain, which is exactly what the integrity check on attach will tell you.
Self-host, the server writes the folder directly. On the hosted app, the Provider Vault extension brokers a write-only, single-folder, revocable grant — see the OPSEC notice in the extension options for why that is safe in this specific architecture.