docs(agents): upgrade agent-foundry to 6df8975 #43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/foundry-6df8975"
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
castrum's agent policy sits at Agent Foundry 4545b66 (
8e39ec8); thesource has since added a main-checkout guard, sandboxed runs of others'
code, and issue triage. This brings it to 6df8975 through the
foundry-upgradeskill.What changed
checkout, so changes happen in
.worktrees/.review-pr,check-issueand outside-builtdiagnosereproductionsrun code only in a bubblewrap sandbox; the new
check-issueskilltriages an issue into a verdict.
.agents/templates/review.md; later reviewrounds report earlier findings in the report's Verdict.
AGENTS.mdgains the source's rules on remotes, pull-request approvaland writing in English; castrum's project sections are unchanged.
.claude/settings.jsondeniesWorkflow,ScheduleWakeup,ReportFindingsandListAgents, whichturns off
/loop, Workflow runs and/code-reviewfindings.CONTRIBUTING.mdnames what a workstation needs for the agents:jqfor the hooks, bubblewrap for sandboxed runs, and Codex hook trust.
How to verify
make verifyfrom the repository root: passes (needs podman).<agent-foundry>/scripts/verify-agent-config.sh .from a sourcecheckout at 6df8975: prints
agent configuration statically valid.refused; the same edit in a worktree goes through.
Run: the source validator (pass),
make check(pass),git diff --check origin/main(clean). Not run:make testandmake verify, since the agent sandbox has no podman.Considerations
Codex users trust the new hooks in
/hookson each workstation oncethis lands; Codex skips them until then.
17b87d9e4ato234ee67a4d