)

Closes #665

## Summary

Moves the `aws-sm`, `azure-kv`, and `1password` vault providers from
built-in types to extension vaults published at swamp.club. After this
change, only `local_encryption` (and `mock` for testing) remain as
built-in vault types. The three cloud/external vault providers are now
independently versioned extensions that auto-resolve from the registry
on first use.

### What changed

**Removed from core:**
- Deleted `aws_vault_provider.ts`, `azure_kv_vault_provider.ts`,
`onepassword_vault_provider.ts` and their test files (-1,545 lines)
- Removed `aws-sm`, `azure-kv`, `1password` from `BUILT_IN_VAULT_TYPES`
in `vault_types.ts` — only `local_encryption` remains
- Removed their switch cases from `VaultService.registerVault()`
- Removed `@aws-sdk/client-secrets-manager`, `@azure/identity`,
`@azure/keyvault-secrets` from `deno.json` dependencies

**Migration path via `RENAMED_VAULT_TYPES`:**
- `aws` / `aws-sm` → `@swamp/aws-sm`
- `azure` / `azure-kv` → `@swamp/azure-kv`
- `1password` → `@swamp/1password`

When `VaultService.fromRepository()` loads an existing vault config with
an old type name, it remaps to the `@swamp/*` extension type and
auto-resolves it from the registry (installed by PR #725's
auto-resolution infrastructure).

**`vault create` simplified:**
- Removed `--region`, `--vault-url`, `--op-vault`, `--op-account` flags
- All extension vault types now use `--config <json>` for provider
configuration
- `resolveProviderConfig()` only handles `local_encryption` now

**`ensureDefaultVaults()` is now a no-op:**
- Previously auto-created an AWS vault when `AWS_ACCESS_KEY_ID`,
`AWS_SECRET_ACCESS_KEY`, and `AWS_REGION` were set
- This behavior is removed since AWS is now an extension

**Error messages updated:**
- "No vaults configured" error now suggests `swamp extension pull
@swamp/aws-sm` instead of setting AWS env vars

### Published extensions

The three vault providers have been published to swamp.club as:
- `@swamp/[email protected]` — shells out to `op` CLI, no npm SDK
deps
- `@swamp/[email protected]` — uses
`@aws-sdk/[email protected]`
- `@swamp/[email protected]` — uses `@azure/[email protected]` +
`@azure/[email protected]`

Source lives at https://github.com/systeminit/swamp-extensions

## User impact

### Existing users with vault configs on disk

**No action required.** Existing `.swamp/vault/*.yaml` files with `type:
aws-sm`, `type: azure-kv`, or `type: 1password` continue to work. On
first use, swamp will:
1. Log a deprecation warning about the old type name
2. Remap it to the `@swamp/*` extension type
3. Auto-resolve and install the extension from the registry
4. Load the vault and proceed normally

### Creating new vaults

The CLI syntax changes from dedicated flags to `--config <json>`:

```bash
# Before
swamp vault create aws-sm my-vault --region us-east-1
swamp vault create azure-kv my-vault --vault-url https://myvault.vault.azure.net/
swamp vault create 1password my-vault --op-vault Engineering

# After
swamp vault create @swamp/aws-sm my-vault --config '{"region":"us-east-1"}'
swamp vault create @swamp/azure-kv my-vault --config '{"vault_url":"https://myvault.vault.azure.net/"}'
swamp vault create @swamp/1password my-vault --config '{"op_vault":"Engineering"}'
```

### Offline users

Users without registry access can manually install extensions by placing
the `.ts` source files in `extensions/vaults/`.

### Binary size

The compiled binary no longer includes the AWS SDK, Azure SDK, or
1Password provider code. These dependencies are now bundled into the
extensions at publish time.

## Known issues

- Azure Key Vault extension bundle fails to load in compiled binary due
to large bundle size (#733)
- Auto-resolver fails when `extensions/models/` directory doesn't exist
for vault-only extensions (#734)

## Verification

- `deno check` — passes
- `deno lint` — passes
- `deno fmt` — passes
- `deno run test` — 3138 passed, 0 failed
- `deno run compile` — binary compiled successfully
- Manual testing: auto-resolution verified for all three extensions
(1password fails at `op` CLI check, aws-sm fails at credential check —
both expected)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>

## Summary

Adds CLI commands to manage trusted collectives for extension
auto-resolution, solving a discoverability problem where the feature was
completely invisible to both users and AI agents.

### The Problem

A user asked Claude about trusted collectives in their swamp repo, and
Claude responded: *"The trusted collectives feature doesn't exist in
swamp yet."* Despite the feature being fully implemented (PRs #725 and
#727), it was only configurable by manually editing `.swamp.yaml` — no
CLI command, no `--help` text, no discoverability path.

### The Solution

Four new commands under `swamp extension trust`:

```bash
swamp extension trust list                # Show explicit, membership, and resolved collectives
swamp extension trust add <collective>    # Add a collective to the trusted list
swamp extension trust rm <collective>     # Remove a collective from the trusted list
swamp extension trust auto-trust <on|off> # Enable/disable membership auto-trust
```

The `list` command shows the full picture — explicit collectives from
`.swamp.yaml`, membership collectives from auth, and the resolved/merged
effective list. This means even on a fresh repo with no config, a user
sees that `swamp` and `si` are trusted by default.

### Architecture

Follows the libswamp + renderer pattern (issue #739):

| Layer | Files | Purpose |
|-------|-------|---------|
| **Shared types** | `src/libswamp/extensions/trust.ts` |
`DEFAULT_TRUSTED`, `TrustModifyData`, `TrustModifyEvent`,
`resolveTrustedCollectives()` |
| **Generators** |
`src/libswamp/extensions/trust_{list,add,rm,auto_trust}.ts` | Pure
business logic with injected deps |
| **Renderers** |
`src/presentation/renderers/trust_{list,modify,auto_trust}.ts` | Log +
Json output modes |
| **CLI commands** | `src/cli/commands/extension_trust*.ts` | Pure
wiring (deps → generator → renderer) |

### Refactoring

- **Extracted `resolveTrustedCollectives()`** from `src/cli/mod.ts` into
`src/libswamp/extensions/trust.ts` — it was domain logic living in the
CLI layer
- **Moved 8 tests** from `src/cli/mod_test.ts` to
`src/libswamp/extensions/trust_test.ts` to follow the code
- **Single `TrustModifyEvent`** shared by both `trust_add` and
`trust_rm` generators (identical event shapes, no reason for separate
types)
- **`DEFAULT_TRUSTED`** defined once, used everywhere

### Documentation Updates

- `design/extension.md` — documents CLI commands in "Trusted
Collectives" section
- `design/repo.md` — cross-references CLI commands from
`trustedCollectives` config
- 7 skill files updated with `swamp extension trust` references for
discoverability

## Test Plan

- [x] 26 generator tests (`src/libswamp/extensions/`) — all pass
- [x] 16 renderer tests (`src/presentation/renderers/trust_*_test.ts`) —
all pass
- [x] 8 `resolveTrustedCollectives` tests moved to proper location — all
pass
- [x] Existing `mod_test.ts` tests still pass (57 tests, down from 65
after moving 8)
- [x] `deno check` passes on all files
- [x] `deno lint` passes
- [x] `deno fmt` applied

🤖 Generated with [Claude Code](https://claude.com/claude-code)