@event4u/agent-config 1.24.0 → 1.26.0

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

@@ -1,76 +0,0 @@
----
-type: "auto"
-tier: "mechanical-already"
-description: "Linking a specific file in agents/council-{questions,responses,sessions}/ from any artifact — council files are gitignored, local-only, auto-pruned; inline the convergence instead"
-alwaysApply: false
-source: package
-triggers:
-  - path_prefix: "agents/council-questions/"
-  - path_prefix: "agents/council-responses/"
-  - path_prefix: "agents/council-sessions/"
-  - intent: "link to council artefact"
-routes_to:
-  - "skill:ai-council"
-validator_ignore:
-  - type: "substring"
-    pattern: ".agent-src.uncompressed/"
-    reason: "Rule references the authoring tree when contrasting transient council files."
----
-
-# No Council References from Any Artifact
-
-Council artefacts under `agents/council-{questions,responses,sessions}/`
-are **gitignored, local-only, and auto-pruned** after
-`ai_council.session_retention_days` (default 7). They are
-disposable scratch — never part of the repo, never visible to a
-reviewer who clones, never durable across the retention window.
-
-A link to a specific council file rots three ways: gitignored
-(not in cloned repo), pruned after retention window (gone even
-locally), and the installed `.augment/` projection cannot follow a
-path that does not exist in the consumer.
-
-## The Iron Law
-
-```
-NEVER LINK TO A SPECIFIC FILE INSIDE
-agents/council-{questions,responses,sessions}/
-FROM ANY ARTIFACT — ROADMAPS INCLUDED.
-INLINE THE CONVERGENCE WITH DATE + MEMBERS, NEVER THE PATH.
-```
-
-Applies to **every** artifact. Council artefacts are more transient
-than roadmaps — the local copy disappears too.
-
-## Forbidden vs allowed
-
-**Forbidden** in any `*.md` / `*.yml` / `*.json` / `*.py`:
-`agents/council-questions/<file>.md`,
-`agents/council-responses/<file>.json`,
-`agents/council-sessions/<file>.json` or `<timestamp>/...`.
-
-**Allowed**: directory mentions (talking about the output convention,
-not a specific file); the `ai-council` skill and `/council:*` commands
-documenting the output path schema; inline convergence summary —
-e.g. *"Council (claude-sonnet-4-5 + gpt-4o, 2026-05-06) converged
-on …"* with date + members, no filepath.
-
-## What to do instead
-
-Identify the durable conclusion (decision, contract, lesson),
-inline a convergence-summary block (members, date, cost if relevant
-— see `ai-council` § Output format), and optionally promote the
-lesson to `agents/contexts/`. The context is durable; the council
-file was the catalyst.
-
-Failure mode: *"I'll just link to the session JSON, it's evidence."*
-The session is gone in 7 days. **Inline first, link never.**
-
-## See also
-
-- [`no-roadmap-references`](no-roadmap-references.md) — sibling rule
-  for the roadmap layer
-- [`augment-source-of-truth`](augment-source-of-truth.md) — edit
-  `.agent-src.uncompressed/`
-- [`ai-council`](../skills/ai-council/SKILL.md) — output path
-  convention and convergence-summary format

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

@@ -1,19 +0,0 @@
----
-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
-triggers:
-  - keyword: "reviewer"
-  - phrase: "risk hotspot"
-  - phrase: "ownership map"
-routes_to:
-  - "skill:review-routing"
----
-
-# Review Routing Awareness
-
-**Iron Law.** Consult ownership-map and historical-bug-patterns before suggesting reviewers or claiming a change is safe.
-
-Body migrated to `skill:review-routing` (per P4 of `road-to-kernel-and-router.md`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/templates/copilot-review-instructions.md

@@ -1,76 +0,0 @@
-# Copilot Code Review — Repository-Specific Suppressions
-
-> Read by GitHub Copilot Code Review (PR bot) when reviewing this repo.
-> Companion to `.github/copilot-instructions.md`. **This file is the
-> path-resolution suppression floor** — it carries the rules Copilot
-> needs to *not* flag, sharply scoped to the agent-config layout.
-
-## Why this file exists
-
-The repo ships agent-config rules, skills, commands, and contexts under
-`.augment/`, `.agent-src/`, and (during authoring) `.agent-src.uncompressed/`.
-Cross-references inside those trees are valid via the **delivered**
-`.augment/` layout — not via raw git checkout. Copilot's static checker
-walks the git tree, so it sees broken paths where there are none.
-
-This is **intentional, not a bug**. The installer (`scripts/install.sh`)
-projects `.agent-src/` → `.augment/` and creates the symlinks that make
-the paths resolve at agent runtime.
-
-## ✅ Known False Positives — Do NOT Flag
-
-### Relative cross-references inside markdown rules / skills / commands
-
-```markdown
-[link](../docs/guidelines/foo.md)
-[link](../contexts/bar.md)
-[link](../docs/guidelines/baz.md)
-```
-
-These resolve from the file's delivered location (e.g.
-`.augment/rules/<rule>.md`). Even when the file is symlinked into
-`.claude/rules/`, `.cursor/rules/`, or `.clinerules/`, the relative
-form is correct by construction.
-
-### `path_prefix:` triggers containing `.agent-src.uncompressed/`
-
-```yaml
-triggers:
-  - path_prefix: ".agent-src.uncompressed/rules/"
-```
-
-This is a **literal match string** for the host's router — *not* a file
-reference. Source-of-truth meta-rules (`augment-source-of-truth`,
-`augment-portability`, `skill-quality`, `docs-sync`,
-`rule-type-governance`) legitimately match against the authoring tree.
-
-### Symlinked rule / skill / command files
-
-Targets resolve into `.augment/rules/`, `.augment/skills/`,
-`.augment/commands/` via installer-managed symlinks. Missing-file
-reports under `.claude/`, `.cursor/`, `.clinerules/` are renderer
-artifacts, not real bugs.
-
-### Body-link forms `../docs/guidelines/...`
-
-Single-up form is the post-rewrite shape produced by
-`scripts/compress.py`. The compressed `.agent-src/rules/` tree is one
-level deeper than the source `.agent-src.uncompressed/rules/`, so the
-rewriter collapses `../../docs/...` to `../docs/...`. Both forms are
-expected — one in source, one in compressed output.
-
-## ✅ What TO flag
-
-- Code defects, security issues, broken tests, type errors — normal
-  review.
-- New `.agent-src.uncompressed/` substrings introduced into
-  `.agent-src/rules/` body content (the `check-compressed-paths` task
-  already gates this — flag it as a regression if it slips through).
-- Rule frontmatter with `load_context:` entries that don't follow the
-  logical-name convention (`contexts/<area>/<file>.md`).
-
-## Pointer
-
-The full architecture is in `docs/architecture.md` § "Path resolution
-and Copilot integration". The compressed-path validator is
-`scripts/check_compressed_paths.py`, wired into `task ci`.