Defame1297
620f20b0fd
Why The two audit skills carried 1,724 lines of byte-identical duplication: the ADR-0020 boundary resolver (1,061), vale-wrap.sh (526), the Vale style rules (44) and the Contributing-files parser (93). Nothing shared them — they were held in sync by a 413-line pre-push gate and its 797-line test suite. Sync-by-gate had already failed once: at484357athe two parser copies drifted into different spellings of the bullet loop while a docstring asserted they were identical. That drift was behaviour-neutral and was re-unified by hand at598a7c3, so the copies were identical at merge time — but nothing had caught it, and the next drift need not be neutral. Implementation Notes Self-containment binds BETWEEN skills, not within one. The agentskills.io spec forbids reaching across skill directories, which is why two separate skills needed embedded copies; two files inside ONE skill may source a third. That is the whole reason the merge removes duplication rather than relocating it. The union of both bodies measured 1,532 words against BODY_MAX_WORDS=900, and only 211 of those words were shared, so SKILL.md is a dispatch body. Step 0 resolves the flow from the target path before any validation, and its table mirrors validate.sh's detection exactly: a directory holding SKILL.md or a SKILL.md file (skill); a *.agent.md, or a .md directly under an agents/ directory (agent); anything else stops without running a validator. Steps 1-3 live in references/skill-flow.md and references/agent-flow.md, and gotchas that apply to one flow live in that flow's file, since it is loaded on every invocation anyway. If validate.sh reports on the other artifact type, the body restarts at Step 0. Named factory-audit rather than forge-audit because forge is a live skill, and a family prefix that matches a live sibling reads as ownership rather than membership. The description carries one arrow per boundary target, because ADR-0020 resolves only the first target after an arrow. It drops the quoted "audit this skill"-style phrases, which restated "audited" in a second register (ADR-0020's duplicate-register rule). 241 characters, Gotchas 16% of the body: no size SUGGESTIONs. The boundary resolver stays embedded in two files rather than imported: a cache-installed plugin cannot read outside its own directory, and the repo-root hook resolves via .pre-commit-hooks.yaml where entry[0] is the only token pre-commit rewrites, so no single file is reachable by both. tests/test-adr0020-contract.sh hashes both copies for byte-identity, and asserts validate.sh sources the resolver and that no third copy exists. The entry scripts classify the target from its resolved parent directory, so a bare agent filename typed inside agents/ works; resolve SCRIPT_DIR CDPATH-safely; and exit 2 when a lib-*.sh is missing, rather than dying with exit 1, the tier the flows relay as real findings. The provenance run functions stash their findings code in KYBERFORGE_PROV_RC and return 0, so validate-provenance.sh calls them UNTESTED. Testing a function's status (`f || RC=$?`) disables errexit for its entire body, and no subshell or `set -e` inside can re-arm it once the call sits in a condition context (measured, both spellings). Their error paths use `exit`, which is unaffected either way; this keeps errexit armed for anything added later. Case 0's readability guard reads the file instead of asking `[[ -r ]]`. `-r` is access(2), which answers yes for uid 0 even on a mode-000 file, and this repo's dev environment is root -- so the guard could never fire where it exists to fire. A read attempt is also the stricter question, catching EIO. This is the reasoning scripts/check-vale-style-sync.sh carried before this commit deleted it; the hazard did not go with it. All three entry scripts are CDPATH-safe, vale-wrap.sh included: both of its cd sites are cleared, the --config resolution and the directory-mirror walk, where an exported CDPATH would otherwise print a decoy path into the -print0 stream and build the mirror from the decoy's files. The two remaining bare cd calls take absolute paths, which CDPATH is never consulted for. Impact BREAKING: skill-audit and agent-audit no longer exist as invocable skills. kyberforge goes to 2.0.0 (catalog 0.4.7). Check logic is unchanged: differential runs of the old and new validators across every skill and agent produced byte-identical stdout, stderr and exit codes, and the reconstructed Python payloads differ only in comments and the references/field-inventory.md -> agent-field-inventory.md rename. One doctrine governs the tiers: exit 0 is audited and clean, exit 1 is audited with findings OR a target present but unreadable, exit 2 is that nothing was audited at all. Edge paths DID change, deliberately (full table in ADR-0025): - a missing target exits 2 (never ran), not 1, under its own "does not exist" message; detection is by path shape, so a shape-matching path that is simply absent used to reach the validator and come back as a FAIL against a file that never existed; - an unshaped target exits 2 under the generic "matches neither" message, and a directory with no SKILL.md under a third, distinct one -- three exit-2 messages, not one; - a dangling symlink or a symlink loop stays exit 1: it is present but broken, which is a finding about the artifact rather than a usage error; - a SKILL.md file path is audited as its skill directory instead of refused; - a .md agent outside an agents/ directory is refused rather than audited; - a missing script library, a missing python3, a missing PyYAML, and no argument at all each exit 2. validate-provenance.sh already exited 2 for the last two; validate.sh now matches it. .pre-commit-hooks.yaml is a published contract consumed by external repos. Both hook IDs and both files: regexes are unchanged; only entry: and description: moved. scripts/check-vale-style-sync.sh (413), scripts/sync-vale-styles.sh (21), tests/test-check-vale-style-sync.sh (797) and agent-audit/scripts/README.md (47) are deleted. The checker made 17 assertions: 6 compared the two Vale copies and are moot; 10 are rehomed into tests/test-vale-wrap.sh (case 0, cases 28-31, and the suite's Vale-absent skip); and the cross-manifest files: agreement check, which selected hooks by entry: and so could not survive both hooks sharing one, is ported as case 33 pairing hooks by id:. Cases 28, 30 and 33 carry mutation self-tests; narrowing the local skill prefilter to 6 of 38 SKILL.md files now fails the suite. Skills go 39 to 38. Pre-push goes 9 repo-authored hooks to 8. ADR: 0025 BREAKING-CHANGE: the skill-audit and agent-audit skills are removed. Both flows are served by factory-audit, which auto-detects whether it was handed a skill directory or an agent file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD
4.5 KiB
Plugin-scope agent provenance file moves to <plugin-root>/sources.md
Partially supersedes: ADR-0005 (agent-author dual-provider scaffold) — specifically the
claim that "both files share a single agents/sources.md for provenance." The rest of
ADR-0005 (dual-provider generation, scope detection, single-root script interface) is
unaffected and remains in force.
Path update per ADR-0016: at plugin scope, agent files no longer live at
<plugin-root>/agents/<name>.md. The authoring source is now
<plugin-root>/.apm/agents/<name>.agent.md — a single vendor-neutral file (no dual Claude/
Copilot pair) compiled to both targets via apm pack. See ADR-0016 for why (the field-dropping
rationale, tools: incompatibility, the compiled-output mechanics) — not restated here. This
ADR's own conclusion is unaffected by that move: the provenance file still belongs at
<plugin-root>/sources.md, outside any directory claude plugin validate --strict
auto-scans, and .apm/agents/ is, if anything, further removed from plugin-root than the old
flat agents/ directory was, so the reasoning below still holds. References below to
<plugin-root>/agents/ describe the pre-APM layout in effect when this decision was made.
Skill renamed per ADR-0025 (2026-09-15): agent-audit merged with skill-audit into
factory-audit; read the agent-audit references below as factory-audit's agent flow, whose
validate-provenance.sh still resolves <plugin-root>/sources.md exactly as this ADR decided.
Scope boundary (per ADR-0016): this path change is plugin scope only. Project scope
(.claude/agents/ + .github/agents/) and user scope (~/.claude/agents/ +
~/.copilot/agents/) are unaffected — they are not APM packages and keep the dual-file
Claude+Copilot pair model this ADR originally described.
claude plugin validate --strict auto-discovers every .md file directly under a plugin's
agents/ directory and treats it as an agent definition requiring YAML frontmatter (name,
description, etc.). A flat provenance file at agents/sources.md — no frontmatter, by
design, since it is not an agent — fails validation with a missing-frontmatter warning that
--strict promotes to an error.
This was first hit in plugins/git/agents/sources.md (added by the git-plugin skill suite).
It failed the validate-plugins pre-push hook. The stopgap in commit 0239b00 added
throwaway agent frontmatter to unblock the push:
---
name: git-agents-sources
description: Provenance record for the git plugin's agents, not an invokable agent. Do not invoke.
tools: none
---
That workaround is now reverted — the file no longer lives where it needs to impersonate an agent to pass validation.
Considered options
Exclude via an explicit agents manifest array (rejected) — plugin.json supports
"agents": ["./agents/reviewer.md"] as an alternative to "agents": "agents/". The
hypothesis was that listing only real agent files would stop the validator from also
discovering sources.md in the same directory. Tested empirically on a scratch copy of the
git plugin: claude plugin validate --strict still auto-discovered and failed on the
unlisted sources.md, regardless of the explicit array. The manifest field controls what
Claude Code loads as agents at runtime; it does not control what the validator scans on
disk. There is no manifest-level or CLI-flag mechanism to exclude a file from agents/
auto-discovery.
Keep the frontmatter workaround permanently (rejected) — cheapest fix, already applied,
but semantically wrong: it makes a plain provenance record indistinguishable from a real
invokable agent to any tooling or UI that lists available agents (e.g. it could appear as a
callable agent in the /agents picker), which is confusing and incorrect.
Consequences
- The provenance file moves to
<plugin-root>/sources.md— a flat file, plugin-root relative, sitting outside any directory that Claude Code or its validator auto-scans. No frontmatter is needed or added. agent-author'snew-agent.shnow writes<root>/sources.mdinstead of<root>/agents/sources.mdat plugin scope.agent-audit'svalidate-provenance.shnow looks for<plugin-root>/sources.mdwhen checkingsource_keysprovenance chains.- All doc and template references to
agents/sources.md(agent-authorSKILL.md, agent-auditSKILL.md/README.md, both provider templates) are updated tosources.md. plugins/git/agents/sources.mdis relocated toplugins/git/sources.mdand the0239b00frontmatter workaround is removed.