AGENTS.md

@@ -38,14 +38,14 @@ Fall back to raw shell only when no skill covers it.
 - **A `.apm/` edit is not live in this session until it is pushed.** The six dependencies resolve from the holocron remote, unpinned against the default branch. `apm install` deploys from the lock; `apm update` is what re-resolves refs.
 - **The ADR-0020 skill gates ship hot, with no baseline.** 26 of 39 descriptions and 9 of 39 bodies exceed their FAIL tier, and the `Kyberforge.CompositionNote` Vale rule fires 10 errors across `gitea-issues`, `gitea-labels-milestones`, `gitea-prs` and `gitea-workflow`. Editing any of those skills *for any reason* means retrofitting it to the contract first — a one-line fix cannot be committed until the skill complies. Deliberate; tracked as Gitea issue #99. `skill-size-check` will not warn you about the Vale half, so check both: `pre-commit run --all-files`.
 - **Run `bash tests/run-tests.sh --strict` before considering any change done.** Keep the flag: without it a suite whose dependency is missing exits 77 and is counted SKIPPED rather than failed, so the run goes green having verified less than it claims.
-- **Before pushing, run the whole gate locally:** `pre-commit run --hook-stage pre-push --all-files`. Pushing runs 14 repo-defined hooks, not just the test suite.
+- **Before pushing, rehearse the gate locally:** `pre-commit run --hook-stage pre-push --all-files`. It runs the 14 pre-push hooks this repo authors itself plus pre-commit's 2 `meta` hooks, so it prints 16; `check-release-needed` passes without checking anything, because it needs a real push to `main`. `docs/spec/gates.md` reconciles both.
 - **Pushing without a network** needs `SKIP=apm-marketplace-check,apm-pack-check-clean git push` — those two resolve a remote marketplace entry via `git ls-remote`. Skip only those two; the rest are real local checks, and adding one to `SKIP` disarms it silently.
 - **Author commits with `git-commits`** — it validates Conventional Commits, which `commit-msg` enforces.
 - **This repo and Gitea are the only source of truth.** All project state, decisions, and working conventions live here. Do not use an external memory system for this project — cached state diverges from the repo and you get a split brain. Before answering any design or architecture question, check `docs/adr/` for an existing decision.
 
 ## Key documents
 
-Read `CONTEXT.md` at the start of every session — it is this repo's domain language, and the terms in it are used unglossed everywhere else.
+Read `CONTEXT.md` at the start of every session — it is this repo's domain glossary, and the terms it defines are used unglossed everywhere else. It is not exhaustive: terms it does not carry are defined at their point of use, mostly in `docs/spec/`.
 
 Read these on demand:
 

CONTEXT.md

@@ -69,10 +69,10 @@ plugin's `.apm/` tree so hosts that convention-scan those paths discover the con
 _Avoid_: generated copy, duplicate tree
 
 **Output profile**:
-An `apm pack` target format for a generated manifest; apm has `claude`
+An `apm pack` target format for a generated *marketplace* manifest; apm has `claude`
 (`.claude-plugin/marketplace.json`) and `codex` (the differently-shaped
-`.agents/plugins/marketplace.json`) and none for Copilot CLI's legacy path, which a sync script
-mirrors instead. Mechanics: `docs/spec/architecture.md`.
+`.agents/plugins/marketplace.json`), and none for `.github/plugin/marketplace.json` (Copilot CLI's
+legacy path), which a sync script mirrors instead. Mechanics: `docs/spec/architecture.md`.
 _Avoid_: build target, export format
 
 **Plugin marketplace**:
@@ -160,8 +160,9 @@ The directory a gate resolves against — the nearest ancestor of the file being
 _Avoid_: repo root, project root
 
 **Near-miss**:
-A sibling skill or agent whose plausible queries share keywords with this one but need something
-different — the only thing a boundary clause should exclude.
+A query that shares keywords with this skill but needs a different one — and, by extension, the
+sibling that would wrongly answer it; boundary clauses exist to exclude genuine near-misses rather
+than to enumerate siblings. Detail: `skill-audit/references/description-quality.md`.
 _Avoid_: overlap, similar skill
 
 **Vacuous green**:

README.md

@@ -18,8 +18,8 @@ Content ships as six installable plugins, each an apm (Agent Package Manager) pa
 The six plugins:
 
 - **kyberforge** — skills and agents for creating, maintaining, and managing a Claude Code / Copilot CLI plugin marketplace
-- **git** — conventional commits, branches, history, submodules, worktrees, remotes, and pre-commit hook authoring and running (`pc-author` / `pc-run`)
-- **gitea** — issues, pull requests, labels, milestones, releases, branches, files
+- **git** — conventional commits, branches, history, submodules, worktrees, remotes, pre-commit hook authoring and running (`pc-author` / `pc-run`), and an interactive router (`git-workflow`)
+- **gitea** — issues, pull requests, labels, milestones, releases, branches, files, and an interactive router (`gitea-workflow`)
 - **core** — authoring and auditing a repo's `AGENTS.md` and the provider adapter files that defer to it
 - **lint** — configuring and running linters
 - **bin** — cross-cutting workflow skills not yet split into a focused plugin: research, documentation, TDD, prototyping, triage, diagnosis, architecture review, requirement grilling, compressed output (`caveman`), and re-orienting mid-task (`zoom-out`)

docs/adr/0018-repo-consumes-its-own-plugins-through-apm.md

@@ -59,7 +59,9 @@ answers to `git-commits` and `kyberforge:skill-audit` to `skill-audit`. This is
 a project skill has no plugin to prefix. `AGENTS.md` and `CONTEXT.md` are updated to name the bare
 form, which is what apm deploys and the only form a repo consuming holocron through apm gets.
 
-**Correction (2026-08-14): the namespaced form did not stop resolving.** An earlier revision of
+**Correction (2026-08-14): the namespaced form did not stop resolving.** *Superseded by the
+2026-08-17 correction below: the machine state this cites is no longer present. Both are kept
+because the pair is the finding — read neither as current.* An earlier revision of
 this consequence said every `<plugin>:<skill>` reference "was stale the moment the switch landed",
 and `AGENTS.md`/`CONTEXT.md` were written to match. That contradicts the "User scope is untouched,
 deliberately" consequence below, and the contradiction resolves against it: `~/.claude.json` still

docs/adr/0021-plugin-descriptions-state-a-domain-boundary.md

@@ -11,10 +11,11 @@ plugin is *for*, and the inventory lives where an inventory can be read off the
 ## Context
 
 A plugin's published description is one string authored twice — in `plugins/<name>/apm.yml` and in
-the matching `marketplace.packages[]` entry of the root `apm.yml` — and compiled into six files per
-plugin edit: `.claude-plugin/plugin.json`, `.github/plugin/plugin.json`,
-`.claude-plugin/marketplace.json`, `.github/plugin/marketplace.json`, and (for the version field
-only) their codex counterpart. It is the only text a consumer sees in a marketplace listing before
+the matching `marketplace.packages[]` entry of the root `apm.yml` — and compiled into four generated
+files per plugin edit: the plugin's `.claude-plugin/plugin.json` and `.github/plugin/plugin.json`,
+plus the repo-wide `.claude-plugin/marketplace.json` and its `.github/plugin/marketplace.json`
+mirror. (`.agents/plugins/marketplace.json`, apm's codex profile, carries no per-package
+`description` or `version` at all and is unaffected.) It is the only text a consumer sees in a marketplace listing before
 installing. It is **not** a SKILL.md `description`: it is never preloaded into an agent's context and
 routes nothing at runtime. ADR-0020 governs that other artifact; this one governs this one. The
 overlap is a finding, not a scope: ADR-0020 established that capability enumeration in a description
@@ -70,17 +71,21 @@ unnamed in `git`'s corrected description, though `65bac15`'s own commit message
 `gitea`'s. Across the three plugins, 23 of 27 skills are named at the third attempt.
 
 **Nothing checks any of this.** `scripts/check-manifests.sh` does not contain the string
-`description`. `scripts/skill-size-check.sh` and the three ADR-0020 validators read SKILL.md and
-agent frontmatter and never open an `apm.yml`. `apm audit --ci`, `apm pack --check-clean` and
-`scripts/sync-plugin-content.sh --check --all` all compare compiled output against `apm.yml`, so
-their entire job is to propagate whatever the description says into six files byte-for-byte and
-confirm they match. The `wiki` claim passed every one of the fourteen pre-push hooks, every day it
+`description`. The three ADR-0020 validators (`scripts/skill-size-check.sh` and skill-audit's and
+agent-audit's `validate.sh`) gate on SKILL.md and agent frontmatter; they do open `apm.yml`, but only
+to read `dependencies.apm` when resolving the boundary-target universe — none of them reads the
+`description:` key, and their hook globs match `SKILL.md` and `*.agent.md` only. `apm audit --ci`,
+`apm pack --check-clean` and `scripts/sync-plugin-content.sh --check --all` all compare compiled
+output against `apm.yml`, so their entire job is to propagate whatever the description says into
+those four files byte-for-byte and confirm they match. The `wiki` claim passed every one of the fourteen pre-push hooks, every day it
 was published.
 
 **And the obligation is unbounded.** Under enumeration, adding one skill to `bin`, `git` or `gitea`
-means editing two copies of a prose string, a PATCH bump on the package, a bump on
-`marketplace.version`, and a regeneration of eight compiled files — a marketplace release, triggered
-by a directory appearing. A skill *rename* triggers the same. 27 of the repo's 39 skills sat behind
+means editing two copies of a prose string on top of the version bumps and regeneration any skill
+addition already owes under this repo's release policy
+(`plugins/kyberforge/.apm/skills/apm-workflow/references/marketplace.md`). The bumps are not the
+marginal cost — the prose edit is, and it is the half nothing checks. A skill *rename* triggers the
+same, for a string no consumer can tell went stale. 27 of the repo's 39 skills sat behind
 a description carrying that obligation; the other 12 did not, and their three plugins have generated
 no defect of this class.
 
@@ -159,7 +164,7 @@ fresh and two prior commits as precedent, is four skills unnamed.
 
 **Cap the description length**, mirroring ADR-0020's 250/400-character tiers, on the theory that a
 short description has no room to enumerate. Rejected because length does not measure correspondence:
-`gitea`'s failing description was 114 characters and asserted a skill that has never existed, while
+`gitea`'s failing description was 96 characters and asserted a skill that has never existed, while
 `bin`'s 176-character enumeration is under the same cap. All six descriptions here, before and after,
 sit inside ADR-0020's tiers; the tier would have been silent through all three failures.
 
@@ -183,11 +188,12 @@ field at all, only `name`, `source`, `policy` and `category`.
 1.3.5, `gitea` 1.3.5 → 1.3.6, `marketplace.version` 0.4.4 → 0.4.5.
 
 **The root `apm.yml` top-level `version:` is restored to lockstep with `marketplace.version`,
-0.4.2 → 0.4.5.** These two fields have moved together in every one of the eleven commits that have
-ever touched root `apm.yml` — 0.3.2, 0.3.3, 0.3.4, 0.4.0, 0.4.1, 0.4.2 in both — until `65bac15` and
+0.4.2 → 0.4.5.** These two fields have moved together in every commit that has ever touched root
+`apm.yml` — 0.3.2, 0.3.3, 0.3.4, 0.4.0, 0.4.1, 0.4.2 in both — until `65bac15` and
 `de84d1b` on this branch bumped `marketplace.version` to 0.4.3 and then 0.4.4 while leaving the
-top-level field at 0.4.2. This is a defect, not a style: `apm.yml`'s own comment above the
-marketplace block records that the top-level `version:` is not inherited into the compiled output
+top-level field at 0.4.2. Lockstep is not folklore: it is stated at
+`plugins/kyberforge/.apm/skills/apm-workflow/references/marketplace.md`. This is a defect, not a
+style: `apm.yml`'s comment inside the marketplace block records that the top-level `version:` is not inherited into the compiled output
 "despite being used elsewhere (e.g. by `apm audit`)", so the field is live and was silently two
 releases behind what the marketplace published. Closed here rather than tracked, because the
 correction is one line and the drift is three days old.
@@ -199,13 +205,14 @@ duplication to collapse — they have different readers and different lifecycles
 says so in its own preamble ("These are routing boundaries, not inventories"). One caveat for whoever
 next edits that page: its closing sentence sends a reader to the published description "for what a
 consumer actually gets", which was true against an enumeration and is now a pointer to a second
-boundary statement. Neither artifact carries an inventory after this change. That sentence is owned
-by a separate workstream in this change and is deliberately not edited here.
+boundary statement. Neither artifact carries an inventory after this change, so that sentence was
+rewritten in the same branch to point at `plugins/<name>/.apm/skills/` and `README.md` instead.
 
 **`README.md`'s plugin bullet list becomes the only place an inventory lives, and it still
-enumerates.** Its `bin` and `git` bullets mirror the retired descriptions almost verbatim. This ADR
-does not extend to it and does not require it to change: a README is a hand-read document where a
-list of what you get is the useful thing, it is not compiled into six files, and a stale line in it
+enumerates.** That is deliberate, but it makes the list load-bearing in a way it was not before, so
+its `bin`, `git` and `gitea` bullets were completed in the same branch to name every skill those
+plugins ship. This ADR does not otherwise extend to it: a README is a hand-read document where a
+list of what you get is the useful thing, it is not compiled into four files, and a stale line in it
 costs a reader a moment rather than misrepresenting a published package. The tradeoff that makes
 enumeration wrong in a marketplace manifest is precisely the one that makes it fine there.
 

docs/spec/architecture.md

@@ -84,4 +84,4 @@ The stated convention is that files referencing other files declare those refere
 
 ## Architectural decisions
 
-Key hard-to-reverse decisions are recorded as ADRs in `docs/adr/`. There is no index file — the directory holds 20 numbered ADRs whose filenames state their decision, so `ls docs/adr/` is the index. Read a superseding ADR before the one it supersedes: ADR-0015 (apm as the authoring source of truth) supersedes ADR-0001 and moots ADR-0006, ADR-0017 corrects ADR-0015's host-discovery gap, and ADR-0019 supersedes one claim in ADR-0018 (that `.claude/settings.json`'s committed content is exactly `{"hooks": {}}`) while keeping the rule behind it. Entry points for the structure described on this page: ADR-0002 (two-tier CLAUDE.md), ADR-0003 (AGENTS.md as the provider-agnostic entry point), ADR-0015 and ADR-0017 (the two compilers behind the plugin roots).
+Key hard-to-reverse decisions are recorded as ADRs in `docs/adr/`. There is no index file — the directory holds numbered ADRs whose filenames state their decision, so `ls docs/adr/` is the index. Read a superseding ADR before the one it supersedes: ADR-0015 (apm as the authoring source of truth) supersedes ADR-0001 and moots ADR-0006, ADR-0017 corrects ADR-0015's host-discovery gap, and ADR-0019 supersedes one claim in ADR-0018 (that `.claude/settings.json`'s committed content is exactly `{"hooks": {}}`) while keeping the rule behind it. Entry points for the structure described on this page: ADR-0002 (two-tier CLAUDE.md), ADR-0003 (AGENTS.md as the provider-agnostic entry point), ADR-0015 and ADR-0017 (the two compilers behind the plugin roots).

docs/spec/gates.md

@@ -141,7 +141,7 @@ A boundary-clause target that resolves to no skill or agent has **three** possib
 | Verdict | When |
 |---|---|
 | **SUGGESTION** — the default | the target does not resolve and neither promotion condition below holds |
-| **blocking ERROR** | the target is **terminal** (not a compound modifier) **and** either written in route notation (`/name`, `-> name`) **or** corroborated by another target in the same sentence that *does* resolve |
+| **blocking ERROR** | the target is **terminal** (not a compound modifier) **and** either written in route notation (`/name` for any name; `-> name` only when the name is hyphenated — see the gap below) **or** corroborated by another target in the same sentence that *does* resolve |
 | **INFO, "DID NOT RUN"** | no skill universe could be determined for the path at all — the targets are named and left unchecked, exit 0 |
 
 The default is deliberately soft because a hyphenated word in a boundary clause is as likely to be a
@@ -149,6 +149,15 @@ tool, a file format or an English compound as a route: "pre-commit hooks" is pro
 never reaches the check at all, being a compound modifier rather than a terminal name. The
 SUGGESTION text says how to opt in — write it as `/name` or `-> name` and it gets checked properly.
 
+**Known gap: the arrow form only works for hyphenated names.** Target extraction is built on
+`NAME_HYPH` (`scripts/skill-size-check.sh:543`), which requires at least one hyphen, and
+`ARROW_BOUNDARY` (`:561`) inherits that. So `-> gitea-prs` is extracted and checked, while
+`-> triage` is not extracted at all — no ERROR, no SUGGESTION, exit 0. The unicode arrow `→` is not
+recognised in either case. This makes the SUGGESTION's own advice unsafe for a single-word skill:
+taking it silences the finding rather than checking it. `/name` has no such restriction and is the
+form to prefer. Tracked as a defect; `tests/test-adr0020-targets.sh` has one arrow case and its
+target happens to be hyphenated, so nothing currently covers this.
+
 Corroboration is what makes the soft default safe: a sentence whose *other* target resolves is
 demonstrably a routing sentence, so a sibling that does not resolve is a typo rather than a noun, and
 gets promoted.

tests/run-tests.sh

@@ -14,11 +14,12 @@
 #     into a red run would just train people to ignore red.
 #   * as a GATE (the run-tests pre-push hook): a skip is a SETUP ERROR, not a
 #     legitimate state. README.md's Prerequisites table documents vale, apm and
-#     jq as required pre-push dependencies, so a suite that cannot run on the
-#     machine doing the pushing means the machine is misconfigured -- and
+#     python3/PyYAML -- the dependencies these suites actually guard on -- as
+#     required pre-push, so a suite that cannot run on the machine doing the
+#     pushing means the machine is misconfigured -- and
 #     pre-commit prints NOTHING for a passing hook, so the skip list below is
-#     swallowed entirely. On a vale-less PATH that silently shipped a green
-#     gate having verified 15 of 17 suites.
+#     swallowed entirely. On a vale-less PATH that once silently shipped a
+#     green gate having verified 15 of the 17 suites that existed then.
 #     Exactly the vacuous-pass class the rest of this file exists to close.
 #
 # Deliberately its own switch, NOT folded into
@@ -259,7 +260,7 @@ fi
 # here (not just referenced) because this block goes to stderr and is what a
 # pre-push reader actually gets handed.
 if [[ "$STRICT" == true && ${#SKIPPED[@]} -gt 0 ]]; then
-  echo "Error: --strict and ${#SKIPPED[@]} suite(s) skipped. Run as a gate, a skip is a SETUP ERROR on this machine, not a legitimate state: README.md's Prerequisites table documents vale, apm and jq as required pre-push dependencies, so every suite is expected to be runnable here. Install what each suite names below and re-run; do not skip the hook." >&2
+  echo "Error: --strict and ${#SKIPPED[@]} suite(s) skipped. Run as a gate, a skip is a SETUP ERROR on this machine, not a legitimate state: README.md's Prerequisites table documents vale, apm and python3/PyYAML — what these suites guard on — as required pre-push dependencies, so every suite is expected to be runnable here. Install what each suite names below and re-run; do not skip the hook." >&2
   sidx=0
   for s in ${SKIPPED[@]+"${SKIPPED[@]}"}; do
     echo "  $s" >&2

tests/test-run-tests.sh

@@ -395,8 +395,8 @@ fi
 # suite exiting 77 means a dependency README.md's Prerequisites table documents
 # as required is missing on the pushing machine -- and pre-commit prints nothing
 # at all for a passing hook, so the skip list this script writes to stdout was
-# swallowed whole. A vale-less PATH shipped a green gate having verified 15 of
-# 17 suites.
+# swallowed whole. A vale-less PATH once shipped a green gate having verified
+# 15 of the 17 suites that existed then.
 #
 # The reason is asserted, not just the name: "something was skipped" leaves the
 # reader with no idea which binary to install, which is most of why the swallowed