fix(holoindex): restore truthful RedDog query boundary

[Foundup]

Summary

• Establish one canonical HoloIndex store, maintenance lease, atomic invalidation, exact clean-HEAD receipt, complete seven-collection source scope, and per-collection embedding-space fingerprints.
• Add a serialized semantic-only owner on literal 127.0.0.1 with bearer authentication, private handoff, proxy/redirect denial, generation pinning, bounded warmup/query handling, timeout poisoning, and no indexing API.
• Wire RedDog startup, trusted WRE maintenance dispatch, audit/research consumers, and cross-lane repository proofs to fail closed on stale, lexical, narrowed, raced, or unbound evidence.
• Add the WSP_97 assumption audit/receipt, WSP_15 P0 record, WSP_62 exact exemption ledgers and remediation, runbook, machine contract, module docs, and regression suites.

Why

The live store currently has a legacy v1 receipt at an older HEAD and lacks both generation and embedding-space fingerprints. Previous paths could also open divergent stores, publish narrowed/incomplete refreshes as current, or accept lexical/stale evidence. This change rejects those states rather than reporting false CURRENT.

Validation

• Final non-overlapping focused matrices: 745 passed
  • HoloIndex storage/source/CLI/embedding/freshness/incremental/machine contract: 346
  • owner/bootstrap/HTTP/maintenance infrastructure: 133
  • RedDog owner/query boundary: 57
  • downstream audit/bootstrap/FoundUp state: 200
  • idle maintenance bridge: 9
• Independent adversarial owner/client/maintenance/security matrix: 289 passed
• All 81 changed/added Python files compile without bytecode writes.
• WSP_62 accounting: 107 changed paths, 21 inherited temporary exemptions, 0 unregistered violations.
• WSP_97 receipt structurally compliant; WSP_00 gate green.
• Machine JSON parses at exactly 200 lines; YAML/JSON parse and cached diff/secret checks are clean.

CI remediation

The first CodeQL run identified two high-severity clear-text logging flows in the legacy timeout helper. Commit 0fbc55ae1 removes caller-controlled query/path/hint/exception text from logs, emits stable codes plus exception class names only, and adds a sentinel-secret regression. The focused post-fix matrix is green locally; this PR update triggers a fresh CodeQL run.

Truth boundary and activation

• This proves the governed RedDog POC evidence/maintenance boundary, not unrestricted production autonomy or OS isolation.
• The existing persistent store intentionally remains non-operational for this commit. After merge, activation requires a clean main checkout at the merge SHA, an exclusive repository-writer window, canonical fp32 --index-all, then authenticated health/query evidence bound to the merge SHA, generation, receipt digest, and all seven fingerprints.
• Cooperative writer discipline, transient edit/revert detection, abrupt orphan cleanup, hostile same-user loopback/header behavior, and legacy foundups_mcp_bridge/src/holo_tools.py direct-store access remain explicit residuals.
• A broad local legacy test_holo_tools_foundup_validation.py run is not claimed green: 7 cases fail in this Windows sandbox because that out-of-scope path opens E:\HoloIndex directly and its ripgrep fallback hits host encoding behavior. No modified supported-owner test is failing.

WSP disposition

No WSP_framework or WSP_knowledge file changes. MODULE_CONCATENATION_GATE.md remains correctly unmirrored because it is a non-protocol annex. The audit records WSP_62 enforcement-schema and WSP_97 structural-receipt limitations for a separate reviewed protocol/tooling slice.