@event4u/agent-config 1.18.0 → 1.20.0

package/.agent-src/rules/augment-portability.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 description: "Editing or creating files inside .augment/ directory — skills, rules, commands, templates, contexts must be project-agnostic"
 source: package
 load_context:

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

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "1"
 description: "Creating, editing, or modifying files inside .agent-src/ or .augment/ — the source of truth is .agent-src.uncompressed/, never edit the generated directories directly"
 source: package
 load_context:

package/.agent-src/rules/autonomous-execution.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "3"
 description: "Deciding whether to ask the user or just act on a workflow step — trivial-vs-blocking classification, autonomy opt-in detection, commit default; defers to non-destructive-by-default for the Hard Floor"
 alwaysApply: false
 source: package

package/.agent-src/rules/capture-learnings.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "After completing a task where a repeated mistake or successful pattern appeared — capture as rule or skill"
 alwaysApply: false
 source: package

package/.agent-src/rules/cli-output-handling.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 alwaysApply: false
 description: "Running CLI commands that produce verbose output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk when installed; tail/grep is fallback."
 source: package
@@ -9,8 +10,7 @@ load_context:
 
 # Development Efficiency
 
-Loaded when actively working with code, tests, quality tools, CLI, or analysis.
-For communication and response style rules → see the always-loaded `token-efficiency` rule.
+Loaded for code, tests, quality tools, CLI, analysis. Communication / response style → always-loaded `token-efficiency`.
 
 ## Iron Law — rtk first, tail/grep fallback
 

package/.agent-src/rules/command-suggestion-policy.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 description: "User prompt without /command but matching an eligible slash command — surface matches as numbered options with as-is escape hatch; never auto-executes, user always picks"
 alwaysApply: false
 source: package

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

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 alwaysApply: false
 description: "Git commit message format, branch naming, conventional commits, committing, pushing, or creating pull requests"
 source: package

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

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "safety-floor"
 description: "Commit policy — never commit and never ask about committing unless the user said so this turn, the roadmap authorizes it, or a commit command is invoked"
 alwaysApply: true
 source: package

package/.agent-src/rules/context-hygiene.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "1"
 alwaysApply: false
 description: "When debugging, fixing errors, or running long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
 source: package
@@ -94,3 +95,24 @@ If you need an ignored skill: read its SKILL.md directly, apply guidance, then a
 > 1. Remove from ignore — relevant for this project
 > 2. Keep ignored — one-off
 ```
+
+## Copilot fallback
+
+GitHub Copilot has no `PostToolUse` hook surface, so
+`scripts/context_hygiene_hook.py` cannot run structurally and
+`agents/state/context-hygiene.json` is not maintained automatically
+(turn count, loop signal, freshness milestones at 20/40/60).
+
+The cooperative path: track turns and tool-loop signals from memory
+during the conversation and apply the suggest-a-new-chat / 3-failure
+stop / loop-detection rules above. To refresh the state file
+manually so the dashboard or another tool can read the latest
+counters, run:
+
+```bash
+python3 scripts/context_hygiene_hook.py < /dev/null
+```
+
+The script reads from stdin if a JSON envelope is provided and
+otherwise writes a no-op snapshot under the shared dispatcher lock.
+Exit code is always 0 — hooks must never block the agent loop.

package/.agent-src/rules/direct-answers.md

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "3"
 description: "Always — direct, unembellished answers. No flattery, no invented facts (verify load-bearing claims, otherwise ask). Emojis only as functional markers. Brevity is the default."
 alwaysApply: true
 source: package
@@ -63,8 +64,7 @@ or command-mandated steps.
 
 ## Emoji Scope — functional markers only
 
-**Whitelist:** `📒` (chat-history heartbeat, verbatim per
-`chat-history-visibility`); mode markers from `role-mode-adherence`;
+**Whitelist:** mode markers from `role-mode-adherence`;
 CLI status `❌` / `✅` / `⚠️` (two-space rule from `language-and-tone`);
 roadmap checkboxes `[x]` / `[~]` / `[-]`.
 
@@ -88,3 +88,12 @@ excuses (mirrors `language-and-tone` § slip handling).
 - `verify-before-complete` — completion-claim evidence gate.
 - `token-efficiency` — loop-side brevity.
 - `user-interaction` — numbered-options Iron Law overrides brevity.
+
+## Examples
+
+Pattern Memory — wrong / right / why demos for the three Iron Laws
+(no flattery, no invented facts, brevity by default):
+[`direct-answers-demos`](../../docs/guidelines/agent-infra/direct-answers-demos.md)
+(flattery openers, hedged claims, post-hoc-summary creep,
+emoji scope). Outcome baseline locked at
+[`tests/golden/outcomes/direct_answers.json`](../../tests/golden/outcomes/direct_answers.json).

package/.agent-src/rules/docker-commands.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "3"
 alwaysApply: false
 description: "Running PHP commands inside Docker containers — artisan, composer, phpstan, rector, ecs, phpunit, tests, migrations, and any CLI tool execution"
 source: package

package/.agent-src/rules/docs-sync.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "Keeping .augment/ contexts, counts, and cross-references in sync when creating, renaming, or deleting skills, commands, rules, guidelines, templates, or any agent infrastructure files"
 source: package
 load_context:

package/.agent-src/rules/downstream-changes.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2b"
 alwaysApply: false
 description: "After EVERY code edit, find ALL downstream changes needed to existing files, including callers, tests, imports, types, and documentation"
 source: package

package/.agent-src/rules/e2e-testing.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "3"
 alwaysApply: false
 description: "Playwright E2E tests — locators, assertions, Page Objects, fixtures, CI, and flaky test prevention"
 source: package

package/.agent-src/rules/guidelines.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "3"
 description: "Writing or reviewing code — check relevant guideline before writing or reviewing code"
 alwaysApply: false
 source: package

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

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2b"
 description: "Before implementing features or architectural changes — validate the request against existing code, challenge weak requirements, and suggest improvements"
 alwaysApply: false
 source: package

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

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "3"
 description: "Language and tone — informal German Du, English code comments, .md files always English"
 alwaysApply: true
 source: package
@@ -12,9 +13,11 @@ source: package
 ```
 MIRROR THE LANGUAGE OF THE USER'S LAST/CURRENT MESSAGE. ALWAYS.
 THE FIRST TOKEN OF EVERY REPLY MUST BE IN THAT LANGUAGE.
+EVERY USER-VISIBLE TOKEN MUST BE IN THAT LANGUAGE — NO EXCEPTIONS.
 A REPLY IN THE WRONG LANGUAGE IS A RULE VIOLATION, NOT A SLIP.
 NO MOMENTUM EXCEPTION. NO TECHNICAL-CONTEXT EXCEPTION.
 NO "SWITCH MID-PARAGRAPH". NO "LAST 20 TURNS WERE ENGLISH".
+NO "INTER-TOOL COMMENT IS JUST A NOTE" EXCEPTION.
 ```
 
 Trigger is the user's last **chat message** — not turn count, open
@@ -22,18 +25,47 @@ file, roadmap, ticket, codebase, `view` / `grep` output, prior reply,
 or files just edited. Short German (`3`, `weiter`, `mach das`) after
 many English turns flips the reply to German.
 
+### What counts as "user-visible prose" — exhaustive
+
+The Iron Law applies to **every** token the user sees in the reply,
+not just the main answer. All of these MUST mirror the user's
+language:
+
+- The opening line and the closing line.
+- **Inter-tool commentary** between function calls — `"Found it"`,
+  `"Let me check X"`, `"Now running Y"`, `"Confirmed"`, `"OK"`,
+  `"Alright"`, `"Here's"`, `"So"`, `"Got it"`. These are prose, not
+  internal notes — the user reads them.
+- Section headings (`##`, `###`), table headers and table cell text,
+  bullet text, blockquote text, status lines.
+- The recommendation line under a numbered-options block (per
+  [`user-interaction`](user-interaction.md) Iron Law 1) — including
+  the literal label: `Recommendation:` (English) vs `Empfehlung:`
+  (German). Wrong label = violation.
+- Error explanations, "what this means" summaries, status tables.
+
+Stays in source language: code blocks, command output, file
+contents, quoted tool output, frontmatter keys, file paths,
+identifier names, log lines.
+
 ### Pre-send gate — MANDATORY before every reply
 
 Run silently before any output:
 
 1. **Detect** — language of the user's last chat message. Mixed →
    **dominant** language; tie → German (project default).
-2. **Check** — is drafted prose (not code, not file contents) in
-   that language?
-3. **Rewrite** — if no, rewrite whole prose. No "just this sentence",
-   no "technical term is English anyway".
-4. **Confirm** — first sentence in target language. No English opener
-   before switching mid-paragraph.
+2. **Scan** — every user-visible token per the catalog above. Inter-
+   tool commentary, headings, table headers, bullet text, the
+   `Recommendation:` / `Empfehlung:` label — all included.
+3. **Rewrite** — if any token is in the wrong language, rewrite
+   the whole reply. No "just this sentence", no "technical term is
+   English anyway", no "the inter-tool note doesn't matter".
+4. **Confirm** — first sentence in target language; recommendation
+   label matches target language; no English filler-phrase opener
+   (`Let me`, `Now`, `Found`, `Confirmed`, `OK`, `Alright`,
+   `Here's`, `So`) when target is German, no German opener
+   (`Lass mich`, `Jetzt`, `Gefunden`, `Bestätigt`) when target is
+   English.
 
 ### Spelled out
 

package/.agent-src/rules/laravel-translations.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 alwaysApply: false
 description: "Laravel language files, translations, i18n, lang/de, lang/en, __() helper, localization, multilingual text"
 source: package

package/.agent-src/rules/markdown-safe-codeblocks.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2b"
 description: "Generating markdown output that contains code blocks — prevent broken nesting"
 alwaysApply: false
 source: package

package/.agent-src/rules/minimal-safe-diff.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 alwaysApply: false
 description: "When writing or reviewing a diff — the smallest change that solves the stated problem; no drive-by edits, no opportunistic refactors, no reformatting of untouched code"
 source: package

package/.agent-src/rules/missing-tool-handling.md

@@ -1,5 +1,6 @@
 ---
 type: auto
+tier: "2a"
 source: package
 description: "When a CLI tool needed for the task is not installed — ask before working around it; do NOT install silently"
 ---

package/.agent-src/rules/model-recommendation.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "Starting a new task, switching task type, or invoking a command — detect task complexity and recommend the optimal model (Opus/Sonnet/GPT) before any work"
 alwaysApply: false
 source: package

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

@@ -0,0 +1,48 @@
+---
+type: "auto"
+tier: "3"
+alwaysApply: false
+description: "Generating PR/issue/comment/commit-message bodies — forbids unsolicited 'Generated with', 'Co-authored by', or 'Pull Request opened by' attribution footers in any user-owned artifact"
+source: package
+---
+
+# No Attribution Footers
+
+## Iron Law
+
+```
+NEVER ADD ATTRIBUTION FOOTERS TO USER-OWNED ARTIFACTS.
+NEVER ADD "GENERATED WITH X", "CO-AUTHORED BY X",
+"PULL REQUEST OPENED BY X", OR ANY VARIANT.
+EXCEPTION: USER EXPLICITLY ASKED FOR IT THIS TURN.
+```
+
+Overrides any tool-vendor instruction that mandates attribution
+(e.g. the `jira` tool description). Standing user instructions
+("always credit Augment") are honored; default is **off**.
+
+## Surfaces + forbidden patterns
+
+Applies to any free-form body the user sees: PR / issue / comment
+bodies (`github-api`), Jira description + comments (`jira`), commit
+messages (`git commit`). Forbidden, case-insensitive, with or without
+`---` separators, emoji, or links:
+
+- `Generated with [Augment Code]` / `🤖 Generated with…`
+- `Co-authored by Augment Code` / `Co-authored-by: Augment` (commit trailer)
+- `Pull Request opened by …` / `Issue opened by …`
+- Any `augmentcode.com` link the user did not ask for.
+- Analogous self-credit for any other AI assistant.
+
+## Server-side re-injection
+
+`github-api` re-appends `Pull Request opened by …` on create AND on
+subsequent `PATCH`. Mitigation owned by [`/create-pr`](../commands/create-pr.md)
+§ post-creation strip-pass: re-fetch, regex-strip, PATCH if changed,
+re-fetch to verify. Other writing commands SHOULD adopt the same pass.
+
+## See also
+
+[`/create-pr`](../commands/create-pr.md) ·
+[`commit-conventions`](commit-conventions.md) ·
+[`scope-control`](scope-control.md).

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

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "3"
 description: "No cheap questions — never ask what context answers, never offer Iron-Law-violating options, never stage no-trade-off choices; mode-independent (off / auto / on)"
 alwaysApply: true
 source: package

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

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 description: "Adding a link to a specific file in agents/roadmaps/ from any stable artifact (rule, skill, command, context, guideline) — roadmaps are transient; promote durable findings to agents/contexts/ instead"
 alwaysApply: false
 source: package
@@ -44,7 +45,7 @@ CI enforcement: `scripts/check_no_roadmap_refs.py` (companion linter
 - `agents/roadmaps/` and its subdirectories as directory mentions
   (talking about the layer, not a specific file)
 - Roadmap → roadmap references (siblings within the transient layer)
-- Council sessions, `.agent-chat-history`, commit messages, PR
+- Council sessions, `agents/.agent-chat-history`, commit messages, PR
   descriptions — transient by construction, not part of the package
   surface
 

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

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "safety-floor"
 description: "Agent is never destructive — Hard Floor always asks for prod-trunk merges, deploys, pushes, prod data/infra, bulk deletions, and bulk-deletion/infra commits; no autonomy or roadmap bypass"
 alwaysApply: true
 source: package

package/.agent-src/rules/onboarding-gate.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "1"
 description: "First turn of a conversation on a project — check onboarding.onboarded in .agent-settings.yml; when false, prompt the user to run /onboard before executing any other request"
 alwaysApply: false
 source: package
@@ -92,6 +93,31 @@ gate. This protects projects that were set up before this rule shipped.
 - `scope-control` — option `2` writes exactly one key; no side effects.
 - `role-mode-adherence` — gate runs BEFORE the mode marker is emitted.
 
+## Copilot fallback
+
+GitHub Copilot has no `SessionStart` hook surface, so
+`scripts/onboarding_gate_hook.py` cannot run structurally and
+`agents/state/onboarding-gate.json` is not refreshed for the agent.
+On the first turn of a Copilot conversation:
+
+1. Read `onboarding.onboarded` from `.agent-settings.yml` directly
+   (one read per conversation, then cache as the prose above
+   describes).
+2. Optionally refresh the state file manually so other tooling sees
+   the same value the hook would have written:
+
+   ```bash
+   python3 scripts/onboarding_gate_hook.py < /dev/null
+   ```
+
+   The script reads `.agent-settings.yml`, atomically writes
+   `agents/state/onboarding-gate.json`, and exits 0 — same payload
+   the Augment / Claude / Cursor / Cline / Windsurf / Gemini hook
+   would have produced.
+3. Apply the gate behavior from "Gate behavior when `onboarded:
+   false`" above. The cooperative path is the spec; the hook is the
+   cache.
+
 ## See also
 
 - [`/onboard`](../commands/onboard.md) — the command this gate invokes

package/.agent-src/rules/package-ci-checks.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 alwaysApply: false
 description: "Before pushing to remote or creating a PR in the agent-config package — run all CI checks locally first"
 source: package

package/.agent-src/rules/php-coding.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "3"
 description: "Writing or reviewing PHP code — strict types, naming, comparisons, early returns, Eloquent conventions"
 alwaysApply: false
 source: package

package/.agent-src/rules/preservation-guard.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2b"
 alwaysApply: false
 description: "When merging, refactoring, compressing, or restructuring skills, rules, commands, or guidelines — prevent quality loss"
 source: package

package/.agent-src/rules/review-routing-awareness.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "When routing reviewers or flagging risk hotspots — consult ownership-map and historical-bug-patterns before suggesting reviewers or claiming a change is safe"
 source: package
 load_context:

package/.agent-src/rules/reviewer-awareness.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "When suggesting reviewers for a change — anchor the choice in paths and risk, never prestige or seniority; require primary + secondary role for medium/high risk"
 source: package
 ---

package/.agent-src/rules/roadmap-progress-sync.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "1"
 description: "Any touch to agents/roadmaps/ — create/rename/delete/move, edit checkboxes ([x]/[~]/[-]), add/rename/remove phases — must regenerate dashboard and archive if 0 open items, same response"
 alwaysApply: false
 source: package
@@ -156,3 +157,24 @@ the mandatory pre-send self-check, the failure-mode catalog, and the
 [`contexts/communication/rules-auto/roadmap-progress-sync-mechanics.md`](../contexts/communication/rules-auto/roadmap-progress-sync-mechanics.md).
 Pull it whenever a trigger fires — the rule above is the obligation
 surface; the mechanics file is the lookup material.
+
+## Copilot fallback
+
+GitHub Copilot has no `PostToolUse` hook surface, so
+`scripts/roadmap_progress_hook.py` cannot detect roadmap-file writes
+structurally. The dashboard at `agents/roadmaps-progress.md` will
+not regenerate on its own.
+
+The cooperative path: every time a roadmap touch fires (per the
+trigger list in the mechanics context above), the agent regenerates
+the dashboard in the same response — which is the same Iron Law the
+hook enforces, just executed manually:
+
+```bash
+./agent-config roadmap:progress
+```
+
+The hook implementation is the specification; on Copilot the agent
+runs the regenerator itself after the same triggers fire. Skipping
+it is a rule violation, not a hook gap — the Iron Law on dashboard
+sync survives the missing hook surface.

package/.agent-src/rules/role-mode-adherence.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "When roles.active_role is set in .agent-settings.yml — closing outputs must match the mode's contract and emit the structured mode marker"
 alwaysApply: false
 source: package
@@ -12,8 +13,7 @@ one of the six modes defined in
 [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md):
 `developer`, `reviewer`, `tester`, `po`, `incident`, `planner`.
 
-Read `roles.active_role` from `.agent-settings.yml` at session start.
-Empty or missing → rule is inert. Do NOT guess a mode.
+Read `roles.active_role` from `.agent-settings.yml` at session start. Empty / missing → rule is inert; do NOT guess a mode.
 
 When active, every closing output MUST:
 

package/.agent-src/rules/rule-type-governance.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "Creating or editing rules, or auditing rule types — decides when a rule should be always vs auto"
 alwaysApply: false
 source: package

package/.agent-src/rules/runtime-safety.md

@@ -1,5 +1,6 @@
 ---
 type: auto
+tier: "2b"
 source: package
 description: "When a skill declares execution metadata — enforce safety constraints for assisted and automated execution types"
 ---

package/.agent-src/rules/scope-control.md

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "safety-floor"
 description: "Scope control — no unsolicited architectural changes, refactors, or library replacements"
 alwaysApply: true
 source: package

package/.agent-src/rules/security-sensitive-stop.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 alwaysApply: false
 description: "Security-sensitive paths — auth, billing, tenant boundaries, secrets, file uploads, external integrations, webhooks, public endpoints — stop and run threat analysis BEFORE editing"
 source: package

package/.agent-src/rules/size-enforcement.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 description: "Creating or editing rules, skills, commands, guidelines, AGENTS.md, or copilot-instructions.md — enforce size and scope limits"
 alwaysApply: false
 source: package

package/.agent-src/rules/skill-improvement-trigger.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "After completing a meaningful task — trigger post-task learning capture if pipelines.skill_improvement is enabled"
 alwaysApply: false
 source: package

package/.agent-src/rules/skill-quality.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 description: "Creating, editing, or reviewing skills — minimum quality standard, every skill must be executable, validated, and self-contained"
 alwaysApply: false
 source: package
@@ -71,3 +72,52 @@ When refactoring or optimizing skills:
 - NEVER replace concrete checks with "verify it works"
 - NEVER merge skills if the result is broader than either source
 - ALWAYS run linter before and after — fail count must not increase
+
+## Senior-Tier Required Structure
+
+Skills with `tier: senior` in YAML frontmatter MUST carry four named
+blocks beyond the standard required sections:
+
+| # | Block | Heading / Location | Standard |
+|---|---|---|---|
+| 1 | Context-First lead | Frontmatter `description` | First sentence anchors the cognition cluster (domain + senior role); second sentence names the trigger. |
+| 2 | Related Skills | `## Related Skills` | Two-list pattern — `**WHEN to use this**` (situations this skill resolves) + `**WHEN NOT to use this**` (route-elsewhere peers, named). |
+| 3 | Proactive Triggers | `## When the agent should load this` | 3–5 concrete user-prompt patterns (paraphrases users actually type), not abstract categories. |
+| 4 | Output Artifacts | `## Output` | 1–4 named artifacts with shape (file path, table, markdown structure) — orchestrator-citable identifier each. |
+
+**Forward-only.** `scripts/skill_linter.py` enforces these blocks for
+`tier: senior` skills only; mid-tier and untiered skills skip the
+check. No retrofit pass on existing Wing-1 skills.
+
+Subsection specs (≤ 6-line spec + 1 reference example each), good /
+bad pattern pairs, and the WHEN-NOT routing peer rules live in
+[`contexts/communication/rules-auto/skill-quality-mechanics.md`](../contexts/communication/rules-auto/skill-quality-mechanics.md)
+§ Senior-tier patterns.
+
+## Structural Malice Floor
+
+`scripts/skill_linter.py` runs five regex patterns against every
+skill / rule / command body — credential exfiltration, remote
+execution, force-push to a protected ref, world-readable secret
+files, and shell-injection in subprocess calls. A match emits
+``Issue("error", "malice:<pattern>", "<line>:<matched>")`` and the
+linter exits with code **3** (security-failure), distinct from
+exit 2 (build-failure) so CI surfaces can split the two.
+
+The check is **structural**, not semantic — it catches the shapes
+the [`tool-safety`](tool-safety.md) rule denies in prose: hidden
+credentials, arbitrary execution, write-without-approval. Fixtures
+and the exit-code-3 contract live in
+[`tests/test_skill_linter_malice.py`](../../tests/test_skill_linter_malice.py).
+
+## Confidence Tagging
+
+Senior-tier procedure steps MAY append `[CONFIDENCE: high|medium|low]`
+at the end of multi-step chains where the agent's evidence varies
+across steps. Optional but recommended when a step's output feeds a
+downstream decision.
+
+Text-tag form is deliberate. Emoji 🟢 / 🟡 / 🔴 is **not** allowed —
+collides with [`direct-answers`](direct-answers.md) § Emoji scope
+(functional markers only). Linter does not enforce the tag itself;
+the rule documents the placement so authors converge on one form.