docs(devbox): polish infisical auth guidance

Author: altaywtf

AGENTS.md

@@ -31,19 +31,11 @@ agent guide.
   identity context.
 
 Machine-local secrets belong in explicit owner-only local storage or an
-approved secret manager login. Humans may use both 1Password and Infisical;
-agents use Infisical only for secrets/env access. Agent devboxes should use
-Infisical machine identity config through the devbox runner and should not keep
-authenticated human Infisical CLI sessions.
-
-When a devbox task needs shared env, check the relevant Infisical
-project/path first. Do not revive workspace `.env` symlinks, devbox-env
-generated files, or 1Password service-account refresh stacks.
-
-For agent SSH, ordinary private keys may live in Infisical under the devbox or
-agent boundary. Keep fingerprints and public metadata in docs, retrieve keys
-only for the command or owner-only local file that needs them, and keep key
-files mode `0600`.
+approved secret manager login. For shared agent hosts, use the current contract
+in [Devbox setup](docs/devbox.md): humans may use 1Password and Infisical;
+agents use Infisical machine identity auth only for secrets/env access. Do not
+revive workspace `.env` symlinks, devbox-env generated files, or 1Password
+service-account refresh stacks.
 
 ## Agent Operating Checklist
 

README.md

@@ -78,14 +78,11 @@ Keep these out of Git:
 - Codex auth, Browser approvals, sessions, caches, worktrees, and app state.
 - Browser profiles, Docker/Colima state, dependency folders, and build output.
 
-For always-on agent hosts, use the secret model in [Devbox setup](docs/devbox.md):
-humans use both 1Password and Infisical, agents use Infisical only, and normal
-shells do not export Infisical tokens or machine credentials. Devbox agents
-should use owner-only persistent machine identity config plus
-`scripts/secrets/infisical-devbox-run.sh`, not saved human Infisical CLI
-sessions. Agent SSH keys may live in Infisical under the devbox secret boundary
-and should be retrieved only into owner-only local key files or the command
-environment that needs them.
+For always-on agent hosts, use the secret model in
+[Devbox setup](docs/devbox.md). The short version: humans may use 1Password and
+Infisical, agents use Infisical machine identity auth only, and tokens or client
+credentials must not live in default shells, process managers, tracked files, or
+generated dotenv refresh stacks.
 
 ## Personalization
 

docs/bootstrap.md

@@ -214,12 +214,10 @@ use a different local key path than commit signing.
 If the devbox runs long-lived workspace or agent services, follow
 [Devbox setup](devbox.md). The short version: run
 `./scripts/secrets/configure-infisical-devbox.sh` once with a human-supplied
-machine identity client ID/secret, keep human Infisical CLI sessions off agent
-devboxes, keep long-lived tokens out of default shells and process-compose
-YAML, and run routine secret-aware commands through
-`./scripts/secrets/infisical-devbox-run.sh`. Agent SSH keys may live in
-Infisical under the devbox secret boundary and should be retrieved only into
-owner-only local key files or the command environment that needs them.
+Universal Auth client ID/secret, keep human Infisical CLI sessions off agent
+devboxes, keep long-lived tokens out of default shells and process-compose YAML,
+and run routine secret-aware commands through
+`./scripts/secrets/infisical-devbox-run.sh`.
 
 Verify each devbox user:
 

docs/devbox.md

@@ -34,7 +34,7 @@ write it.
 
 When an agent task needs shared env, check the relevant Infisical project/path
 first. Do not recreate workspace `.env` symlinks, devbox-env generated files,
-or 1Password service-account refresh stacks.
+token caches, or 1Password service-account refresh stacks.
 
 For services and agents:
 
@@ -71,9 +71,9 @@ One-time setup:
 The helper prompts locally for the Infisical domain, project ID, environment,
 Universal Auth client ID, and Universal Auth client secret. Use the client ID
 shown under the machine identity's Universal Auth method, not the machine
-identity ID shown in the identity details panel. Humans should source the
-initial client ID/secret from their secret manager, usually 1Password or
-Infisical, and enter them locally. Do not paste them into agent chat.
+identity ID shown in the identity details panel. Humans should source those
+values from their secret manager, usually 1Password or Infisical, and enter them
+locally. Do not paste them into agent chat.
 
 It writes non-secret selectors to `~/.config/uinaf/devbox.env` and machine
 credentials to `~/.config/uinaf/infisical-machine.env`. Both files must be mode
@@ -86,27 +86,31 @@ Routine command-boundary use:
 
 ```sh
 ./scripts/secrets/infisical-devbox-run.sh -- sh -c '
+  mkdir -p "$HOME/.config/example"
   infisical export \
     --domain "$INFISICAL_DOMAIN" \
     --token "$INFISICAL_TOKEN" \
     --projectId "$INFISICAL_PROJECT_ID" \
     --env "$INFISICAL_ENV" \
-    --path "/example-devbox/openclaw-env" \
+    --path "/example-devbox/runtime-env" \
     --format dotenv \
-    --output-file "$HOME/.openclaw/.env" \
+    --output-file "$HOME/.config/example/runtime.env" \
     --silent
+  chmod 600 "$HOME/.config/example/runtime.env"
 '
-
-chmod 600 "$HOME/.openclaw/.env"
 ```
 
-For non-OpenClaw services, replace the output file with the runtime-specific
-file or run the service command through `infisical-devbox-run.sh`.
+Replace the output file with the runtime-specific file or run the service
+command through `infisical-devbox-run.sh`.
 
 Do not create additional hidden helper scripts, token caches, shell exports, or
 runtime dotenv refresh stacks outside this contract. If another unattended
 refresh mechanism becomes necessary, document and verify that mechanism first.
 
+If setup fails with `Invalid credentials`, check that the ID came from the
+Universal Auth method. The machine identity ID in the details panel is not a
+Universal Auth client ID and cannot mint a token.
+
 ## Agent SSH Key Storage
 
 Devbox agent SSH keys may be stored as Infisical secrets. This keeps the key in
@@ -229,7 +233,7 @@ INFISICAL_CLIENT_SECRET=...
 ```
 
 Keep both files out of Git. Do not create repo-local workspace `.env` symlinks
-for agent/OpenClaw runtime env.
+for agent runtime env.
 
 If a devbox identity does not run process-compose, set
 `PROCESS_COMPOSE_ENABLED=0` in its local config so verification does not