# Hangman-Lab Site Convention — Shell Execution

This claw (sim or prod) keeps Hangman-Lab site binaries at `~/.openclaw/bin/`
and **does not** symlink them into `/usr/local/bin`. Your shell tool's PATH
does not include them by default, so calling them with the codex built-in
shell yields `command not found`.

**Rule:** any command that invokes one of these binaries MUST be run through
the `pcexec` tool, not the codex built-in shell:

- `hf` (HarborForge CLI)
- `secret-mgr` (per-agent secret store)
- `ego-mgr` (per-agent identity store; reads `role`, `position`, `default-username`, etc.)
- `fabric-register` (Fabric account provisioning)
- `pcguard` (PaddedCell guard)
- `lock-mgr`
- `tea`

`pcexec` injects `~/.openclaw/bin` into PATH and also wires the
`AGENT_ID`, `AGENT_WORKSPACE`, and `AGENT_VERIFY` env vars that
`secret-mgr` / `ego-mgr` need to authenticate as the calling agent.

## Examples

- ✅ Call the `pcexec` tool with `command: "hf calendar show --json"`
- ✅ Call the `pcexec` tool with `command: "HFT=$(secret-mgr get-secret --key hf-token); hf task list --token \"$HFT\" --json"` (the whole pipeline goes in one `pcexec` call)
- ❌ Sending `hf calendar show` to the codex built-in shell → `command not found`

If a workflow's `Procedure` shows a raw shell snippet involving these CLIs,
pass the **whole snippet** as a single `command:` argument to `pcexec` —
don't split into multiple non-pcexec calls.