chore(agents): upgrade Agent Foundry to 414f822 #66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/foundry-upgrade"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The agent policy comes from Agent Foundry, pinned in the
foundry-upgradeskill's Record at2546ee9of 30 October. The source has since moved 48 commits: it extracted the procedures several skills repeated, moved rules fromAGENTS.mdinto the skills and templates that hold their steps, and gave.claude/settings.jsonrules that keep secrets from Claude Code and turn its Bash sandbox on. Staying behind makes every later upgrade a larger merge, and the new rules protect every session on this repository. The upgrade follows the source'sUPGRADING.md.What changed
Agents find three new skills,
prove-on-main,run-sandboxed, andsettle-findings, which the workflow skills call instead of repeating their steps.AGENTS.mdkeeps the repository's own Architecture, Set-up, Test, and Quality gates text and takes the source's reordered rules; the Template lifecycle and Members sections stay out, as the adoption removed them.Claude Code on this repository now refuses to read secret files such as
.envand private keys, asks beforegit fetch,pull, andpush, and runs every Bash command in its sandbox. A session inside a client container also needssandbox.enableWeakerNestedSandboxin the container's Claude settings, whichdocs/development.mdnow says, pointing at Nested sandboxes.How to verify
claudeimage from the branch, launch it in this repository, and run a Bash command through Claude Code withsandbox.enableWeakerNestedSandboxset in the container's Claude settings. Expect it to run; without the setting, expectCan't mount proc on /newroot/proc..envor~/.ssh/id_ed25519. Expect a refusal.On the tip,
make lint && .agents/hooks/shellcheck.sh repo && make testpasses (57 scripts clean, 349 tests, 0 failures), the source'sscripts/verify-agent-config.shreports the configuration valid, andprettier --checkpasses on the changed Markdown. The branch adds no test: it changes policy text and settings only. Scenario 1 was checked by hand in a container, not by a test.Considerations
Every changed file apart from
AGENTS.mdanddocs/development.mdis the source's byte for byte.