git:20260317.0c8d415 to git:20260805.f85d9cf

6 added, 4 removed. Audit A to A.

---

name: campaign-commit

- description: Choose the correct commit command in a campaign workspace. Use when you are about to commit and need to select `camp p commit`, `fest commit`, root `git commit`, or intentional root pointer sync via `camp refs-sync`.

+ description: Choose the correct commit command in a campaign workspace. Use when you are about to commit and need to select `camp commit`, `camp p commit`, `fest commit`, or intentional root pointer sync via `camp refs-sync`.

---

# Campaign Commit Decision

## Decision

- - Project submodule change: `camp p commit -m "msg"`

+ - Project change (submodule, linked project, or worktree): `camp p commit -m "msg"`

- Festival task execution: `fest commit -m "msg"`

- - Campaign root files: `git commit -m "msg"`

+ - Campaign root files: `camp commit -m "msg"` (stages all root-level changes; submodule refs excluded by default)

+ - Campaign root, scoped to specific paths: `git add <paths>` then `camp commit --all=false -m "msg"` (commits only what is staged)

- Intentional root pointer sync: `camp refs-sync [submodule...]`

## Rules

+ - Never run raw `git commit` anywhere in a campaign workspace; staging with `git add` is fine.

- Keep submodule commits and root pointer sync as separate, explicit actions.

- - Avoid raw `git commit` in submodules when campaign tooling is available.

- Do not bypass hooks with `--no-verify` without clear justification.

+ - Do not add agent co-author trailers unless explicitly requested.