Scrub access key IDs before publishing

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs/inventory.md

@@ -193,7 +193,7 @@ Redeploy: `scripts/api.sh compose.deploy '{"composeId":"WICLbVwy5JEbHz2SPb4tR"}'
 | Data dir | `/mnt/objects/minio` — bind mount on the 250 GB `mercury-objects` Hetzner volume |
 | Root user | `exiftree-admin` (password in Dokploy compose env) |
 | Buckets | `exiftree-media` (anonymous download enabled) |
-| Service account | access key `HU3BA5QMX2AZ67LYSKOQ` |
+| Service account | access key in Dokploy (photos compose env) |
 
 ⚠️ Gotcha learned the hard way: Dokploy compose domains are applied as **container
 labels at deploy time** — `domain.create`/`delete` alone changes nothing until the
@@ -213,7 +213,7 @@ compose is redeployed. Stale labels keep routing the old hostname.
 | Data dir | `/mnt/objects/minio-infra` (on the volume) |
 | Root user | `infra-admin` (password in Dokploy compose env) |
 | Buckets | `dokploy-backups` (private) |
-| Service account | access key `6XXKL051TW9ENNKE14DM` (used by the Dokploy destination) |
+| Service account | access key in the Dokploy destination config |
 
 #### Compose: gitea