@event4u/agent-config 1.19.0 → 1.21.0

package/.agent-src/commands/council/default.md

@@ -28,14 +28,19 @@ The user invoked `/council default` on exactly one input mode:
 - `files:<path>,<path>` — a comma-separated file list
 
 Optional invocation flag: `mode:api|manual` overrides the per-member
-and global mode for this call only (see Step 2.5). `mode:playwright`
-is reserved for Phase 2c — refuse politely if invoked.
+and global mode for this call only (see Step 2.5).
 
-Optional **rounds**: `rounds:N` (1-3) enables multi-round debate. Round
-1 sees the artefact alone. Round 2+ sees the artefact plus anonymised
-critiques from the previous round (provider/model identity stripped).
-Total spend = N × single-round cost; surface this in the cost gate.
-Default `rounds:1`.
+Optional **rounds**: `rounds:N` (1-3) overrides the multi-round debate
+count. Round 1 sees the artefact alone. Round 2+ sees the artefact plus
+anonymised critiques from the previous round (provider/model identity
+stripped). Total spend = N × single-round cost; surface in cost gate.
+
+Default comes from `ai_council.min_rounds` in `.agent-settings.yml`
+(default `2` so members critique each other at least once before
+convergence). **Do NOT ask "how many rounds?"** when `rounds:N` is
+unset or `N <= min_rounds` — proceed with the settings default. Ask
+only when the artefact is genuinely complex; surface as a numbered
+choice with the cost delta.
 
 Optional **mode_override**: `mode_override=pr|design|optimize` swaps
 the system-prompt addendum for one of the specialised lenses
@@ -71,7 +76,7 @@ Read `.agent-settings.yml` → `ai_council`:
   to env vars. Ever.
 
 Load the price table via `scripts.ai_council.pricing.load_prices()`
-(auto-bootstraps `.agent-prices.md` from defaults if missing). Run
+(auto-bootstraps `agents/.agent-prices.md` from defaults if missing). Run
 `pricing.is_stale(table)` and, if stale, surface the staleness gate
 from the `ai-council` skill (§ Stale price-table gate) before
 continuing.
@@ -81,15 +86,13 @@ continuing.
 For each enabled member, resolve its mode via
 `scripts.ai_council.modes.resolve_mode(name, invocation_mode,
 member_settings, global_mode)`. Precedence: invocation flag >
-per-member setting > global setting > default (`api`).
+per-member setting > global setting > default (`manual`).
 
 Construct each member from the resolved mode:
 
 - `api` → `AnthropicClient` / `OpenAIClient` (billable, cost-gated).
 - `manual` → `ManualClient` from `scripts.ai_council.clients`
   (`billable=False`, no API key, no SDK call).
-- `playwright` → reserved for Phase 2c. If a settings/invocation
-  resolves to it, refuse with a one-line note.
 
 ### 3. Cost confirmation — ALWAYS ASK for billable members
 
@@ -136,6 +139,12 @@ Once the user picks `1`, invoke the same arguments with `run` plus
     [--original-ask "<framing sentence>"]
 ```
 
+`--rounds` defaults to `ai_council.min_rounds` from
+`.agent-settings.yml` (or `2` if unset). Pass `--rounds N` only when
+the user explicitly asked for a different count or a complex
+artefact justifies more depth — do not pass `--rounds 1` to "save
+money" by default; settings owner already chose `min_rounds`.
+
 The CLI:
 
 - bundles the artefact via `scripts.ai_council.bundler` (redaction +
@@ -203,7 +212,7 @@ council can act on the project directly.
 - **Stale price table, refresher fails (offline)** → state the
   failure, re-offer "continue with stale table / cancel", do not
   proceed silently.
-- **`.agent-prices.md` corrupt (missing frontmatter or columns)** →
+- **`agents/.agent-prices.md` corrupt (missing frontmatter or columns)** →
   surface the parse error, suggest deleting the file to bootstrap
   fresh from defaults; never silently fall back.
 - **All members error (CLI exit 1)** → render the errors via

package/.agent-src/commands/council.md

@@ -26,7 +26,7 @@ sub-command swaps the mode-specific addendum.
 | `/council optimize` | `commands/council/optimize.md` | Run the council on an optimization target — ranked, evidence-based suggestions |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/create-pr.md

@@ -106,19 +106,39 @@ Once the user approves the content from step 2:
 
 ### 4. After creation
 
-- Show the PR URL.
-- If a Jira ticket was linked, ask:
-  ```
-  > Transition Jira ticket {TICKET-ID} to "In Review"?
-  >
-  > 1. Yes — update status
-  > 2. No — leave as-is
-  ```
+#### 4a. Strip attribution footers (mandatory)
+
+`github-api` may server-side-append attribution after a clean send.
+Per [`no-attribution-footers`](../rules/no-attribution-footers.md),
+re-check the body after creation **and after every body PATCH**:
+
+1. `GET /repos/{owner}/{repo}/pulls/{number}` — re-fetch body.
+2. Search (case-insensitive) for: `Generated with [Augment Code]`,
+   `🤖 Generated with`, `Pull Request opened by [Augment Code]`,
+   `Co-authored by Augment Code`, unsolicited `augmentcode.com` link.
+3. If any present, strip with surrounding `---` and trailing
+   whitespace, then `PATCH /pulls/{number}` with cleaned body.
+4. Re-fetch to verify. If the pattern reappears, repeat once; if
+   still present, surface to user and stop (no strip/PATCH loop).
+5. Note in the reply how many footers were removed (or "clean").
+
+#### 4b. Show the PR URL
+
+#### 4c. Jira transition
+
+If a Jira ticket was linked, ask:
+```
+> Transition Jira ticket {TICKET-ID} to "In Review"?
+>
+> 1. Yes — update status
+> 2. No — leave as-is
+```
 
 ### Rules
 
 - **Always use the PR template** from `.github/pull_request_template.md` — read it, fill its sections.
 - **Always show the PR content before creating it** — never create blindly.
 - **Push the branch first** if it hasn't been pushed (with user permission).
+- **Never add attribution footers** — see [`no-attribution-footers`](../rules/no-attribution-footers.md). Strip-pass in 4a defends against tool-injected footers.
 - Only create the PR — never merge it.
 - Only commit or push with explicit user permission.

package/.agent-src/commands/e2e-heal.md

@@ -21,7 +21,7 @@ suggestion:
 > 2. Fix a specific test file — which one?
 > 3. Fix tests that failed in CI — provide the CI run URL or error output
 
-- Read the Playwright guideline: `../../docs/guidelines/e2e/playwright.md`
+- Read the Playwright guideline: `../docs/guidelines/e2e/playwright.md`
 
 ### 2. Run failing tests
 

package/.agent-src/commands/e2e-plan.md

@@ -21,7 +21,7 @@ suggestion:
 > 2. Which feature area? (e.g., "checkout flow", "user settings", or "all visible flows")
 > 3. Is there an existing seed/setup file? (e.g., `tests/e2e/fixtures/auth.ts`)
 
-- Read the Playwright guideline: `../../docs/guidelines/e2e/playwright.md`
+- Read the Playwright guideline: `../docs/guidelines/e2e/playwright.md`
 - Check for existing test plans in `specs/` or `tests/e2e/specs/`.
 
 ### 2. Explore the application

package/.agent-src/commands/feature/dev.md

@@ -78,15 +78,15 @@ Do NOT use for single-line fixes, trivial changes, or urgent hotfixes.
 ### Phase 5: Implementation
 
 1. **Wait for explicit approval** before writing code.
-2. Create a task list with all implementation steps.
+2. Create a task list with all impl steps.
 3. Follow chosen architecture from Phase 4.
 4. Follow codebase conventions strictly (read guidelines).
 5. Update task list as progress is made.
-6. Write tests alongside the implementation.
+6. Write tests alongside the impl.
 
 ### Phase 6: Quality Review
 
-1. Review the implementation for:
+1. Review the impl for:
    - **Simplicity & DRY** — is the code as simple as possible?
    - **Correctness** — are there logic errors or missing edge cases?
    - **Conventions** — does it follow project patterns?

package/.agent-src/commands/feature.md

@@ -27,7 +27,7 @@ commands with a single entry point + sub-command dispatch.
 ## Workflow ordering
 
 Typical sequence: `explore` → `plan` → `roadmap` → `dev` (or per-step
-implementation). Use `refactor` whenever an existing plan needs an update.
+impl). Use `refactor` whenever an existing plan needs an update.
 
 ## Dispatch
 

package/.agent-src/commands/fix/seeder.md

@@ -63,9 +63,9 @@ where the seeder class is NOT the owner of the data file.
 
 ### Known Exceptions
 
-Currently there are **no exceptions**. All circular dependencies have been resolved.
+Currently there are **no exceptions**. All circular deps have been resolved.
 
-**Pattern for resolving circular dependencies:** Use two-phase seeding. The data file seeds
+**Pattern for resolving circular deps:** Use two-phase seeding. The data file seeds
 records with placeholder values (e.g., empty arrays). The Seeder's `run()` method then updates
 records with the real values using `getReference()`. Since `run()` is called after all seeders
 are initialized, the circular dependency is broken.

package/.agent-src/commands/fix.md

@@ -27,7 +27,7 @@ with a single entry point + sub-command dispatch.
 | `/fix pr-developers` | `commands/fix/pr-developers.md` | Fix and reply to **human** reviewer comments only |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/jira-ticket.md

@@ -72,4 +72,4 @@ suggestion:
 
 ## See also
 
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract (Goal / Plan / Changes / Tests / Open questions)
+- [`role-contracts`](../docs/guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract (Goal / Plan / Changes / Tests / Open questions)

package/.agent-src/commands/judge.md

@@ -23,7 +23,7 @@ commands with a single entry point + sub-command dispatch.
 | `/judge steps` | `commands/judge/steps.md` | Execute an ordered plan step by step, judge gate between steps |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 The standalone reviewer surface lives at [`/review`](review-changes.md).
 
 ## Dispatch
@@ -51,4 +51,4 @@ The standalone reviewer surface lives at [`/review`](review-changes.md).
 
 - [`subagent-orchestration`](../skills/subagent-orchestration/SKILL.md)
 - [`/review`](review-changes.md) — human-oriented self-review (Reviewer-mode contract)
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#reviewer)
+- [`role-contracts`](../docs/guidelines/agent-infra/role-contracts.md#reviewer)

package/.agent-src/commands/memory.md

@@ -24,7 +24,7 @@ commands with a single entry point + sub-command dispatch.
 | `/memory propose` | `commands/memory/propose.md` | Append a provisional signal to the intake stream |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/mode.md

@@ -11,7 +11,7 @@ suggestion:
 
 Sets `roles.active_role` in `.agent-settings.yml` and surfaces the active
 contract before any work. Six modes are defined in
-[`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md):
+[`role-contracts`](../docs/guidelines/agent-infra/role-contracts.md):
 
 - `developer` · `reviewer` · `tester` · `po` · `incident` · `planner`
 
@@ -37,7 +37,7 @@ Anything else: refuse. List the valid values and stop.
 
 ### 2. Validate the mode name
 
-Read [`role-contracts.md`](../../docs/guidelines/agent-infra/role-contracts.md).
+Read [`role-contracts.md`](../docs/guidelines/agent-infra/role-contracts.md).
 Extract H3 headings under `## Contract skeletons` and lowercase them.
 If `<name>` is not in that set, refuse and print the valid list.
 
@@ -62,7 +62,7 @@ exactly what the contract demands.
 ### 5. Write the active role
 
 Update `roles.active_role` in `.agent-settings.yml` using the
-[section-aware merge rules](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
+[section-aware merge rules](../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
 (preserve comments, preserve key order, touch only the changed field).
 
 For `/mode none`: set `active_role: ""`.
@@ -118,7 +118,7 @@ For `/mode` (status only):
 
 ## See also
 
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md) — the six modes
+- [`role-contracts`](../docs/guidelines/agent-infra/role-contracts.md) — the six modes
 - [`role-mode-adherence`](../rules/role-mode-adherence.md) — closing-output gate
-- [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md) — merge rules for settings edits
+- [`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md) — merge rules for settings edits
 - [`ask-when-uncertain`](../rules/ask-when-uncertain.md) — never invent modes

package/.agent-src/commands/module.md

@@ -22,7 +22,7 @@ commands with a single entry point + sub-command dispatch.
 | `/module explore` | `commands/module/explore.md` | Load a module's structure, docs, and context into the conversation |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/onboard.md

@@ -25,7 +25,7 @@ Triggered by the [`onboarding-gate`](../rules/onboarding-gate.md) rule when
 - Change cost profile only → [`/set-cost-profile`](set-cost-profile.md).
 - Single-value edit → ask the agent to change it, or edit
   `.agent-settings.yml` directly. The agent follows the merge rules in
-  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md).
+  [`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md).
 
 ## Preconditions
 
@@ -134,7 +134,7 @@ template — `minimal` + `skill_improvement: true`):
 
 Write `onboarding.onboarded: true` to `.agent-settings.yml` using the
 section-aware merge rules from
-[`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
+[`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
 (preserve comments, key order, touch only the changed fields).
 
 ### 8. Summary
@@ -174,7 +174,7 @@ and stays off unless explicitly enabled.
 
   The log is local-only JSONL — nothing uploaded, nothing shared across
   projects. Reports: ./agent-config telemetry:report
-  Contract + privacy floor: docs/contracts/artifact-engagement-flow.md
+  Contract + privacy floor: .augment/contexts/contracts/artifact-engagement-flow.md
 ```
 
 Skip this block in cloud surfaces (no settings file, no log path).
@@ -200,5 +200,5 @@ local-agent concern; the cloud agent should proceed without invoking it.
 
 - [`onboarding-gate`](../rules/onboarding-gate.md) — rule that triggers this command
 - [`set-cost-profile`](set-cost-profile.md) — isolated profile change
-- [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md) — merge rules for mid-life edits
+- [`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md) — merge rules for mid-life edits
 - [`agent-settings` template](../templates/agent-settings.md) — settings reference

package/.agent-src/commands/optimize/augmentignore.md

@@ -261,7 +261,7 @@ echo "Rules ignored: $rules_count"
 - **Lock files are always ignored** — they're huge and provide zero code insight.
 - **IDE helpers are always ignored** — generated, 20k+ lines, stale quickly.
 - **When in doubt, ignore files** — false positive is easy to fix, false negative wastes tokens silently.
-- **When in doubt, keep skills** — ignoring a needed skill causes bad output, keeping an unneeded one just wastes ~3 lines.
+- **When in doubt, keep skills** — ignoring a needed skill → bad output, keeping an unneeded one just wastes ~3 lines.
 - **Never ignore always-active rules** — only auto-loaded rules (those with `description` frontmatter) may be ignored.
 - **Never ignore meta/agent-system skills** — `agent-docs-writing-writing`, `commands`, `context-create`, `override-management`, `guidelines`, `project-docs`, `roadmap-management`, `naming`, `skill-reviewer`, `file-editor`, `copilot-config`, `copilot-agents-optimization`.
 - **Restore previously ignored skills** when the stack changes (e.g., Vue added to project → restore `vue` skill).

package/.agent-src/commands/optimize-prompt.md

@@ -0,0 +1,61 @@
+---
+name: optimize-prompt
+cluster: optimize
+description: "Optimize a raw prompt for ChatGPT, Claude, Gemini, or another AI via the 4-D methodology — BASIC vs DETAIL auto-detect, one clarifying question per turn, returns the polished prompt."
+disable-model-invocation: true
+skills: [prompt-optimizer]
+suggestion:
+  eligible: true
+  trigger_description: "optimize this prompt, make it better for ChatGPT, rewrite for Claude, sharpen this AI prompt"
+  trigger_context: "user pastes a rough prompt or names a target AI and asks for it to be improved"
+---
+
+# /optimize-prompt
+
+Entry point for the [`prompt-optimizer`](../skills/prompt-optimizer/SKILL.md) skill (persona: **Lyra**). Use when the user wants a polished prompt to paste into an external AI — not when they want the answer that prompt would produce.
+
+## Welcome
+
+On the first turn (or whenever the user invokes `/optimize-prompt` with no prompt body), respond with:
+
+```
+Hi! I'm Lyra, your AI prompt optimizer.
+
+Tell me:
+1. Your target AI — ChatGPT · Claude · Gemini · Perplexity · Other
+2. Your prompt style — DETAIL (I'll ask one question at a time first) or BASIC (I'll apply smart defaults and return the optimized prompt immediately)
+
+Examples
+- "DETAIL using ChatGPT — write me a marketing email"
+- "BASIC using Claude — help with my resume"
+
+Or just paste your rough prompt — I'll auto-detect the mode and announce it.
+```
+
+Render the welcome **once** per session. If the user invokes `/optimize-prompt <prompt>` directly, skip the welcome and run the skill.
+
+## Instructions
+
+### 1. Parse input
+
+Three input shapes:
+
+1. `/optimize-prompt` (no body) → render welcome, wait.
+2. `/optimize-prompt <prompt>` → load the skill, run mode auto-detect, proceed.
+3. `/optimize-prompt DETAIL|BASIC [using <AI>] — <prompt>` → load the skill, honor the explicit mode + target AI, proceed.
+
+### 2. Delegate to the skill
+
+Load [`prompt-optimizer`](../skills/prompt-optimizer/SKILL.md) and follow its `## Procedure` verbatim. The skill owns mode detection, the 4-D methodology, the output format, and gotchas.
+
+### 3. Hand back
+
+After the optimized prompt is delivered, end the turn. Do **not** propose to also execute the optimized prompt. Do **not** offer to commit, push, or save the result to a file — this is conversational output the user copies elsewhere.
+
+## Rules
+
+- **One question per turn** — DETAIL mode iterates; never batch clarifications (`ask-when-uncertain`).
+- **No auto-execution** — produce the prompt, not the answer it would generate, unless the user explicitly asks for both.
+- **No file writes** — the skill is conversational; no commits, no roadmap edits, no `agents/` writes.
+- **Welcome once** — don't re-render the welcome on every turn within the same session.
+- **Mirror the user's language** — the optimized prompt body uses the language the user wrote in; the skill's own scaffolding (mode announcement, "what changed" labels) stays English when the user is in English, German when they're in German (`language-and-tone` Iron Law).

package/.agent-src/commands/optimize.md

@@ -24,7 +24,7 @@ commands with a single entry point + sub-command dispatch.
 | `/optimize rtk` | `commands/optimize/rtk.md` | Create or refine project-local rtk filters |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/override.md

@@ -22,7 +22,7 @@ commands with a single entry point + sub-command dispatch.
 | `/override manage` | `commands/override/manage.md` | Review, update, and refactor existing overrides |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/review-changes.md

@@ -175,7 +175,7 @@ or the equivalent configured command).
 - [`/do-and-judge`](do-and-judge.md) — implementer + judge loop for a single change
 - [`/judge`](judge.md) — standalone judge, no review-changes dispatch
 - [`code-review`](../skills/code-review/SKILL.md) — human-oriented review patterns (tone, feedback handling)
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#reviewer) — Reviewer mode output contract (Summary / Risks / Findings / Required actions / Verdict)
+- [`role-contracts`](../docs/guidelines/agent-infra/role-contracts.md#reviewer) — Reviewer mode output contract (Summary / Risks / Findings / Required actions / Verdict)
 
 ## References
 

package/.agent-src/commands/review-routing.md

@@ -107,7 +107,7 @@ After the block, ask:
 - [`reviewer-awareness`](../rules/reviewer-awareness.md) — role vocabulary
 - [`review-routing-awareness`](../rules/review-routing-awareness.md) —
   data-source rules
-- [`review-routing-data-format`](../../docs/guidelines/agent-infra/review-routing-data-format.md)
+- [`review-routing-data-format`](../docs/guidelines/agent-infra/review-routing-data-format.md)
   — YAML schemas
 - [`create-pr-description`](../skills/create-pr-description/SKILL.md) —
   consumes the routing block

package/.agent-src/commands/roadmap.md

@@ -22,7 +22,7 @@ commands with a single entry point + sub-command dispatch.
 | `/roadmap execute` | `commands/roadmap/execute.md` | Read and interactively execute a roadmap |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/set-cost-profile.md

@@ -25,7 +25,7 @@ the [`agent-settings` template](../templates/agent-settings.md#cost-profiles):
 - For first-run setup use [`/onboard`](onboard.md).
 - For any other single-value change, edit `.agent-settings.yml`
   directly or ask the agent — the merge rules live in
-  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
+  [`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
 - For role modes use [`/mode`](mode.md) — different concept (sets
   `roles.active_role`, not `cost_profile`).
 
@@ -73,7 +73,7 @@ value directly — still echo the old → new line in step 6.
 ### 5. Write the value
 
 Update `cost_profile` in `.agent-settings.yml` using the
-[section-aware merge rules](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
+[section-aware merge rules](../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
 (preserve comments, preserve key order, touch only the changed field).
 
 If the user picked "Keep current", do nothing and stop.
@@ -107,6 +107,6 @@ flip. Cost behaviour on those surfaces is governed by the platform itself.
 ## See also
 
 - [`agent-settings`](../templates/agent-settings.md) — profile matrix and settings reference
-- [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md) — merge rules for settings edits
+- [`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md) — merge rules for settings edits
 - [`onboard`](onboard.md) — first-run setup (includes profile confirmation)
 - [`mode`](mode.md) — role-mode setter (different concept)

package/.agent-src/commands/sync-agent-settings.md

@@ -15,7 +15,7 @@ Reconciles `.agent-settings.yml` with the shipped template
 (`config/agent-settings.template.yml`) and the selected cost-profile
 preset (`config/profiles/{profile}.ini`). Applies the section-aware
 merge rules documented in
-[`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md):
+[`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md):
 
 - Template section order wins — keys reorder to match.
 - Existing user scalar values are preserved.
@@ -129,6 +129,6 @@ is a local-agent concern.
 - [`scripts/sync_agent_settings.py`](../../../scripts/sync_agent_settings.py) — the helper
 - [`config/agent-settings.template.yml`](../../../config/agent-settings.template.yml) — canonical template
 - [`config/profiles/`](../../../config/profiles/) — profile presets
-- [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md) — the merge rules this command enforces
+- [`layered-settings`](../docs/guidelines/agent-infra/layered-settings.md) — the merge rules this command enforces
 - [`scripts/install.py`](../../../scripts/install.py) — first-install path; this command handles the update path
 - [`/sync-gitignore`](sync-gitignore.md) — sibling command for the `.gitignore` block

package/.agent-src/commands/sync-gitignore.md

@@ -11,7 +11,7 @@ suggestion:
 
 Ensures the consumer project's `.gitignore` contains every entry the
 package expects to be ignored (symlinked `.augment/` subdirectories,
-`/agent-config` CLI wrapper, `.agent-settings*`, `.agent-chat-history*`).
+`/agent-config` CLI wrapper, `.agent-settings*`, `agents/.agent-chat-history*`).
 Canonical list lives in `config/gitignore-block.txt`; the same file
 drives the installer, so the two cannot drift.
 

package/.agent-src/commands/tests/create.md

@@ -59,7 +59,7 @@ suggestion:
 - Place tests in the matching directory structure under `tests/` (mirror the source structure).
 - Group related tests with `describe` blocks (Pest) or separate test methods (PHPUnit).
 - Use data providers for testing multiple input/output combinations.
-- Mock external dependencies (database, HTTP, file system) — don't test infrastructure.
+- Mock external deps (database, HTTP, file system) — don't test infrastructure.
 
 ### 6. Verify
 
@@ -70,7 +70,7 @@ suggestion:
 
 - **Do NOT commit or push.**
 - **Quality over quantity** — 5 meaningful tests beat 20 trivial ones.
-- If a class is hard to test (too many dependencies, global state), flag it and suggest a refactoring approach instead of writing brittle
+- If a class is hard to test (too many deps, global state), flag it and suggest a refactoring approach instead of writing brittle
   tests.
 
 ## See also

package/.agent-src/commands/tests.md

@@ -22,7 +22,7 @@ commands with a single entry point + sub-command dispatch.
 | `/tests execute` | `commands/tests/execute.md` | Run PHP tests inside the Docker container |
 
 Sub-command names match the locked contract in
-[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+[`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
 
 ## Dispatch
 

package/.agent-src/commands/threat-model.md

@@ -71,7 +71,7 @@ Produce one combined report with these sections, in order:
 5. **Required controls** — the minimum set of validations, authorization
    checks, logging, and negative tests that must exist before the change ships
 6. **Open questions** — anything the skills flagged as uncertain and the user
-   must answer before implementation starts
+   must answer before impl starts
 
 ### 5. Decide next step
 
@@ -83,7 +83,7 @@ After the report, ask:
 > 3. Stop here — threat model is the deliverable, no implementation yet
 ```
 
-- On **1**: hand off to the implementation flow (e.g., `feature-plan`,
+- On **1**: hand off to the impl flow (e.g., `feature-plan`,
   `bug-fix`, or direct edit) with the required-controls list pinned
 - On **2**: re-gather context and re-dispatch
 - On **3**: save the report as the deliverable, stop
@@ -106,7 +106,7 @@ After the report, ask:
 - NEVER merge `threat-modeling` and `authz-review` outputs into a single
   block — each skill owns its format
 - NEVER write production code in the same turn as this command — the
-  deliverable is the report; implementation is a separate step
+  deliverable is the report; impl is a separate step
 - NEVER mark the change "safe" if any 🔴 abuse case has no control
 
 ## See also
@@ -116,4 +116,4 @@ After the report, ask:
 - [`data-flow-mapper`](../skills/data-flow-mapper/SKILL.md) — trace specific data through the change
 - [`blast-radius-analyzer`](../skills/blast-radius-analyzer/SKILL.md) — enumerate affected call sites
 - [`security-sensitive-stop`](../rules/security-sensitive-stop.md) — the trigger rule
-- [`minimal-safe-diff`](../rules/minimal-safe-diff.md) — keep the implementation scoped
+- [`minimal-safe-diff`](../rules/minimal-safe-diff.md) — keep the impl scoped

package/.agent-src/contexts/authority/commit-mechanics.md

@@ -8,6 +8,19 @@ in autonomous vs. non-autonomous mode.
 **Size budget:** ≤ 3,000 chars. Tracked under Phase 6 of
 `road-to-pr-34-followups`.
 
+## The four commit exceptions — restated
+
+Outside the four below, no commit is allowed and no commit ask is allowed.
+
+1. **User says so this turn** — "commit this now", "commit it", "go
+   ahead and commit". Single commit, not standing.
+2. **Standing instruction not yet revoked** — earlier "commit after
+   every phase"; cache the instruction and commit per its terms.
+3. **Commit command invoked** — `/commit` (split + confirm per commit)
+   or `/commit:in-chunks` (auto-split, Hard Floor still applies).
+4. **Roadmap authorization** — roadmap lists explicit commit steps and
+   the user invoked roadmap execution; each commit matches a step.
+
 ## Hard Floor still applies — bulk deletions and infra changes
 
 Even when one of the four `commit-policy` exceptions authorizes a
@@ -19,7 +32,7 @@ Hard Floor still fires when the diff:
 - Touches Terraform / Pulumi / k8s manifests / Ansible / cloud-config
 
 In those cases, **surface the diff** (paths + counts) and confirm
-this turn before committing — even under `/commit-in-chunks`,
+this turn before committing — even under `/commit:in-chunks`,
 roadmap pre-scan authorization, or an explicit "commit this now". The
 four exceptions cover *whether* commits happen; the Hard Floor covers
 *which diffs* still need a separate confirmation.

package/.agent-src/contexts/authority/destructive-mechanics.md

@@ -9,6 +9,19 @@ context holds everything an agent reaches for once those have fired.
 **Size budget:** ≤ 3,500 chars. Tracked under Phase 7.4 of
 `road-to-pr-34-followups`.
 
+## Iron Law — restatement
+
+The rule's Iron Law ("HARD FLOOR OVERRIDES EVERYTHING") is the universal
+non-destructive-by-default safety net. No autonomy setting, roadmap step,
+or standing instruction can lift it. This is the same Iron Law restated
+in `commit-policy` (row 6 of its trigger table) and in `scope-control`
+(production / infra / bulk-destructive subset).
+
+The trigger surface covers production-branch merges, deploys / releases,
+production data and infrastructure changes, pushes to remote, and
+whimsical or unscoped bulk-destructive operations. Authorization is
+"user said so this turn", never inferred from a previous turn.
+
 ## Bulk deletions during WIP — allowed if task-connected
 
 Deletions inside an **active, user-stated task** are allowed in the
@@ -58,7 +71,7 @@ the diff (paths + counts), get confirmation, then commit.
 - Committing a diff that removes a directory, deletes ≥5 unrelated
   files, or touches Terraform / k8s manifests / Ansible without
   surfacing the diff first — even when [`commit-policy`](../../rules/commit-policy.md)
-  otherwise authorizes commits (e.g. `/commit-in-chunks`, roadmap
+  otherwise authorizes commits (e.g. `/commit:in-chunks`, roadmap
   pre-scan, an explicit "commit this now"). Bulk-deletion / infra
   commits need their own ask, every time.
 - Reading a roadmap step listing files to delete as authorization to

package/.agent-src/contexts/authority/scope-mechanics.md

@@ -35,6 +35,11 @@ concerns:
 A roadmap step or earlier turn does **not** count as authorization
 for these. Authorization is "the user said so on this turn".
 
+Earlier permission for a different operation does **not** carry over —
+permission is per-operation, this-turn. Standing autonomy directives
+narrow other rules but never grant permission for items in this Hard
+Floor subset.
+
 ## Brief-before-asking — separate branch / PR / worktree
 
 If a task seems to need a separate branch or PR (spike, hotfix,