agent-soliditylisted

# agent-solidity Deployed code is public, immutable, and holds money strangers will try to take. There is no patch release. So contract work runs as a walk that is handed to you one step at a time and refuses to advance until the current step has produced something real. Instructions only. Every action is the `agent-wallet` CLI: one process, exit. Most verbs print a JSON envelope `{ok, data, error, meta}`; `contract-step` prints the step as plain text because it is instructions for you to read. On `ok:false` follow `error.hint`. ## Start here Node >= 22.18. Skill packs ship `dist/agent-wallet.mjs` (no npm install, no Solidity toolchain). **Resolve CLI once** (first hit wins; reuse it): ``` command -v agent-wallet test -x .noob/skills/agent-wallet/agent-wallet && echo .noob/skills/agent-wallet/agent-wallet test -f .noob/skills/agent-wallet/dist/agent-wallet.mjs && echo "node .noob/skills/agent-wallet/dist/agent-wallet.mjs" test -x ./agent-wallet && echo ./agent-wallet ``` **Then open the walk. This is the first thing you do, before writing any Solidity:** ``` agent-wallet contract-step ``` That prints the mode picker. Pick one, then run `contract-step --mode <mode>` and follow each step's `NEXT` line. One step per action. Never fetch ahead, never batch, never write `.sol` before step 40 tells you to, never touch a chain before step 95. Mirror the walk in your todo list: one task per step, exactly one in progress. Only signing verbs need `AGENT_WALLET_PASSPHRASE` (se