#3260 Docs: default vault at repo init, --no-vault, and base_dir no longer persisted (swamp-club#3259)

The manual needs updates for swamp-club#3259. That change makes swamp repo init create a local_encryption vault named default (and set defaultVault: default), adds swamp repo init --no-vault, and stops local_encryption vault configs from persisting an absolute base_dir.

content/manual/reference/repository-configuration.md

• swamp repo init section: init now creates the default vault at vaults/local_encryption/<id>.yaml and sets defaultVault: default. Document --no-vault as the opt-out, and say that --force keeps an existing default vault and an existing defaultVault.
• swamp repo init --json example output: add the vault field ({ name, type, created }, or null with --no-vault).
• Directories section: mention the vault config file init writes.
• defaultVault section: new repos set it to default. Changing it to a team vault (for example after swamp vault create @swamp/aws-sm ...) is how to send sensitive outputs elsewhere.

content/manual/reference/vaults.md

• The local_encryption config example shows base_dir set to an absolute path under a user's home directory. New configs no longer store base_dir: it is resolved to the repository root when the vault loads. Update the example and the base_dir table row ("not stored by default; resolved to the repository root at runtime").
• The server-defaults note for vault create/vault migrate over --server says base_dir is set to the serve repo. Now it is left unset and resolved to the serve host's repository root when the vault loads. A remote caller still cannot choose the key source.
• The "no vault is configured" section: on a new repo this error now only occurs after --no-vault or after the default vault is deleted.
• A short note on per-machine storage: the default vault's config is committed, but its key and secrets are per machine. A clone starts with an empty default vault, and swamp datastore setup extension warns about this for shared datastores.

content/manual/tutorials/storing-secrets.md

The tutorial runs swamp vault create local_encryption secrets right after swamp repo init. A new repo already has a default vault, so either use it (swamp vault put default ...) or explain why the tutorial creates a second one.

Also check

tutorials/your-first-automation.md and any how-to that tells readers to create a vault before storing a first secret.