docs: fix alex whitelist + condescending-word findings
Fixes the 'genuine' bucket from #4040's triage: whitelist/allowlist (6 hits across 5 files, including a heading rename in turn-loop/mcp.md -- checked no anchor links reference it first) and the simply/obvious/easy condescending-word cluster (10 of 13 hits, real sentence-level rewrites rather than mechanical deletion so nothing reads awkwardly). Left 3 alex.Condescending hits untouched on purpose: integrations/matrix.md:271 and process/conventions.md:442 both say "non-obvious", swarm/ca.md:162 says "not obvious" -- alex matched the substring "obvious" inside a negated phrase, the literal opposite of condescending. Flagging these on the issue rather than silently leaving them out.
This commit is contained in:
parent
115de60b09
commit
cd252ca6b2
10 changed files with 19 additions and 19 deletions
|
|
@ -19,7 +19,7 @@ rewrites this line.
|
|||
|
||||
`nixos-container`'s start script builds the nspawn command line
|
||||
directly. Dropping a `.nspawn` file under `/run/systemd/nspawn/`
|
||||
looks like the obvious extension point and does nothing. Use
|
||||
looks like a natural extension point and does nothing. Use
|
||||
`EXTRA_NSPAWN_FLAGS` (above).
|
||||
|
||||
### `boot.isNspawnContainer = true`
|
||||
|
|
@ -113,7 +113,7 @@ socket without needing a clean reinstall.
|
|||
|
||||
`claude-code` comes from the flake's main `nixpkgs` (nixos-26.05).
|
||||
It's unfree, so the agent modules set `config.allowUnfreePredicate`
|
||||
at the container level to whitelist `claude-code` specifically —
|
||||
at the container level to allowlist `claude-code` specifically —
|
||||
scoped, only this one package. This is needed because each per-agent
|
||||
`nixosConfiguration` evaluates its own nixpkgs instance and the
|
||||
operator's host-level `allowUnfree` does **not** propagate in.
|
||||
|
|
@ -131,7 +131,7 @@ What crosses is the **store path**, not the derivation. Containers
|
|||
share the host's `/nix/store`, so the binary is already reachable
|
||||
inside them with its whole closure; hive-c0re writes the path into each
|
||||
agent's flake as a string literal and the agent module symlinks
|
||||
`bin/claude` onto PATH. Two things rule out the obvious alternatives: a
|
||||
`bin/claude` onto PATH. Two things rule out the natural-seeming alternatives: a
|
||||
`path:/nix/store/<pkg>` flake input is re-copied into the store as a
|
||||
reference-less `-source` (so the runtime closure never arrives), and
|
||||
`lib.types.package` fed a bare path runs `builtins.storePath`, which
|
||||
|
|
|
|||
Loading…
Reference in a new issue