@event4u/agent-config 3.3.0 → 4.2.0

package/.agent-src/rules/augment-edit-discipline.md

@@ -1,11 +1,11 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Editing .augment/ or .agent-src.uncompressed/ — keep files project-agnostic; sync counts and cross-refs on add/rename/delete"
+description: "Editing .augment/ or .agent-src.uncondensed/ — keep files project-agnostic; sync counts and cross-refs on add/rename/delete"
 source: package
 triggers:
   - path_prefix: ".augment/"
-  - path_prefix: ".agent-src.uncompressed/"
+  - path_prefix: ".agent-src.uncondensed/"
   - keyword: "portable"
   - keyword: "rename"
   - keyword: "delete"
@@ -14,8 +14,8 @@ routes_to:
   - "skill:agent-docs-writing"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
-    reason: "Rule scopes the portability gate to the uncompressed authoring tree."
+    pattern: ".agent-src.uncondensed/"
+    reason: "Rule scopes the portability gate to the uncondensed authoring tree."
 workspaces:
   - agent-config-maintainer
 packs:
@@ -32,7 +32,7 @@ install:
 
 # Augment Edit Discipline
 
-**Iron Law (portability).** Files inside `.augment/` and `.agent-src.uncompressed/` MUST stay project-agnostic — no project names, domains, stacks.
+**Iron Law (portability).** Files inside `.augment/` and `.agent-src.uncondensed/` MUST stay project-agnostic — no project names, domains, stacks.
 
 **Iron Law (sync).** On any add / rename / delete of skill / rule / command / guideline, update counts and cross-references in the same edit.
 

package/.agent-src/rules/augment-source-of-truth.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "1"
-description: "Editing files in .agent-src/ or .augment/ — source of truth is .agent-src.uncompressed/; never edit generated dirs directly"
+description: "Editing files in .agent-src/ or .augment/ — source of truth is .agent-src.uncondensed/; never edit generated dirs directly"
 source: package
 load_context:
   - ../contexts/communication/rules-auto/augment-source-of-truth-mechanics.md
@@ -12,7 +12,7 @@ triggers:
   - path_prefix: ".cursor/"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
+    pattern: ".agent-src.uncondensed/"
     reason: "Rule documents the source-of-truth boundary; mentioning the path is its purpose."
 workspaces:
   - agent-config-maintainer
@@ -30,14 +30,14 @@ install:
 
 # Source of Truth
 
-`.agent-src.uncompressed/` is the **single source of truth**. The compressed
+`.agent-src.uncondensed/` is the **single source of truth**. The condensed
 output ships as `.agent-src/`. In the package repo, `.augment/` is a local
 projection of `.agent-src/` for Augment Code (rules copied, rest symlinked).
 Consumer projects still see `.augment/` as the installed runtime tree.
 
 Never edit any of these generated layers directly:
 
-- `.agent-src/` — compressed output shipped in the package
+- `.agent-src/` — condensed output shipped in the package
 - `.augment/` — local projection (gitignored in the package repo; installer
   output in consumer projects)
 - `.claude/`, `.cursor/`, `.clinerules/`, `.windsurfrules` — tool projections
@@ -46,36 +46,36 @@ Never edit any of these generated layers directly:
 
 ```
 NEVER CREATE OR EDIT FILES IN .agent-src/ OR .augment/ DIRECTLY — NOT EVEN "JUST A SMALL FIX".
-ALWAYS WORK IN .agent-src.uncompressed/ — THEN COMPRESS VIA THE /compress COMMAND.
+ALWAYS WORK IN .agent-src.uncondensed/ — THEN CONDENSE VIA THE /condense COMMAND.
 ```
 
 **There are ZERO exceptions to this rule.** Even if:
 
-- You "know" the compressed content is correct
+- You "know" the condensed content is correct
 - It's "just adding a missing section"
-- It's "faster to edit the compressed file directly"
+- It's "faster to edit the condensed file directly"
 - The fix is "trivially obvious"
 
-**STOP. Edit `.agent-src.uncompressed/` first. Always.**
+**STOP. Edit `.agent-src.uncondensed/` first. Always.**
 
-Direct edits to `.agent-src/` break compression hashes, cause CI failures
-("Verify compression hashes" step), and create drift between source and output.
+Direct edits to `.agent-src/` break condensation hashes, cause CI failures
+("Verify condensation hashes" step), and create drift between source and output.
 
-**Compression is ONLY done via the `/compress` command.** The command handles
+**Condensation is ONLY done via the `/condense` command.** The command handles
 hashing, sync verification, and quality checks automatically.
 
 ## Pre-review consistency checkpoints
 
 Before asking for review or creating a PR, verify derived outputs are not stale:
 
-1. Run `bash scripts/compress.sh --changed` — check if `.agent-src.uncompressed/` has changes not yet compressed
-2. If stale files exist: run `/compress` before pushing
+1. Run `bash scripts/condense.sh --changed` — check if `.agent-src.uncondensed/` has changes not yet condensed
+2. If stale files exist: run `/condense` before pushing
 3. Before merge: verify derived outputs (`.agent-src/`, `.augment/`, `.claude/skills/`) are regenerated
 4. Do NOT leave `.agent-src/` stale across review cycles
 
-## Mechanics — workflow, compression rules, commands, symlinks, quick reference
+## Mechanics — workflow, condensation rules, commands, symlinks, quick reference
 
-The authoring workflow, what compression does (and never touches), the
+The authoring workflow, what condensation does (and never touches), the
 commands workflow with required frontmatter, the multi-agent symlink
 mapping, and the per-task quick-reference table live in
 [`contexts/communication/rules-auto/augment-source-of-truth-mechanics.md`](../contexts/communication/rules-auto/augment-source-of-truth-mechanics.md).

package/.agent-src/rules/commit-conventions.md

@@ -25,7 +25,7 @@ install:
 
 # Commit Conventions
 
-**Iron Law.** Use Conventional Commits (`feat:`, `fix:`, `chore:` …); branches `<type>/<short-slug>`; never invent your own format.
+**Iron Law.** Use Conventional Commits (`feat:`, `fix:`, `chore:` …); branches `<type>/<short-slug>`; never invent your own format. Subjects + branch names stay emoji-free per [`no-decorative-emojis-in-git-surfaces`](no-decorative-emojis-in-git-surfaces.md); body emojis allowed only with an in-artifact legend.
 
 Body migrated to `skill:conventional-commits-writing` (per P4 of `road-to-kernel-and-router.md`).
 Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/commit-policy.md

@@ -48,6 +48,16 @@ Anything else → no commit. Hard Floor (bulk deletions, infra changes) still fi
 
 Quoted commit phrases (chat-log paste, log excerpt, roadmap snippet) are **not** permission — see [`commit-mechanics § Speech-act check`](../contexts/authority/commit-mechanics.md).
 
+## Always split into logical chunks — never ask how
+
+```
+COMMIT AUTHORIZED → SPLIT INTO LOGICAL CHUNKS BY DEFAULT.
+NEVER ASK "ONE COMMIT OR MULTIPLE?", "HOW SHOULD I SPLIT?",
+"WHICH CHUNK FIRST?". THE AGENT PICKS THE SPLIT.
+```
+
+One chunk per concern (scope / refactor / rules / config / cleanup), foundation-first. Generated files ride with their source chunk. State the split inline, execute. Full mechanics + carve-outs: [`commit-mechanics § Always split into logical chunks`](../contexts/authority/commit-mechanics.md).
+
 ## NEVER write commit steps into roadmaps unsolicited
 
 When **creating** a roadmap (`/roadmap-create`, `/feature-roadmap`, any roadmap-producing flow) — do **not** include commit steps unless the user explicitly requested them. Commits are a delivery decision; roadmaps plan **work**.

package/.agent-src/rules/domain-adoption-policy.md

@@ -11,10 +11,10 @@ triggers:
   - keyword: "mobile track"
   - keyword: "ml track"
   - keyword: "blockchain track"
-  - path_prefix: ".agent-src.uncompressed/skills/"
+  - path_prefix: ".agent-src.uncondensed/skills/"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
+    pattern: ".agent-src.uncondensed/"
     reason: "Rule names the authoring tree as the gated-entry location for new domain plates."
 workspaces:
   - agent-config-maintainer
@@ -51,7 +51,7 @@ ALL THREE PASS, OR THE ROADMAP MARKS THE DOMAIN GATED.
 ```
 
 The three gates fire before any skill, guideline, command, or rule from the
-domain enters `.agent-src.uncompressed/`. A council session may inform the
+domain enters `.agent-src.uncondensed/`. A council session may inform the
 decision but cannot replace the gate evidence.
 
 ## Gate 1 — Demand signal

package/.agent-src/rules/fast-path-marker-visibility.md

@@ -11,8 +11,8 @@ triggers:
   - intent: "low-impact council dispatch"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
-    reason: "Compressor injects a back-pointer to the uncompressed source for full failure-modes detail."
+    pattern: ".agent-src.uncondensed/"
+    reason: "Condenseor injects a back-pointer to the uncondensed source for full failure-modes detail."
 workspaces:
   - agent-config-maintainer
 packs:
@@ -43,7 +43,7 @@ Markers (from `scripts/ai_council/low_impact.py`):
 - **Split** — `> Low-impact council split — escalating to user (<m1>: X / <m2>: Y):`
 - **Aborted** — `> Low-impact council aborted (token cap) — escalating to user:`
 
-Verbatim = first non-whitespace line, English (no translation), no emoji prefix, no merged numbered-options. Marker is the only audit signal that distinguishes fast-path from local deliberation. See `.agent-src.uncompressed/rules/fast-path-marker-visibility.md` for full failure modes.
+Verbatim = first non-whitespace line, English (no translation), no emoji prefix, no merged numbered-options. Marker is the only audit signal that distinguishes fast-path from local deliberation. See `.agent-src.uncondensed/rules/fast-path-marker-visibility.md` for full failure modes.
 
 ## Failure modes
 

package/.agent-src/rules/finance-safety-floor.md

@@ -79,7 +79,7 @@ Each finance deliverable surfaces, in this order:
 1. **Assumptions block** — every input value the model uses, sourced or marked `assumption`.
 2. **Sensitivity** — at least one variable swept (±20% or ±1 σ); single-point estimates without sensitivity are forbidden for valuation and runway.
 3. **Confidence band** — `high` / `medium` / `low` per the surrounding council / skill conventions, with the reason for the band (data quality, model fit, time horizon).
-4. **Counter-case** — one sentence on what would invalidate the conclusion ("if growth halves, runway compresses to 7 months").
+4. **Counter-case** — one sentence on what would invalidate the conclusion ("if growth halves, runway condenses to 7 months").
 
 ## Human review escalation
 

package/.agent-src/rules/framework-neutrality-in-generic-skills.md

@@ -4,9 +4,9 @@ tier: "2a"
 description: "Editing a generic skill/rule/command — block single-stack mandates; use language-agnostic procedures with carve-out pointers"
 source: package
 triggers:
-  - path_prefix: ".agent-src.uncompressed/skills/"
-  - path_prefix: ".agent-src.uncompressed/rules/"
-  - path_prefix: ".agent-src.uncompressed/commands/"
+  - path_prefix: ".agent-src.uncondensed/skills/"
+  - path_prefix: ".agent-src.uncondensed/rules/"
+  - path_prefix: ".agent-src.uncondensed/commands/"
   - keyword: "FormRequest"
   - keyword: "PHPStan"
   - keyword: "php artisan"
@@ -24,8 +24,8 @@ applies_to_user_types:
   - "maintainer"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
-    reason: "Rule's subject is generic artifacts under .agent-src.uncompressed/; every body link points there by design."
+    pattern: ".agent-src.uncondensed/"
+    reason: "Rule's subject is generic artifacts under .agent-src.uncondensed/; every body link points there by design."
   - type: "substring"
     pattern: "scripts/lint_framework_leakage"
     reason: "Rule cites the enforcing linter script by name in body and enforcement section."
@@ -62,9 +62,9 @@ into surfaces the agent must trigger on regardless of project stack.
 
 This rule fires on edits under:
 
-- `.agent-src.uncompressed/skills/`
-- `.agent-src.uncompressed/rules/`
-- `.agent-src.uncompressed/commands/`
+- `.agent-src.uncondensed/skills/`
+- `.agent-src.uncondensed/rules/`
+- `.agent-src.uncondensed/commands/`
 
 **Exempt** (file or directory name matches — these are correctly
 framework-specific): `laravel*`, `symfony*`, `nextjs*`, `react-*`,

package/.agent-src/rules/git-history-discipline.md

@@ -91,7 +91,7 @@ If either stop fires and resolution is not immediate → tag the state (`git tag
 
 ## Why this rule exists
 
-Interactive rebase + fixup loops generate disproportionate token cost on every iteration: re-running CI per replayed commit, resolving the same content conflict in three derived files (`.compression-hashes.json`, `dist/router.json`, `.windsurfrules`), losing the working tree to a stash that silently re-introduces older state. A single conflict can burn the budget of an entire feature.
+Interactive rebase + fixup loops generate disproportionate token cost on every iteration: re-running CI per replayed commit, resolving the same content conflict in three derived files (`.condensation-hashes.json`, `dist/router.json`, `.windsurfrules`), losing the working tree to a stash that silently re-introduces older state. A single conflict can burn the budget of an entire feature.
 
 A previous session squashed a pushed branch, the push hook failed at the token boundary, the session ended — and the next session saw local and origin pointing at different SHAs for the same logical work. A blind `git pull --rebase` cascaded into conflicts across every derived file. Recovery required forensic SHA-archaeology. The pre/post-rewrite stops make that sequence structurally impossible.
 

package/.agent-src/rules/improve-before-implement.md

@@ -11,7 +11,7 @@ triggers:
   - keyword: "refactor"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
+    pattern: ".agent-src.uncondensed/"
     reason: "Rule cites the authoring tree when describing where examples live."
 workspaces:
   - engineering
@@ -117,5 +117,5 @@ When the request is to create or significantly rewrite a skill, rule, command,
 or guideline, the "fit the existing architecture" check above is handled by
 [`artifact-drafting-protocol`](artifact-drafting-protocol.md)'s Phase B
 (Research). Follow that protocol instead of improvising a one-shot check — it
-scans `.agent-src.uncompressed/` for overlap and reports candidates to extend
+scans `.agent-src.uncondensed/` for overlap and reports candidates to extend
 before creating a new file.

package/.agent-src/rules/language-and-tone.md

@@ -6,7 +6,7 @@ alwaysApply: true
 source: package
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
+    pattern: ".agent-src.uncondensed/"
     reason: "Rule scopes the .md-English mandate to the authoring tree."
 workspaces:
   - agent-config-maintainer
@@ -72,7 +72,7 @@ Examples + wrong-vs-correct: [`language-and-tone-examples`](../docs/guidelines/a
 
 ## `.md` files — ALWAYS English
 
-Every text inside `.md` under `.augment/`, `.agent-src/`, `.agent-src.uncompressed/`, `agents/`: headings, paragraphs, bullets, option labels, prompts, placeholders, ASCII labels, table headers / content. Agent translates at runtime.
+Every text inside `.md` under `.augment/`, `.agent-src/`, `.agent-src.uncondensed/`, `agents/`: headings, paragraphs, bullets, option labels, prompts, placeholders, ASCII labels, table headers / content. Agent translates at runtime.
 
 **Labeled-anchor exception** — quoting German inside English prose is forbidden. Either translate, OR use a labeled `DE: … · EN: …` anchor block (only allowed location for German prose).
 

package/.agent-src/rules/media-governance-routing.md

@@ -25,8 +25,8 @@ validator_ignore:
     pattern: "../../agents/"
     reason: "Routing rule whose subject matter is the project-local agents/settings/policies/media/ tree; every body link points there by design."
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
-    reason: "Rule contrasts project-local placement with the .agent-src.uncompressed/rules/ alternative — mentioning the path is the argument."
+    pattern: ".agent-src.uncondensed/"
+    reason: "Rule contrasts project-local placement with the .agent-src.uncondensed/rules/ alternative — mentioning the path is the argument."
 workspaces:
   - agent-config-maintainer
 packs:
@@ -67,12 +67,12 @@ Any trigger match → agent loads into context:
 
 Each policy carries own trigger block → within active context agent narrows from superset to policies whose specific patterns actually fired (e.g. prompt naming public figure → `public-figures.md` + `disclosure.md`; `--no-disclosure` → `disclosure.md` standalone).
 
-## Why project-local, not `.agent-src.uncompressed/rules/`
+## Why project-local, not `.agent-src.uncondensed/rules/`
 
-Seven media policies live under [`agents/settings/policies/media/`](../../agents/settings/policies/media/), not as `.agent-src.uncompressed/rules/domain-safety-media-*.md`, for three reasons:
+Seven media policies live under [`agents/settings/policies/media/`](../../agents/settings/policies/media/), not as `.agent-src.uncondensed/rules/domain-safety-media-*.md`, for three reasons:
 
 1. **Consumed by skills + adapters**, not surfaced as standalone always-loaded prose. Cost non-trivial (7 × ~80 lines = ~560 lines always-context if hoisted to rules), and most sessions never touch video / image / voice surface.
-2. **Enforcement model project-local** — working precedent (`/ghostwriter:*` mandatory footer in `write-engine.md`) + audit log (session transcripts) are project artifacts. Rules under `.agent-src.uncompressed/` are tool-portable governance; these policies are domain-specific bindings.
+2. **Enforcement model project-local** — working precedent (`/ghostwriter:*` mandatory footer in `write-engine.md`) + audit log (session transcripts) are project artifacts. Rules under `.agent-src.uncondensed/` are tool-portable governance; these policies are domain-specific bindings.
 3. **Extraction to reusable domain pack explicitly deferred** until second non-video domain (audio, image, docs, exports) lands with overlapping execution surfaces. Until then, one-domain abstraction structurally premature — policies stay project-local, routing rule on-demand bridge.
 
 This routing rule is the bridge: sits in always-loaded rule set so trigger keywords surface project-local policies into context on demand, without paying full always-loaded cost.

package/.agent-src/rules/no-attribution-footers.md

@@ -62,4 +62,5 @@ re-fetch to verify. Other writing commands SHOULD adopt the same pass.
 
 [`/create-pr`](../commands/create-pr.md) ·
 [`commit-conventions`](commit-conventions.md) ·
+[`no-decorative-emojis-in-git-surfaces`](no-decorative-emojis-in-git-surfaces.md) — sibling rule covering decorative emojis in the same surfaces ·
 [`scope-control`](scope-control.md).

package/.agent-src/rules/no-cheap-questions.md

@@ -75,6 +75,9 @@ Silent, before any numbered-options block. Any "yes" → don't ask:
 8. Mandate active + "weiter? / continue?" — IL 4, pick next item.
 9. Prereq for user-authorized action? IL 5, execute silently.
 10. Destination (branch / PR) already named? IL 6, never re-ask.
+11. Cleanup of gitignored / auto-pruned / TTL-managed artefact? Self-managing — state inline, never offer.
+12. Numbered option contains a commit-message body, "message preview", or "Vorschlag falls Du committen willst"? Disguised commit ask — `commit-policy` violation, drop it.
+13. Commit authorized + asking "one commit or multiple?", "how should I split?", "which chunk first?"? Forbidden — `commit-policy § Always split into logical chunks`. Pick the split, state inline, execute.
 
 Pick dominant path, state inline assumption, hand back. Genuine ambiguity → [`ask-when-uncertain`](ask-when-uncertain.md).
 

package/.agent-src/rules/no-decorative-emojis-in-git-surfaces.md

@@ -0,0 +1,111 @@
+---
+type: "auto"
+tier: "3"
+alwaysApply: false
+description: "Generating PR/issue/commit titles or PR/issue comments — forbids decorative emojis; allowed in PR/issue descriptions + commit bodies only when matched by an in-artifact legend"
+source: package
+triggers:
+  - intent: "PR title"
+  - intent: "PR body"
+  - intent: "commit message"
+  - intent: "issue title"
+  - intent: "post PR comment"
+  - keyword: "gh pr create"
+  - keyword: "git commit"
+workspaces:
+  - agent-config-maintainer
+  - engineering
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
+---
+
+# No Decorative Emojis in Git Surfaces
+
+## Iron Law
+
+```
+NEVER ADD DECORATIVE EMOJIS TO PR / ISSUE / COMMIT TITLES OR
+TO PR / ISSUE COMMENTS. NEVER ADD UNIVERSAL-BLACKLIST EMOJIS
+(🤖 🚀 🎉 ✨ 🔥 💡 👍 ❤️) ANYWHERE — TITLE OR BODY.
+DECORATIVE EMOJIS IN PR / ISSUE DESCRIPTIONS OR COMMIT BODIES
+ARE ALLOWED ONLY WHEN A LEGEND IN THE SAME ARTIFACT DEFINES
+EVERY EMOJI USED. NO LEGEND → NO EMOJI.
+EXCEPTION: USER EXPLICITLY ASKED FOR IT THIS TURN.
+```
+
+Decorative = visual flair, ranking, mood, "look how fancy". Functional emojis below stay allowed.
+
+## Surfaces — what this gates
+
+Always blocked (titles + free-standing comments):
+
+- PR titles (`gh pr create --title`, `octokit.pulls.create`, PATCH).
+- Issue titles (`gh issue create`, `octokit.issues.create`, PATCH).
+- Commit subject (first line of `git commit -m` / message file).
+- Branch names.
+- Standalone PR / issue comments (`gh pr comment`, `gh issue comment`,
+  `octokit.issues.createComment`) — covers everything `no-pr-progress-comments`
+  lets through (review-replies, user-invoked comment flows).
+
+Body-only, legend-gated:
+
+- PR / issue descriptions (body of create / PATCH payload).
+- Commit body (lines below the blank-line subject separator).
+
+## Universal blacklist — forbidden even with a legend
+
+```
+🤖 🚀 🎉 ✨ 🔥 💡 👍 ❤️ 🤗 😊 (and skin-tone / variant forms)
+```
+
+"Look how fancy" / empathy classes from `direct-answers`. Self-attribution (🤖) is the punkpeye PR (#6865 title-emoji spam) pattern. No legend rescues them.
+
+## Legend carve-out — when body emojis ARE allowed
+
+All three must hold for the same artifact:
+
+1. Body contains a `Legend:` (or `Legende:`) block on its own line defining every decorative emoji used elsewhere in the body.
+2. Emojis carry **information** (language tag, OS marker, hosting class) — not pure decoration. Example punkpeye-#6865 body:
+   `📇 TypeScript · ☁️ Cloud · 🏠 Local · 🍎 macOS · 🪟 Windows · 🐧 Linux`.
+3. No universal-blacklist emoji appears (above list always wins).
+
+Body emojis without a legend → strip before posting / committing.
+
+## Whitelist — always allowed, no legend
+
+- CLI / agent-status markers: `❌` `✅` `⚠️` (literal status).
+- Mode markers from `role-mode-adherence`.
+- Roadmap checkbox glyphs (`[x]` `[~]` `[-]`) in fenced code or quoted roadmap excerpts — not emojis, no carve-out needed.
+
+## Server-side re-injection
+
+Host AI client or tool wrapper re-injects 🤖 / 🎉 into a title or comment after creation (analog to the `Pull Request opened by …` injection in `no-attribution-footers`) → same mitigation: re-fetch after create, regex-strip, PATCH if changed, re-fetch to verify.
+
+## Failure modes — what counts as a violation
+
+- `feat: 🚀 ship the unified setup wizard` — emoji in commit subject.
+- PR title `🤖 Update dependencies` — title-emoji spam (punkpeye #6865).
+- Comment body `🎉 All checks green now!` — decorative comment.
+- PR body with `Status: 🟢 Ready` — no legend, no carve-out.
+- Branch `feat/🔥-new-thing` — emoji in ref name.
+- Body legend present but body also uses 🤖 — universal blacklist wins.
+
+## See also
+
+- [`no-attribution-footers`](no-attribution-footers.md) — sibling rule on
+  the same surfaces; covers the `🤖 Generated with …` footer class.
+- [`no-pr-progress-comments`](no-pr-progress-comments.md) — gates *whether*
+  to post a comment at all; this rule gates the *form* of any comment
+  that does get posted.
+- [`commit-conventions`](commit-conventions.md) — Conventional Commits
+  format; this rule narrows the allowed character set in the subject.
+- [`direct-answers`](direct-answers.md) § Emoji Scope — chat-reply analog;
+  same emoji classes, different surface.

package/.agent-src/rules/no-pr-progress-comments.md

@@ -0,0 +1,118 @@
+---
+type: "auto"
+tier: "2a"
+alwaysApply: false
+description: "Posting comments on an open PR — refuses unsolicited progress / status / CI-fix narration unless personal.pr_progress_comments is true"
+source: package
+triggers:
+  - intent: "post PR comment"
+  - intent: "PR status update"
+  - intent: "CI fix progress"
+  - keyword: "gh pr comment"
+  - keyword: "PullRequestComment"
+workspaces:
+  - agent-config-maintainer
+  - engineering
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
+---
+
+# No Unsolicited PR Progress Comments
+
+## Iron Law
+
+```
+NEVER POST UNSOLICITED PROGRESS / STATUS / CI-FIX COMMENTS ON A PR
+WHEN `personal.pr_progress_comments` IS FALSE (DEFAULT).
+EXCEPTION: USER-INVOKED FLOWS ALWAYS RUN.
+EXCEPTION: USER EXPLICITLY ASKED FOR IT THIS TURN.
+```
+
+Reading `.agent-settings.yml`:
+
+- Missing key / not set → treat as `false`.
+- `personal.pr_progress_comments: false` (default) → gate fires.
+- `personal.pr_progress_comments: true` → gate inert, agent may comment.
+
+## What this gates — and what it does NOT
+
+**Gated** (do not post when the setting is `false`):
+
+- "CI fix iteration #N" status comments narrating what the agent did.
+- "Blocked on X" status notices the agent posts unprompted.
+- "All checks green now" celebration comments.
+- Any `gh pr comment` / `octokit.pulls.createReview` / equivalent the
+  agent decides to fire mid-loop without an explicit ask.
+
+**Not gated** (always allowed regardless of the setting):
+
+- The PR body / description in [`/create-pr`](../commands/create-pr.md) and
+  in PATCH-after-create strip passes — that text *is* the PR.
+- Replies to individual review comments via
+  [`/fix:pr-comments`](../commands/fix/pr-comments.md),
+  [`/fix:pr-developer-comments`](../commands/fix/pr-developer-comments.md),
+  and [`/fix:pr-bot-comments`](../commands/fix/pr-bot-comments.md) —
+  the user invoked the command, that is the explicit ask.
+- Comments the user explicitly requested this turn ("post a comment
+  on PR #244 explaining the workflow-scope block").
+- Comments from a slash-command flow the user invoked
+  (`/council:pr`, `/code-review --comment`, etc.).
+
+If unsure whether the planned comment qualifies as gated:
+**treat it as gated**. The user can flip the setting once if they
+want progress narration; a missed unsolicited comment is recoverable,
+a noisy PR thread is not.
+
+## What to do instead when the gate fires
+
+State the progress in the **chat reply**, not on the PR. Examples:
+
+- "Fixed the schema lint; force-pushed `b17c4ef8`. Node Tests still
+  blocked on the workflow-scope edit (diff in working tree, needs
+  maintainer push)."
+- "CI cycle 3/3 green except for Node Tests; same blocker as before."
+
+The chat reply reaches the user with the same information. The PR
+stays clean for reviewers.
+
+## Failure modes — what counts as a violation
+
+- Posting "CI status update" comments during an autonomous CI-fix loop.
+- Re-running `gh pr comment` after a previous unsolicited comment was
+  posted (compounding the noise).
+- Narrating the diff of the next push in a PR comment — diffs belong
+  in commit messages.
+- Posting "I noticed you opened this PR — here's my analysis" without
+  a `/code-review` invocation.
+
+## Carve-out: surfacing safety-critical info
+
+If the agent uncovers a security / data-loss / production-impact
+issue that the reviewer needs to see **before** they read the diff
+and posting a chat reply alone risks the message being missed, treat
+this as an explicit safety surface and:
+
+1. Post the comment **and** state in the chat reply that the gate was
+   bypassed for safety.
+2. Cite the rule + the carve-out in the comment body so the reviewer
+   knows why the agent broke the default silence.
+
+Routine CI status, refactor progress, and "this might interest you"
+notes do **not** clear this carve-out.
+
+## See also
+
+- [`/create-pr`](../commands/create-pr.md) — PR body / description path (not gated).
+- [`/fix:pr-comments`](../commands/fix/pr-comments.md) — review-reply path (not gated).
+- [`no-attribution-footers`](no-attribution-footers.md) — sibling rule on PR-comment hygiene.
+- [`no-decorative-emojis-in-git-surfaces`](no-decorative-emojis-in-git-surfaces.md) — sibling rule gating decorative emojis in any comment that does get posted.
+- [`scope-control`](scope-control.md) — git-ops permission gate (PR creation).
+- `personal.pr_progress_comments` in `config/agent-settings.template.yml`.

package/.agent-src/rules/no-roadmap-references.md

@@ -15,7 +15,7 @@ routes_to:
   - "skill:ai-council"
 validator_ignore:
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
+    pattern: ".agent-src.uncondensed/"
     reason: "Rule contrasts the authoring tree with transient layers."
 workspaces:
   - agent-config-maintainer
@@ -71,7 +71,7 @@ These paths must not appear inside a stable artifact:
   `agents/runtime/council/responses/<file>.json`,
   `agents/runtime/council/sessions/<file>.json` or `<timestamp>/...`
 
-Stable artifact = any file under `.agent-src.uncompressed/{rules,
+Stable artifact = any file under `.agent-src.uncondensed/{rules,
 skills,commands,contexts,templates,personas}/`, `agents/settings/contexts/`,
 `docs/guidelines/`, `docs/contracts/`, `docs/architecture.md`,
 `docs/customization.md`, `docs/getting-started.md`, `docs/catalog.md`,
@@ -145,6 +145,6 @@ Failure modes:
 - [`roadmap-progress-sync`](roadmap-progress-sync.md) — sync dashboard
   on roadmap touch
 - [`augment-source-of-truth`](augment-source-of-truth.md) — edit
-  `.agent-src.uncompressed/`
+  `.agent-src.uncondensed/`
 - [`ai-council`](../skills/ai-council/SKILL.md) — output path
   convention and convergence-summary format

package/.agent-src/rules/non-destructive-by-default.md

@@ -47,7 +47,7 @@ Standing "just keep going" + next step crosses the floor → STOP, surface what'
 
 ## Not in scope — deterministic regeneration
 
-Output regenerated from a tracked source (compression, code-gen, formatter passes, lock-file rebuilds) is reversible from source — **not destructive**. Lives in [`autonomous-execution § Trivial`](autonomous-execution.md#trivial--just-act-do-not-ask). Per-file diff approval is theater.
+Output regenerated from a tracked source (condensation, code-gen, formatter passes, lock-file rebuilds) is reversible from source — **not destructive**. Lives in [`autonomous-execution § Trivial`](autonomous-execution.md#trivial--just-act-do-not-ask). Per-file diff approval is theater.
 
 ## Bulk deletions during WIP — allowed if task-connected
 

package/.agent-src/rules/persona-governance.md

@@ -4,7 +4,7 @@ tier: "2a"
 description: "Creating/editing/proposing personas — enforce per-domain cap (≤ 2 specialists), ≥ 1 skill citation, deprecation path"
 source: package
 triggers:
-  - path_prefix: ".agent-src.uncompressed/personas/"
+  - path_prefix: ".agent-src.uncondensed/personas/"
   - path_prefix: ".agent-src/personas/"
   - keyword: "persona"
   - keyword: "personas"
@@ -22,8 +22,8 @@ validator_ignore:
     pattern: "../../docs/"
     reason: "Rule routes to docs/contracts/persona-schema.md and docs/personas.md — the canonical persona catalog and schema live there by design."
   - type: "substring"
-    pattern: ".agent-src.uncompressed/"
-    reason: "Rule documents the persona authoring tree (.agent-src.uncompressed/personas/) as the deprecation-path operand."
+    pattern: ".agent-src.uncondensed/"
+    reason: "Rule documents the persona authoring tree (.agent-src.uncondensed/personas/) as the deprecation-path operand."
 workspaces:
   - agent-config-maintainer
 packs: