claudiomaradonna/castrum
1
0
Fork 0
Code Issues Pull requests Activity Actions

fix: trim the jail rule and ignore local settings #48

Merged
claudiomaradonna merged 2 commits from fix/agents-jail-rule-and-local-settings into main 2026-11-12 09:41:27 +01:00
Conversation 0 Commits 2 Files changed 2 +3 -4
motoko commented 2026-11-12 09:34:00 +01:00
Collaborator
Copy link

Why

AGENTS.md is the instruction file coding agents read at the start of
every session in this repository. Since the Agent Foundry upgrade
(49f53d5), its agent-jail rule repeats the reporting rule that
§ Working with the user now holds, so the two copies can drift apart on
the next edit or upgrade.

Separately, .claude/settings.local.json is where a contributor keeps
personal Claude Code settings. Git listed it as untracked, so a
git add -A could commit one person's settings for everyone; the Agent
Foundry source has always ignored it, and this repository's own
.gitignore never carried the line over.

Closes #47

What changed

  • The agent-jail rule in AGENTS.md § Project rules now says only what
    this project adds: a jail may lack podman and make; run what it can,
    and without make run a target's commands with the venv's tools. What
    a report says about checks run and left unrun stays in § Working with
    the user.
  • Git ignores .claude/settings.local.json, beside AGENTS.local.md
    and CLAUDE.local.md; the shared .claude/settings.json stays
    tracked.

How to verify

  1. In a checkout of the branch:

    git check-ignore -q --no-index .claude/settings.local.json; echo $?

    It prints 0; on main it prints 1.

  2. git ls-files .claude | wc -l prints 36, as on main.

  3. git diff main -- AGENTS.md changes only the agent-jail bullet, and
    grep -n 'left unrun' AGENTS.md still finds the report bullet.

make check passes on the tip. make test was not run: the agent
environment has no podman, and the change touches no role or playbook.

## Why `AGENTS.md` is the instruction file coding agents read at the start of every session in this repository. Since the Agent Foundry upgrade (49f53d5), its agent-jail rule repeats the reporting rule that § Working with the user now holds, so the two copies can drift apart on the next edit or upgrade. Separately, `.claude/settings.local.json` is where a contributor keeps personal Claude Code settings. Git listed it as untracked, so a `git add -A` could commit one person's settings for everyone; the Agent Foundry source has always ignored it, and this repository's own `.gitignore` never carried the line over. Closes #47 ## What changed - The agent-jail rule in `AGENTS.md` § Project rules now says only what this project adds: a jail may lack podman and `make`; run what it can, and without `make` run a target's commands with the venv's tools. What a report says about checks run and left unrun stays in § Working with the user. - Git ignores `.claude/settings.local.json`, beside `AGENTS.local.md` and `CLAUDE.local.md`; the shared `.claude/settings.json` stays tracked. ## How to verify 1. In a checkout of the branch: ```sh git check-ignore -q --no-index .claude/settings.local.json; echo $? ``` It prints `0`; on main it prints `1`. 2. `git ls-files .claude | wc -l` prints `36`, as on main. 3. `git diff main -- AGENTS.md` changes only the agent-jail bullet, and `grep -n 'left unrun' AGENTS.md` still finds the report bullet. `make check` passes on the tip. `make test` was not run: the agent environment has no podman, and the change touches no role or playbook. 
The report bullet of Working with the user already says what a report
gives about checks run and left unrun; keep only what the agent jail
adds.

Closes #47
Personal settings in .claude/settings.local.json override the shared
.claude/settings.json; keep them out of commits, as the Agent Foundry
source does.
claudiomaradonna deleted branch fix/agents-jail-rule-and-local-settings 2026-11-12 09:41:35 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!48
No description provided.