docs: tokens in a file, no keyring (U0e)

Deploy recipe loses its D-Bus dance, install.sh its macOS skip, README and
site their macOS caveat; packaging, architecture and testing records follow;
U0e As built filled in (D-63).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HS8WZziDnyxunC23MUxrLp

docs/packaging.md

@@ -21,11 +21,10 @@ table is filled by the person who runs it.
 
 ## What step 0 found about the platforms (read before the macOS and Windows rows)
 
-The agent path was Linux-only because of the keyring. Step 0 adds the
-macOS login Keychain and the Windows Credential Manager behind
-`ledger-host/src/tokens.rs::Keeper`; CI (`portable` job) is the evidence.
-Beyond the keyring, the Windows host is a port, not a `cfg` gap. Today
-Unix-only, found by grep (2026-10-29):
+The agent path was Linux-only because of the keyring; D-63 removed the
+keyring on every OS (tokens are 0600 files under the data root, unit U0e),
+so nothing about tokens is OS-specific now. The Windows host is a port,
+not a `cfg` gap. Today Unix-only, found by grep (2026-10-29):
 
 - `ledger-host`: `bridge`, `host`, `start`, `opener` and others are
   `#[cfg(unix)]` modules; `host.rs`/`start.rs` use `setsid`, `umask`,