docs(docs-hygiene): audit-derivability fork-mechanism wording drift (line 56 vs 111) + Gotchas line ~119 still undisambiguated

[kyle-sexton]

Lane: work-2. Category: review-deferral (VALID, non-blocking).

Source

Review-bot findings on PR #1067 (docs(docs-hygiene): clarify audit-derivability Hard Rules line 111 fork-mechanism reference, closing #1062, itself a follow-up to #1058/#1053). Deferred per this lane's rule 8.

Findings

Two low-severity consistency observations on plugins/docs-hygiene/skills/audit-derivability/SKILL.md's fork-mechanism disambiguation, now stated at two sites (line 56 and line 111) with two different follow-up sites:

1. Wording drift between the two existing disambiguations. Line 56's spot-test bullet says a skill's own context: fork frontmatter "is the opposite: it starts blank." Line 111's Hard Rules bullet (added by docs(docs-hygiene): clarify audit-derivability Hard Rules line 111 fork-mechanism reference #1067) says it's "unrelated ... it starts blank." Both are accurate, but they read as two different explanations of the same fact rather than one consistent voice.
2. Third site still bare. The Gotchas bullet at (approximately) line 119 still says plain "non-fork subagent" with no disambiguation between the Agent-tool fork subagent type and skill-level context: fork. It's a prose summary rather than a definitive statement, so lower stakes than sites 1/2, but it's the remaining site to complete the trilogy of fork-mechanism references in this file.

Suggested fix

In one pass: (a) pick one consistent phrase ("the opposite" or "unrelated," whichever reads better in context) and align lines 56 and 111 to it; (b) add the same brief disambiguating clause to the Gotchas bullet near line 119, or explicitly note there that the term is fully disambiguated elsewhere in the file if a full repeat would be redundant in a Gotchas-style summary.

Category

improvement (documentation consistency, non-blocking)

Work-class: C2 (mechanical) — attended triage 2026-07-23, operator-ratified. 🤖

[kyle-sexton]

This was generated by AI on operator direction.

Superseded — this item was already ratified and should not have been queued.

The earlier first-drain ratification request on this issue was raised in error. The admission gate dispatches a C3 bug-fix-shaped item when it carries either its own recorded ratification or a completed first drain — and this issue already carried recorded ratification in its body from attended triage on 2026-07-23. The drain cycle applied the blanket first-drain rule without first reading bodies for an existing ratification, so it queued an item that was already admitted.

Restored to the autonomous frontier: agent-ready re-applied, needs-human removed. No human action is required, and this issue no longer appears in the attended queue's ratify view.