Task · SKT-0122

Resolve generic-api-key false positive on ordinary teardown documentation

Description

Exact main CI38128447237 atf493ff84292c117f01c16f1d8bb110af8a61ab66 failed secret-scan with one generic-api-key finding. Matching Gitleaks8.30.1 scan restricted to that main ancestry reproduces exactly docs/fleet-management.md line46, a natural-language teardown sentence rather than a credential. Current-source edits cannot remove this historical finding. A default scan of all local refs additionally sees an unpublished review snapshot; that is not public main history. No secret was identified and no matched value is retained here. Existing detector/canary/baseline and history protections must not be weakened; publication is blocked until the scanner proof contract is resolved.

Acceptance Criteria

Definition of Done

Implementation Plan

Precise rule-level prose false-positive correction with fail-first full-history redacted scan and preserved plus expanded representative canaries; guarded review before serial landing and exact CI.

Implementation Notes

One read-only diagnosis, zero implementation attempts. Exact main-only fully redacted scan reproduces one historical ordinary-prose finding at the landed runtime SHA; no secret values printed or identified. Parkowner approval of a precise scanner-contract correction with unchanged full-history scope and intact credential/canary coverage. This task owns present main CI red; no unchanged rerun or new allowlist attempted.

Approved correction implemented locally: rule-specific exact source-line prose handling, no file exclusion/fingerprint/history waiver. Full792commit ancestry scan before correction reproduced exactly one redacted prose finding; after correction no leaks. Existing detector controls and four runtime-generated replacement keys in source/patch forms all detected;13findings in config check. Candidate just check0; completed2file CodeRabbit0findings. Base had unrelated Sigil deadline-test failure, candidate failure list empty. Guarded review and root exact-SHA CI/composed proof remain required before acceptance.

loop14: one scanner change-and-verify cycle, root packet/infrastructure corrections consume none. Full-history scan/canaries and guarded reviews passed; landed376696d, exact CI38149789601 all10jobs success including both scan steps. Final composition clears prior unrelated local race red without an unchanged gate rerun. Final code SHA c573c89f65d206f3e274d1904d8db85425a367d2, exact CI38153340011 all11jobs success; clean composed just check0 (946.402s). just dump0 (22.224s), unchanged runtime/renderer inputs and same-SHA catalogue/corpus producer ratchet225/225; no new inventory delta. just gen not applicable: no blueprint/construct/workload/skill config changed; gen-check passed. Tracker-only final-tip CI identity will also be verified in the run report.

Final Summary

Precise rule-local full-line prose correction keeps all inherited rules and history scope; exact source/patch counterexample silent while every old canary and four generated replacements remain detected. No blanket path/fingerprint/history waiver.

View the source file on GitHub