T6: ref and doc hygiene sweep for hyp policy verb#326
Merged
philcunliffe merged 1 commit intoJul 17, 2026
Conversation
Ran ref-check across the touched hyp-policy-verb surface (clients.js, policy.js, classification.js, core_commands.js, both hypaware-privacy SKILL.md bodies, and LLP 0103/0110/0111/0112) and found the verb-surface @ref citations already correct from T2-T5. The remaining stale spots were three doc comments left over from T1's carry-forward (repoRootDefaultTarget, runMarkMachineLocal, runIgnoreCheck) that still described the policy set/show runners as "a future task" and described repoRootDefaultTarget as shared with the future policy verb, when in fact policy set/show now exist and policy set deliberately never calls repoRootDefaultTarget (it marks the resolved path exactly as pointed at, per LLP 0111 #set). Corrected those glosses to state the current, already-landed relationship instead of a stale forward-looking one. Verified LLP 0103's Extended-by: LLP 0110 forward-ref still reads correctly against the final shipped verb surface. ref-check's only remaining findings in touched files are two pre-existing false positives against LLP 0086's HTML-anchor sections (the tool only scans markdown headings), unrelated to this change set and present before T1-T5 touched this file. No behavior change. npm test (2284 tests) and npm run typecheck both pass. Task-Id: T6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements task T6 of hyp-policy-verb.
Ran ref-check across the touched surface (clients.js, policy.js,
classification.js, core_commands.js, both hypaware-privacy SKILL.md
bodies, and LLP 0103/0110/0111/0112). Verb-surface
@refcitationswere already correct from T2-T5 (dual
LLP 0103#cli+LLP 0111#...annotations on the hoisted internals,
LLP 0110/LLP 0111#teachingonthe classification hook). Fixed three stale doc comments left over
from T1's carry-forward that described
policy set/policy showas"a future task" even though T2 had already landed them, and corrected
repoRootDefaultTarget's docstring to state thatpolicy setdoes notuse it (it marks the resolved path exactly as pointed at, per LLP 0111
#set) rather than describing it as a shared-in-the-future concern.
Verified LLP 0103's
Extended-by: LLP 0110forward-ref still readscorrectly against the final shipped verb surface — no change needed
there.
ref-check's only remaining findings in touched files are two
pre-existing false positives against LLP 0086's HTML-anchor sections
(the tool only scans markdown
#headings, not<a id>tags);unrelated to this change set and present before T1-T5 touched the
file.
No behavior change.
Test plan
npm test— 2284 tests, all passingnpm run typecheck— clean/ref-checkrun across touched files — no new/broken refs from this changeTask-Id: T6