docs(agents): upgrade agent-foundry to 4545b66 #39

Merged

claudiomaradonna merged 1 commit from chore/foundry-upgrade-4545b66 into main

2026-10-17 13:21:13 +02:00

motoko commented

2026-10-17 10:16:21 +02:00

Collaborator

Why

The agent policy was adopted from Agent Foundry 33160c4. The source has
since moved to workflow skills over one work file, renamed the
documentation auditor, added a security reviewer, and dropped memory
support. This brings the repository to 4545b66 by the source's own
UPGRADING.md, keeping castrum's rules.

What changed

Agents route each request to a workflow skill (implement-feature,
fix-bug, refactor-code, document-feature, review-pr, …) that
shares one chain of steps and keeps its documents in a work folder
under .plans/.
docs-auditor is now document-reviewer, and security-reviewer is
new; reviews run through run-reviews.
AGENTS.md takes the source's sections by question. castrum's own
text keeps its meaning in the new homes: the architecture summary in
Architecture, the commands in Set-up, Test, and Quality gates, the
sandbox reporting rule in Testing and verification, and the Ansible
conventions, verbatim, in Project rules.
The memory fields and the empty Members section go; the repository
never used either.

Non-goals: castrum's own rules are not reworded, and the Ansible roles,
gates, and Makefile are untouched.

How to verify

<agent-foundry>/scripts/verify-agent-config.sh . from a clone at
4545b66 prints agent configuration statically valid: state=initialized.
git diff --check main reports nothing.
Read AGENTS.md § How to interact with the project: make setup,
make test, make check and make verify as before.

Run: the validator, make check (exit 0), and git diff --check main.
Not run: make test and so make verify, since the agent's sandbox has
no podman.

Considerations

The Quality gates subsection now asks for make check at every commit
as well as before every push, since the new fold-branch skill runs
it on each commit of a fold.
The source's subsection definitions are kept unedited so later
upgrades merge cleanly; the Quality gates one mentions required CI
gates, which castrum does not have.
Review suggestions to trim the Ansible conventions and the
Documentation bullet down to links were set aside: they would reword
castrum's own rules, which an upgrade leaves as they are.

## Why The agent policy was adopted from Agent Foundry 33160c4. The source has since moved to workflow skills over one work file, renamed the documentation auditor, added a security reviewer, and dropped memory support. This brings the repository to 4545b66 by the source's own `UPGRADING.md`, keeping castrum's rules. ## What changed - Agents route each request to a workflow skill (`implement-feature`, `fix-bug`, `refactor-code`, `document-feature`, `review-pr`, …) that shares one chain of steps and keeps its documents in a work folder under `.plans/`. - `docs-auditor` is now `document-reviewer`, and `security-reviewer` is new; reviews run through `run-reviews`. - `AGENTS.md` takes the source's sections by question. castrum's own text keeps its meaning in the new homes: the architecture summary in Architecture, the commands in Set-up, Test, and Quality gates, the sandbox reporting rule in Testing and verification, and the Ansible conventions, verbatim, in Project rules. - The memory fields and the empty Members section go; the repository never used either. Non-goals: castrum's own rules are not reworded, and the Ansible roles, gates, and Makefile are untouched. ## How to verify - `<agent-foundry>/scripts/verify-agent-config.sh .` from a clone at 4545b66 prints `agent configuration statically valid: state=initialized`. - `git diff --check main` reports nothing. - Read `AGENTS.md` § How to interact with the project: `make setup`, `make test`, `make check` and `make verify` as before. Run: the validator, `make check` (exit 0), and `git diff --check main`. Not run: `make test` and so `make verify`, since the agent's sandbox has no podman. ## Considerations - The Quality gates subsection now asks for `make check` at every commit as well as before every push, since the new `fold-branch` skill runs it on each commit of a fold. - The source's subsection definitions are kept unedited so later upgrades merge cleanly; the Quality gates one mentions required CI gates, which castrum does not have. - Review suggestions to trim the Ansible conventions and the Documentation bullet down to links were set aside: they would reword castrum's own rules, which an upgrade leaves as they are.

motoko added 1 commit

2026-10-17 10:16:26 +02:00

docs(agents): upgrade agent-foundry to 4545b66 8e39ec873b

Merge Agent Foundry from 33160c4 to 4545b66 as its UPGRADING.md
describes. The source now routes work through workflow skills over one
work file, renames docs-auditor to document-reviewer, adds
security-reviewer, and drops memory support.

AGENTS.md takes the source's sections by question. The repository's
own text moves to its new homes: the architecture summary to
Architecture, the command fields and their notes to Set-up, Test, and
Quality gates, the sandbox reporting rule to Testing and verification,
and the Ansible conventions to Project rules. The Documentation rule
keeps its owning-document list. The memory fields and the Members
section stay out, and .gitignore keeps its own .plans/ entry.

CONTRIBUTING.md no longer says the validator checks a declaration in
AGENTS.md, which has none now.

claudiomaradonna merged commit 8e39ec873b into main

2026-10-17 13:21:13 +02:00

claudiomaradonna deleted branch chore/foundry-upgrade-4545b66

2026-10-17 13:21:17 +02:00

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

claudiomaradonna/castrum!39

No description provided.

Rows
Columns