chore(agents): upgrade agent-foundry to 5e0c270 #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/upgrade-agent-foundry"
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
warden adopted agent-foundry at b9207e9, before the foundry-upgrade skill
existed, and the source has since moved 87 commits ahead.
What changed
The foundry-upgrade skill is bootstrapped with its Record, then used to merge
b9207e9..5e0c270. warden gains the repository-owned skills (brainstorm,
write-plan, diagnose, forge, foundry-upgrade), the change-reviewer and
dependency-advisor subagents, and the current memory contract and curator
adapters. AGENTS.md takes the new layout and keeps warden's identity,
commands, dependency baseline, and estate-neutral rule.
The memory selection moves to each workstation's untracked AGENTS.local.md,
CLAUDE.md and the bundled validator are removed, and the executed
implementation plan leaves the tree for the local .plans/.
Risks and follow-ups
Memory stays unavailable until the operator repeats the preflight in
docs/LOCALRECALL.md. Codex has not been run against the new layout.