Rebrand alknet-vault -> alkvault

Rename the crate from alknet-vault to alkvault across source and docs:
- Cargo.toml: package name and lib name (alknet_vault -> alkvault)
- src/ doc comments and doc-test use statements
- tests/ use statements and one string literal

Convert references to non-vault alknet ADRs (003, 005, 008, 010, 014,
064) that were broken local links into @alkdev/alknet: cross-repo
references, matching the alktype sibling pattern. Local ADR/OQ
references are now proper links. Rewrote monorepo path references
(crates/alknet-vault/src/...) to the flat layout (src/...). Fixed
sdd_process.md package name (@alkdev/storage -> @alkdev/alkvault).

ADR/OQ renumbering is deferred to a subsequent pass per the alknet-
origin numbering convention. Generic prose 'vault' and type names
(VaultServiceHandle, VaultServiceError, etc.) are unchanged.

Build, 108 tests, and clippy all pass clean.

docs/architecture/decisions/025-vault-local-only-dispatch.md

@@ -6,7 +6,7 @@ Accepted
 
 ## Context
 
-alknet-vault uses irpc for its internal dispatch. The `VaultProtocol` enum is
+alkvault uses irpc for its internal dispatch. The `VaultProtocol` enum is
 annotated with `#[rpc_requests(message = VaultMessage, no_spans)]`, which
 generates a `Service` trait impl (for in-process mpsc dispatch) and a
 `RemoteService` trait impl (for remote QUIC dispatch). The vault's
@@ -103,7 +103,7 @@ which exists only to make `RemoteService` work, which is the footgun.
 
 ## Decision
 
-### 1. alknet-vault drops irpc entirely
+### 1. alkvault drops irpc entirely
 
 The vault's dispatch is direct method calls on `VaultServiceHandle`. No
 `VaultProtocol` enum, no `VaultMessage`, no `VaultServiceActor`, no mpsc
@@ -121,7 +121,7 @@ The vault crate has no remote dispatch capability. There is no
 `RemoteService` trait, no remote handler, no wire format for vault messages.
 Enabling remote vault access is not a flag flip or a server-setup change —
 it requires *building a separate crate* that depends on both alknet-core
-(for auth) and alknet-vault (for the handle) and adds the remote transport
+(for auth) and alkvault (for the handle) and adds the remote transport
 + auth-wrapping handler. That is a visible architectural act that shows up
 in code review, not a runtime config flip on a macro that was already
 generating the remote code.
@@ -152,7 +152,7 @@ defines the wire representation.
 The vault-server-crate question (review #002 C7) is decided: *if* remote
 vault access is ever needed, it is a separate crate that depends on both
 alknet-core (for `IdentityProvider`, scopes, auth-wrapping) and
-alknet-vault (for `VaultServiceHandle`). The vault crate itself remains
+alkvault (for `VaultServiceHandle`). The vault crate itself remains
 local-only. This is a decision not to create the crate now, and not to
 preclude it. It is the path of least commitment, and it matches ADR-018's
 standalone-vault principle.
@@ -311,26 +311,35 @@ version of ADR-018's intent.
 
 ## References
 
-- ADR-005: irpc as call protocol foundation (this ADR amends the vault
-  reference in ADR-005's Decision and Consequences; ~~irpc remains the
-  foundation for alknet-*call*, just not for alknet-*vault*~~ — **this
-  claim is itself superseded by [ADR-064](064-irpc-never-integrated-hand-rolled-framing.md)**,
-  which records that irpc was never integrated into alknet-call either;
-  neither the vault nor the call protocol uses irpc)
-- ADR-008: Vault integration point (the vault is a capability source
-  accessed at assembly time — this ADR makes that the *only* mode)
-- ADR-014: Secret material flow and capability injection (`DerivedKey`
-  never appears in call protocol payloads — the redacting `Serialize`
-  is defense-in-depth for logging, not for wire transport)
-- ADR-018: Vault as standalone crate (this ADR strengthens the
-  standalone principle: zero alknet crate dependencies *and* zero RPC
-  framework dependencies)
-- ADR-019: Vault assembly-layer-only access (this ADR makes the vault
-  local-only, not just assembly-layer-only-for-direct-calls)
-- OQ-21: Remote vault administration (resolved by this ADR — not a vault
-  crate feature; if needed, a separate crate with its own ADR)
-- docs/reviews/002-pre-implementation-architecture-sanity-check.md
+- `@alkdev/alknet: ADR-005` — irpc as call protocol foundation (this ADR
+  amends the vault reference in ADR-005's Decision and Consequences;
+  ~~irpc remains the foundation for alknet-*call*, just not for
+  alkvault~~ — **this claim is itself superseded by
+  `@alkdev/alknet: ADR-064`**, which records that irpc was never
+  integrated into alknet-call either; neither the vault nor the call
+  protocol uses irpc)
+- `@alkdev/alknet: ADR-008` — vault integration point (the vault is a
+  capability source accessed at assembly time — this ADR makes that the
+  *only* mode)
+- `@alkdev/alknet: ADR-014` — secret material flow and capability injection
+  (`DerivedKey` never appears in call protocol payloads — the redacting
+  `Serialize` is defense-in-depth for logging, not for wire transport)
+- [ADR-018](018-vault-standalone-crate.md) — vault as standalone crate
+  (this ADR strengthens the standalone principle: zero alknet crate
+  dependencies *and* zero RPC framework dependencies)
+- [ADR-019](019-vault-assembly-layer-only.md) — vault assembly-layer-only
+  access (this ADR makes the vault local-only, not just
+  assembly-layer-only-for-direct-calls)
+- [OQ-21](../questions/021-remote-vault-administration.md) — remote vault
+  administration (resolved by this ADR — not a vault crate feature; if
+  needed, a separate crate with its own ADR)
+- `@alkdev/alknet: docs/reviews/002-pre-implementation-architecture-sanity-check.md`
   (findings C7, C8, W8 — resolved or dissolved by this ADR)
-- irpc design patterns: `docs/research/references/iroh/irpc/09-design-patterns-and-examples.md`
+- `@alkdev/alknet: docs/research/references/iroh/irpc/09-design-patterns-and-examples.md`
   (Pattern 3: `no_rpc` flag — this ADR goes further by dropping irpc
-  entirely, since the actor pattern is also unnecessary)
+  entirely, since the actor pattern is also unnecessary)
+
+> Cross-repo references (`@alkdev/alknet: ...`) point to the parent
+> `@alkdev/alknet` workspace where this crate originated. The artifacts
+> are preserved there as historical context; they are not part of this
+> standalone repo.