Defame1297
69119f4754
Why A six-agent review of the two preceding commits found their code sound -- the differential claim holds, the published hook contract is byte-unchanged -- but their prose drifted from it in three ways: statements of fact the code contradicts, markers in a convention this repo does not use, and figures that went stale when the merge changed what they counted. Implementation Notes ADR-0025's edge-path table is rewritten around one stated doctrine: 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. Its old row 1 promised "one generic matches-neither message" for three different inputs; there are three distinct messages, and the missing-path case exited 1 until the preceding commit fixed it. Rows are added for the preflight and CDPATH changes, because a table claiming to enumerate every entry-point behaviour change reproduces its own "an earlier revision of this ADR said they were behaviour-neutral" failure if it omits any. ADR-0025 also gains a Consequences supersession record in ADR-0016's form: partially-superseded entries for 0008, 0014, 0020 and 0021, and explicit "is not superseded" entries with reasoning for the rest. Twelve ADRs are amended and it previously listed none. ADR-0008 moves from an amendment note to partially superseded. Its contract genuinely narrowed -- an agent .md outside an agents/ directory was audited before the merge and is refused now -- and ADR-0020 already recorded that the merge "reopens ADR-0008". Its detector description said "a path under .apm/agents/", the phrasing ADR-0025 rejects as wider than the script and circular; the shipped rule is a .md whose immediate parent is named agents/, at any scope. ADR-0020's amendment claimed the boundary resolver is sourced by validate-provenance.sh. It is not, and never was; only validate.sh sources it, once per mode branch. Three Home-column entries pointed at reference filenames the merge renamed, one of which now resolves to two files because its row covers skills and agents. Five ADRs opened with "Skill renamed per ADR-0025", a form this repo does not use, in the same commit that used the conventional "Amended by ADR-0025" twice. They are normalized. "Renamed" was also wrong: the BREAKING-CHANGE trailer says the skills were removed and their flows merged. SIMPLIFICATION-AUDIT.md had 2026-09-15 notes attached to headlines that were never updated, against its own convention of correcting in place with strikethrough. Every figure here was re-derived at HEAD by command, and several differed from the review's own numbers, so the notes record the basis rather than the result alone. LESSONS.md asserted the two review-time suite failures were the SIGPIPE race. The commit that fixed that race explicitly declined to claim it -- the suite was running while agents edited live config files -- so the hedge is restored. Impact No code, test or configuration change; documentation only. Suites stay 20/20 strict with 0 skipped and 374/374 bats. No gate parses ADR or gates.md content, so nothing here is load-bearing for a hook. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD
2.3 KiB
2.3 KiB
AGENTS.md tooling lives in core, split into three skills
kyberforge is scoped to meta-tooling for building and maintaining the holocron marketplace itself (skills, agents, plugins, marketplace entries) — not to generic capabilities for an arbitrary target repo. Authoring and reviewing a target repo's AGENTS.md file is repo-agnostic documentation tooling, closer in kind to bin:write-docs or bin:init than to skill-author/plugin-author. Research for this topic was initially placed under plugins/kyberforge/docs/research/docs/agentsmd/ but has moved to plugins/core/docs/research/docs/agentsmd/ to keep the provenance chain consistent with the plugin the resulting skills live in.
Decision
Three skills in the core plugin (core's first active skills):
agentsmd-author— creates/updates a target repo'sAGENTS.md, including nested monorepo placement (nearest-file-wins). Closes out by invokingagentsmd-auditinline, mirroring theskill-author/skill-auditpattern (Amended by ADR-0025, 2026-09-15:skill-auditwas removed and its flow is nowfactory-audit's skill flow; the author-then-audit pattern is unchanged). When it detects an existing provider-specific file (CLAUDE.md, etc.) with content that duplicates what AGENTS.md should own, it callsprovider-adapter-authorvia skill composition.agentsmd-audit— a single combined pass checking three mandatory baselines againstAGENTS.mdonly: secrets/credentials (governance.md hard prohibition), structural completeness (common-sections checklist from the agents.md spec), and accuracy/drift (do referenced commands/paths resolve against the repo). Never inspects provider adapter files.provider-adapter-author— detects and converts a provider-specific instruction file into a thin adapter that importsAGENTS.md(mirroring this repo's own two-tierCLAUDE.mdpattern). Self-validates via its own bundled deterministic script (scripts/validate-adapter.sh) rather than a separate paired audit skill, since the check (import present, no duplicated headings, size threshold) is mechanical.
Consequences
core's plugin.json/README will list real skills for the first time.plugins/kyberforge/docs/research/docs/agentsmd/moves toplugins/core/docs/research/docs/agentsmd/before authoring begins.