2 Commits

Include renames

Author	SHA1	Message	Date
inliver233	d0fe0ea337	Harden the path audit, generalise three absolute paths, and gate the corpus size ... An external review found the evidence record honest and the gates real, but raised three concrete defects. Each is fixed at its cause rather than at its symptom, and the reasoning is recorded in docs/tool-verification/REPO-DECISIONS.md. build_scripts.py -- the audit reported 37 findings, most of them noise It matched any `X:\...` literal, so `C:\Program Files\...`, `C:\Python314\...` and literal placeholders all counted as machine-specific leftovers. A gate whose output is mostly noise stops being read -- the same failure scan_leaks.py names when it refuses to exempt the RFC 5737 ranges. Two explicit exemption families are added instead of a looser regex: GENERIC_PATH_PREFIXES (install locations that exist on every host of that platform) and `_leaks_nothing()` (also exempts an already-redacted path, since a placeholder or an ellipsis means a normalisation pass already ran). Two traps surfaced only because the change was tested rather than merely run. BARE_ABS stops at whitespace, so `C:\Program Files\...` arrives truncated as `C:\Program` and a one-way `startswith` misses the exemption; the comparison is now bidirectional under a minimum length. And with a lookahead of only `[a-z0-9]` the optional `\\?` backtracks to empty, the next character is the separator, it passes, and a real personal path is swallowed -- the lookahead has to exclude the separator as well. Both were caught by the case table, not by the audit run. Result: 37 -> 0 findings, exit 2 -> exit 0. The real hits (`E:\apk-reverse\...`, `E:\agb_apktool.jar`) were fixed in the documents, not by widening the list. Three absolute paths on the published surface EXTENSION-desensitization.md, EXTENSION-extraction-shell-bench.md and EXTENSION-vmp-diff.md quoted a workbench root, a tool jar and an SDK location absolutely. docs/tool-verification/ already states the rule -- a record may say a run happened at a `tools/...` path, written relatively -- so the three files were made to match the rule they were already under. The tool-jar and SDK cases are rephrased rather than placeholder-ised, so no reader has to learn a new token. check_budget.py -- blind to the half of the problem it was not measuring The gate budgets the always-loaded part and could not see the corpus, where a new reference costs exactly one index line: the corpus can double while the narrative count stays green. Two note-level thresholds now report it. Notes, not failures -- a large corpus is a choice, a growth nobody measured is the defect. The first run reports 47 references + 55 scripts = 102 files, 31,423 lines. A cross-tool inconsistency this pass ran into, recorded rather than papered over build_scripts.py now exempts any `<...>` placeholder; scan_leaks.py recognises a fixed token list. An invented placeholder in a source comment passed the first and was read by the second as the very personal name its `user_path_windows` rule exists to catch, turning check_repo.py red. That is by design -- a strict list is what stops a real name hiding behind a plausible-looking placeholder -- but the two tools disagree about what "already redacted" means, and the disagreement stays invisible until someone writes a new token. Rephrased here; a future pass may want one shared list. Verification - build_scripts.py: 37 -> 0 findings on a clean clone, exit 0. - An 18-case table pins both directions, 0 failures: generic and already-redacted paths are exempt, while a real workbench path, a real personal name after `C:\Users\`, a real POSIX home and a real project path still report. It found two defects in the first implementation. - All four gates pass: check_repo 0 problem, check_refs 0 dangling / 0 warning, check_budget 0 failure / 0 warning / 3 notes, build_scripts 0 findings.	2026-09-21 23:18:17 +08:00
inliver233	fd2a1150be	Structure: sink the evidence record out of SKILL.md, and gate the budget ... SKILL.md was 658 lines against the Anthropic Agent Skills guidance of keeping the body under 500, and the growth sat where it costs most: the Coverage section had accumulated the evidence for every claim plus a per-pass verification history (153 lines / 11.8 KB), and Hand-off had grown two knowledge tables. Both now load on demand, with SKILL.md keeping the decision-level statement and a pointer. Coverage 153 -> 68 lines new references/coverage-and-limits.md Hand-off 51 -> 19 lines new references/handoff-boundaries.md SKILL.md 658 -> 543 lines (404 narrative + 139 index) index rows 24.0 KB -> ~19 KB descriptions now say when to load, not what is inside check_budget.py is the substance of this pass. check_repo.py proves consistency, and consistency has a natural counter-pressure: a broken path fails loudly and someone fixes it. Bloat has none -- every pass adds a reference, an index row and a coverage claim, and nothing in the repository notices. The new gate measures narrative lines separately from index lines, because 139 of SKILL.md's lines are the discoverability tax for 86 bundled files and counting them against a prose budget would push the skill to drop files it needs. Conclusions restated beyond the benchmark matrix, the evidence record and the coverage statement are reported as notes. No measured content changed in this pass: every claim, strength label and negative result is where it was, and the two new references carry the moved text verbatim plus the corrections the benchmark pass produced.	2026-09-21 22:12:58 +08:00