Harden audit privacy exclusions

[pate0304]

What changed

• prevent Codesemble audits from reading or hashing auth/token configuration stores
• retain benign source and documentation files such as src/auth.ts, token utilities, and authorization docs
• add tracked-Git and filesystem test coverage for sensitive names, case variants, nested paths, and known credential stores
• rebuild the bundled plugin archive and refresh checksums
• replace stale validation claims with exact-candidate runtime and local verification evidence

Why

The audit allowlist accepted JSON, YAML, TOML, and similar files, while the secret-like filename filter did not recognize common auth and token stores. A tracked file such as auth.json or token.json could therefore be inspected and hashed despite the privacy documentation saying authentication material was excluded.

Impact

Audits now fail closed for credential-bearing auth/token configuration filenames without hiding normal implementation files. Documentation and runtime evidence accurately distinguish locally verified results from public CI, merge, and release status.

Validation

• TypeScript typecheck
• 20 Vitest files / 141 tests
• deterministic 12-file plugin archive and bundled CLI smoke test
• CycloneDX SBOM generation (128 components)
• 127 checksum verification entries
• repository validator (4 skills / 15 docs)
• official plugin validator and all four skill validators
• npm audit: 0 high-severity vulnerabilities
• fresh typed delegation and no-spawn runtime checks recorded in artifacts/runtime-evidence.json
• GitHub CI passed on Node 22 and 24 across Ubuntu, macOS, and Windows
• CodeQL and dependency review passed

Remaining release gates

• isolated-home reverse rollback proof for the exact payload
• review and merge approval
• tag/release/publication approval