@event4u/agent-config 2.26.0 → 3.1.0

package/.agent-src/skills/readme-reviewer/SKILL.md

@@ -7,6 +7,18 @@ execution:
   type: assisted
   handler: internal
   allowed_tools: []
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # readme-reviewer
@@ -55,7 +67,7 @@ Inspect truth-defining files:
 - Config files, tests, existing docs
 
 Verify: install steps exist, commands work, features are implemented,
-deps are real.
+dependencies are real.
 
 ### 3. Validate installation and setup
 
@@ -141,8 +153,54 @@ Structure checks:
 → See `docs/guidelines/docs/readme-size-and-splitting.md` for full thresholds,
 splitting strategies, and anti-patterns.
 
+### 9. Validate every link and detect orphans — MANDATORY
+
+For every internal link in the README:
+
+1. Resolve the path. `test -f` files, `test -d` directories. Strip
+   `#anchor` and `?query` before the check.
+2. For every anchor link (`file.md#section`), grep the target file for
+   the heading slug. Missing slug = broken anchor.
+3. Group findings:
+   - **broken** — target does not exist (❌ Critical)
+   - **anchor-broken** — file exists, anchor does not (⚠️ Major)
+   - **path-drift** — target moved but a valid path exists elsewhere
+     (⚠️ Major, propose the corrected path)
+
+For every documentation file referenced by the README, check whether
+it has any **other** references in the repo (`grep -r` over
+`AGENTS.md`, `docs/`, `.agent-src*/`, `.augment/`, `packages/`).
+Files referenced only by this README are **single-use** — note them
+so they can be moved or inlined later.
+
+For every doc under `/docs/` that the README **does not** link, check
+whether anything else in the repo links it. Files with zero inbound
+references are **orphan-candidates** — surface them, never delete
+silently.
+
+### 10. Currency check — drift detection
+
+The README may have been correct at write-time but drifted since.
+Compare the README's claims to the live repository:
+
+- **Counts** (badges like "Skills: 218") — recount from the source tree
+  and flag any drift > 0
+- **Commands** — every documented `task`, `npm run`, `npx`, or `bash`
+  call must exist in `Taskfile.yml`, `package.json scripts`, or the
+  named script file at its claimed path
+- **Profiles / user-types / packs** — list members against the live
+  directory listing
+- **Version pins** — runtime, framework, peer-dep versions stated in
+  README vs. the manifest's `engines` / `require` / `dependencies`
+- **Visual identity** — banner / hero image references resolve to real
+  files (not 404s in GitHub rendering)
+
 ## Output format
 
+1. Produce three subsections in order: Summary, Findings, Confidence; no prose outside them.
+2. Findings table must use the severity vocabulary (❌ Critical / ⚠️ Major / ℹ️ Minor) and cite the exact section name.
+3. Close the report with a *Confidence* block that separates confirmed-correct, needs-verification, and unclear-due-to-missing-context.
+
 ### 1. Summary
 
 | Field | Value |
@@ -156,8 +214,11 @@ splitting strategies, and anti-patterns.
 | # | Severity | Section | Issue | Fix |
 |---|---|---|---|---|
 | 1 | ❌ Critical | Install | Command `X` does not exist | Replace with `Y` |
-| 2 | ⚠️ Major | Usage | Example uses deprecated API | Update to current API |
-| 3 | ℹ️ Minor | Structure | Requirements buried below usage | Move above install |
+| 2 | ❌ Critical | Profile grid | Link `.agent-src.uncompressed/profiles/` 404s | Repoint to `packages/core/.agent-src.uncompressed/profiles/` |
+| 3 | ⚠️ Major | Badges | "Skills: 218" — live count is 207 | Update badge or note drift |
+| 4 | ⚠️ Major | Usage | Example uses deprecated API | Update to current API |
+| 5 | ℹ️ Minor | Structure | Requirements buried below usage | Move above install |
+| 6 | ℹ️ Minor | Docs | `docs/foo.md` only linked by README | Either inline or keep as standalone |
 
 Severity levels:
 

package/.agent-src/skills/readme-writing/SKILL.md

@@ -7,6 +7,18 @@ execution:
   type: assisted
   handler: internal
   allowed_tools: []
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # readme-writing
@@ -37,9 +49,34 @@ the intended audience. Reflects the real repository — not assumptions.
 - **Strong quickstart over exhaustive noise** — a reader should get started in 30 seconds
 - **Right scope** — high-level overview in README, deep content in dedicated docs
 - **Match the repo type** — a package README differs from an app, CLI tool, or framework
+- **Re-analyze every time** — never trust cached knowledge of the repo; the README that drifted yesterday is the README the model wrote from memory
+- **Preserve existing visual identity** — banner, badges, profile/role grids, official logo lockups stay byte-identical unless the user explicitly asks to change them
 
 ## Procedure
 
+### 0. Re-analysis gate — MANDATORY before any writing
+
+Before drafting a single line, run a fresh repository inspection in **this**
+session. Do not rely on prior knowledge, prior turns, or the existing README
+prose. Produce an explicit evidence ledger:
+
+```
+ledger:
+  package:      <name + version from manifest>
+  description:  <verbatim from manifest>
+  cli_entry:    <bin / entry from manifest, if any>
+  commands:     <list of real commands from Taskfile / Makefile / package.json scripts>
+  install:      <verified install path(s) from scripts/install.* or docs>
+  doc_targets:  <list of /docs files actually linked from the new draft>
+  counts:       <skills / rules / commands / personas / advisors — if surfaced as badges>
+  visual_keep:  <line range of existing README header, banner, badge block to preserve>
+```
+
+If any cell is unknown, run `ls`, `grep`, `find`, or read the file before
+writing — never invent. If the user asks to "use the existing banner",
+locate the exact source lines and reproduce them byte-for-byte, including
+the surrounding HTML.
+
 ### 1. Identify README type and audience
 
 Determine repository type:
@@ -127,26 +164,49 @@ for install, first example, or requirements).
 splitting strategies (reference-split, deep-link tables, collapsibles),
 multi-audience handling, and anti-patterns.
 
-### 7. Validate
+### 7. Validate links and detect orphans — MANDATORY
+
+For every internal link in the new draft:
+
+1. Resolve the path. If it points to a file, `test -f` the path. If a
+   directory, `test -d`. Strip `#anchor` and `?query` before the check.
+2. For every anchor link (`file.md#section`), grep the target file for
+   the heading slug. Missing anchor = broken link.
+3. Build the **link-delta** between the old README and the new one:
+   - **kept**: linked in both
+   - **added**: only linked by the new README
+   - **dropped**: only linked by the old README
+
+For every `dropped` target, search the rest of the repository
+(`grep -r "<path>"` over `AGENTS.md`, `docs/`, `.agent-src*/`,
+`.augment/`, `packages/`). If no other file references it, mark
+**orphan-candidate**. Surface the list to the user — do not delete
+silently.
+
+### 8. Validate
 
 After writing, verify:
 
 - [ ] Every documented command exists in the repo (`Taskfile.yml`, `Makefile`, `package.json scripts`, etc.)
 - [ ] Setup steps are reproducible (no missing prerequisites)
 - [ ] No features or capabilities are invented
-- [ ] First screen answers: what, why, how-to-start
+- [ ] **First screen contract** — within the first ~40 lines: project name, one-sentence pitch, install command (or pointer), and the primary CTA
+- [ ] Banner, badges, and any explicit "preserve" block from Step 0 are byte-identical to source
 - [ ] No dead sections (heading with 1-2 trivial sentences)
 - [ ] Scope is right — deep content moved to dedicated docs, not crammed in
 - [ ] Size below the "overloaded" threshold, or splitting is in place (see size guideline)
 - [ ] ToC present if README > 150 lines or > 6 top-level sections
 - [ ] Matches existing tonality if repo has established voice
-- [ ] All file paths and references are valid
+- [ ] Every internal link resolved per Step 7 — zero broken file or anchor links
+- [ ] Orphan-candidate list produced even if empty
 
 ## Output format
 
 1. Full README draft
 2. Short note: detected repo type + audience
-3. Any uncertainties or assumptions that need confirmation
+3. **Link delta** — `kept` / `added` / `dropped` with orphan-candidates flagged
+4. Evidence ledger (Step 0) so the user can audit assumptions
+5. Any uncertainties or assumptions that need confirmation
 
 ## Gotcha
 

package/.agent-src/skills/readme-writing-package/SKILL.md

@@ -7,6 +7,18 @@ execution:
   type: assisted
   handler: internal
   allowed_tools: []
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # readme-writing-package
@@ -36,9 +48,33 @@ what it does, whether it fits their stack, how to install it, and how to use it.
 - **Compatibility must be explicit** — don't imply broad support without evidence
 - **First code example must be real, minimal, and verified** — no pseudo-code
 - **README = onboarding, /docs = reference** — keep README focused
+- **Re-analyze every time** — never write from cached knowledge; verify the manifest, source, and CI matrix in this session
+- **Preserve existing visual identity** — banner, badges, hero images, and logo lockups stay byte-identical unless the user explicitly asks to change them
 
 ## Procedure
 
+### 0. Re-analysis gate — MANDATORY before any writing
+
+Before drafting, produce an evidence ledger from a fresh inspection of
+the package — manifest, source, CI, examples. Do not rely on prior turns
+or the existing README prose.
+
+```
+ledger:
+  package:       <name + version from manifest>
+  description:   <verbatim from manifest>
+  install_cmd:   <verified against the manifest's package manager>
+  requirements:  <language version, framework version, ext-*, services>
+  public_api:    <entry classes / functions / exports from source>
+  test_command:  <real command from manifest scripts / Taskfile>
+  doc_targets:   <list of /docs files actually linked from the new draft>
+  visual_keep:   <line range of existing README header / banner / badges to preserve>
+```
+
+If any cell is unknown, run `ls`, `grep`, `find`, or read the file before
+writing — never invent. When the user asks to keep the existing banner
+or badge row, reproduce it byte-for-byte from the source.
+
 ### 1. Identify package type and audience
 
 | Type | Audience | README focus |
@@ -51,7 +87,7 @@ what it does, whether it fits their stack, how to install it, and how to use it.
 
 ### 2. Inspect package truth sources
 
-Read files that define actual package behavior:
+Read and **verify** files that define actual package behavior (confirm each claim against the source — never paraphrase from memory):
 
 - Manifest: `composer.json`, `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, or `*.gemspec` — name, description, requirements, scripts
 - Source entrypoints — public API surface, main classes/functions
@@ -243,7 +279,21 @@ capability comparison. They serve different jobs — install vs. coverage.
 
 README = enough to adopt. Docs = enough to master.
 
-### 8. Validate
+### 8. Validate links and detect orphans — MANDATORY
+
+For every internal link in the new draft:
+
+1. Resolve the path. `test -f` files, `test -d` directories. Strip
+   `#anchor` and `?query` before the check.
+2. For every anchor link, grep the target for the heading slug.
+3. Build the **link-delta** vs. the old README — `kept` / `added` /
+   `dropped`. For every `dropped` target, search the rest of the repo
+   (`grep -r` over `AGENTS.md`, `docs/`, `.agent-src*/`, `packages/`).
+   No other reference → mark **orphan-candidate**.
+
+Surface the orphan-candidate list to the user — never delete silently.
+
+### 9. Validate
 
 - [ ] Install command is correct and complete
 - [ ] Compatibility/requirements match the manifest (`composer.json`, `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `*.gemspec`) and the CI matrix
@@ -254,15 +304,20 @@ README = enough to adopt. Docs = enough to master.
 - [ ] Deep content is in docs, not README (see size guideline)
 - [ ] Multi-platform install uses a table, not stacked blocks
 - [ ] No duplication between README and `/docs/`
-- [ ] First screen shows: what, install, requirements
+- [ ] **First screen contract** — within ~40 lines: name, one-sentence pitch, install command, requirements (or pointer)
+- [ ] Banner / badges / hero from Step 0 visual_keep are byte-identical to source
+- [ ] Every internal link resolved per Step 8 — zero broken file or anchor links
+- [ ] Orphan-candidate list produced even if empty
 
 ## Output format
 
 1. Full README draft
 2. Detected package type + audience
 3. Compatibility summary
-4. Uncertainties needing confirmation
-5. Suggested follow-up docs if README would become too large
+4. **Link delta** — `kept` / `added` / `dropped` with orphan-candidates flagged
+5. Evidence ledger (Step 0) so the user can audit assumptions
+6. Uncertainties needing confirmation
+7. Suggested follow-up docs if README would become too large
 
 ## Gotcha
 

package/.agent-src/skills/receiving-code-review/SKILL.md

@@ -5,6 +5,18 @@ personas:
   - critical-challenger
 source: package
 domain: process
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # receiving-code-review

package/.agent-src/skills/refine-prompt/SKILL.md

@@ -11,6 +11,18 @@ execution:
   type: assisted
   handler: internal
   allowed_tools: []
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Refine Prompt
@@ -284,4 +296,4 @@ For `low`, the question replaces the AC list:
 - [`work_engine.scoring.confidence`](../../templates/scripts/work_engine/scoring/confidence.py) — rubric + band thresholds
 - [`ask-when-uncertain`](../../rules/ask-when-uncertain.md) — one-question-per-turn Iron Law
 - [`artifact-drafting-protocol`](../../rules/artifact-drafting-protocol.md) — this skill was drafted under it
-- AI Council session: `agents/council-responses/prompt-master-mini.json` (2026-05-17) — analysis behind the mini/max split and `/raw` bypass <!-- council-ref-allowed: ADR decision trace -->
+- AI Council session: `agents/runtime/council/responses/prompt-master-mini.json` (2026-05-17) — analysis behind the mini/max split and `/raw` bypass <!-- council-ref-allowed: ADR decision trace -->

package/.agent-src/skills/refine-ticket/SKILL.md

@@ -14,6 +14,18 @@ execution:
   type: assisted
   handler: internal
   allowed_tools: []
+workspaces:
+  - product
+packs:
+  - product-basic
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # Refine Ticket
@@ -151,7 +163,7 @@ in this skill folder) and returns:
 - `threat-modeling` — fires on any auth / webhook / upload / queue /
   secret / tenant / admin / PII / payment keyword, or a `CVE-YYYY-N`
   regex match.
-- `repo_aware` — on when `.git/`, `agents/contexts/`, `composer.json`,
+- `repo_aware` — on when `.git/`, `agents/settings/contexts/`, `composer.json`,
   or `package.json` is present in the cwd; off otherwise.
 - When `repo_aware=True`, `decision.repo_context` is populated by
   `gather_repo_context()`:
@@ -159,7 +171,7 @@ in this skill folder) and returns:
     convention signal).
   - `recent_commits` — up to 30 most recent commit subjects (active
     modules + verb conventions).
-  - `context_docs` — every `agents/contexts/*.md` filename (domain
+  - `context_docs` — every `agents/settings/contexts/*.md` filename (domain
     vocabulary).
 - Outside a repo the context is empty — the skill produces the same
   output shape, minus repo-specific citations (graceful degrade).

package/.agent-src/skills/refine-ticket/detection-map.yml

@@ -110,12 +110,12 @@ sub_skills:
 repo_aware:
   description: >
     When invoked inside a repo clone, /refine-ticket loads
-    agents/contexts/ for domain vocabulary and scans recent branches /
+    agents/settings/contexts/ for domain vocabulary and scans recent branches /
     commits for naming conventions. Outside a repo, skip silently.
   signals:
     - path: .git
       type: dir
-    - path: agents/contexts
+    - path: agents/settings/contexts
       type: dir
     - path: composer.json
       type: file

package/.agent-src/skills/release-comms/SKILL.md

@@ -7,8 +7,18 @@ source: package
 domain: product
 context_spine: [product, team]
 recommended_for_user_types: [creator, gtm, founder]
-
-
+workspaces:
+  - gtm
+packs:
+  - gtm-marketing
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # release-comms

package/.agent-src/skills/repomix-packer/SKILL.md

@@ -3,6 +3,18 @@ name: repomix-packer
 description: "Use when packaging a codebase to a single AI-friendly file for LLM analysis — local or remote, XML/Markdown/JSON, token counting, gitignore filtering, peer-side `repomix` CLI."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 > **Pinned upstream:** `repomix` CLI (npm: `repomix`, brew: `repomix`). Re-verify per minor bump. Repomix is an **optional dependency** — this skill never installs it silently.
@@ -132,5 +144,5 @@ Cite the snapshot path so the consumer skill can read it.
 
 - Upstream tool: https://github.com/yamadashy/repomix (MIT).
 - Adopted from: `Microck/ordinary-claude-skills@8f5c83174f7aa683b4ddc7433150471983b93131:skills_all/repomix/SKILL.md` (MIT, © 2025 Microck) — wrapper-style adoption, no upstream code vendored.
-- Provenance registry: `agents/contexts/skills-provenance.yml` (entry: `repomix`).
+- Provenance registry: `agents/settings/contexts/skills-provenance.yml` (entry: `repomix`).
 - Iron-Law floor: `non-destructive-by-default`, `missing-tool-handling`, `tool-safety`.

package/.agent-src/skills/requesting-code-review/SKILL.md

@@ -5,6 +5,18 @@ personas:
   - critical-challenger
 source: package
 domain: process
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # requesting-code-review

package/.agent-src/skills/retention-loops/SKILL.md

@@ -6,6 +6,18 @@ tier: senior
 source: package
 domain: product
 context_spine: [product, customer-segment, funnel-stage]
+workspaces:
+  - product
+packs:
+  - product-basic
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # retention-loops

package/.agent-src/skills/review-routing/SKILL.md

@@ -3,6 +3,18 @@ name: review-routing
 description: "Use when preparing a PR description, suggesting reviewers, or flagging risk — produces owner-mapped roles plus historical bug-pattern matches from project-local YAML."
 source: package
 domain: quality
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # review-routing

package/.agent-src/skills/rice-prioritization/SKILL.md

@@ -5,6 +5,18 @@ status: active
 tier: senior
 source: package
 domain: product
+workspaces:
+  - product
+packs:
+  - product-basic
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # rice-prioritization

package/.agent-src/skills/risk-officer/SKILL.md

@@ -6,6 +6,18 @@ personas:
   - senior-engineer
 source: package
 domain: quality
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # risk-officer

package/.agent-src/skills/roadmap-management/SKILL.md

@@ -3,6 +3,18 @@ name: roadmap-management
 description: "Use when the user says "create roadmap", "show roadmap", or "execute roadmap". Creates, reads, and manages roadmap files with phase tracking."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # roadmap-manager

package/.agent-src/skills/roadmap-writing/SKILL.md

@@ -3,6 +3,18 @@ name: roadmap-writing
 description: "Use when authoring or rewriting a roadmap in agents/roadmaps/ — phase prose, goal sentence, acceptance criteria, council notes — even when the user just says 'write a plan for X' or 'draft a roadmap'."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 <!-- cloud_safe: degrade -->

package/.agent-src/skills/rtk-output-filtering/SKILL.md

@@ -7,6 +7,18 @@ execution:
   type: assisted
   handler: shell
   allowed_tools: []
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # rtk (Rust Token Killer)

package/.agent-src/skills/rule-refactor/SKILL.md

@@ -3,6 +3,18 @@ name: rule-refactor
 description: "Use when the rule set is over the Augment budget, when a new rule would breach it, or when asked to audit / merge / prune rules — runs the audit pipeline and proposes a verdict per rule."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 <!-- cloud_safe: degrade -->
@@ -45,12 +57,12 @@ python3 scripts/measure_rule_budget.py --json > /tmp/rule-budget-before.json
 The audit infrastructure already exists — compose it:
 
 ```bash
-python3 scripts/audit_auto_rules.py      # → agents/reports/auto-rules-audit.{json,md}
+python3 scripts/audit_auto_rules.py      # → agents/runtime/reports/auto-rules-audit.{json,md}
 python3 scripts/audit_overlap.py         # → appends overlap pairs to the MD
-python3 scripts/audit_likelihood.py      # → agents/reports/auto-rules-likelihood.json
+python3 scripts/audit_likelihood.py      # → agents/runtime/reports/auto-rules-likelihood.json
 ```
 
-Then read `agents/reports/auto-rules-audit.md` end-to-end.
+Then read `agents/runtime/reports/auto-rules-audit.md` end-to-end.
 
 ### 3. Categorise every flagged rule
 

package/.agent-src/skills/rule-writing/SKILL.md

@@ -3,6 +3,18 @@ name: rule-writing
 description: "Use when creating or editing a rule in .agent-src.uncompressed/rules/ — trigger wording, always vs auto classification, size budget — even when the user just says 'add a rule for X'."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 <!-- cloud_safe: degrade -->
@@ -174,7 +186,7 @@ Forward-only: the new check applies to **the rule under review** and
 to **future** edits. The baseline table is informational so reviewers
 can distinguish genuine debt from acceptable carry-overs without
 diffing the full lint output. See
-`agents/analysis/lint-warning-triage.md` for the 3-bucket reference.
+`agents/evidence/analysis/lint-warning-triage.md` for the 3-bucket reference.
 
 ## Frontmatter shape