fix(platform): align HO-DET-012 proof visibility

[raylee-hawkins]

Aligns HO-DET-012 platform factory visibility with current proof truth.

This PR changes only scripts/ho_factory.py and docs/factory/DETECTION_FACTORY_CONTROLLER_V0.md.

Boundary preserved:

• proof status remains CONTROLLED_TEST_VALIDATED
• runtime remains NOT_PROVEN
• signal remains NOT_PROVEN
• public-safe remains NOT_PUBLIC_SAFE
• no runtime-active, public signal, public-safe runtime, production, fleet-wide, autonomous SOC, AI-approved, or analyst-approved claim is promoted
• no runtime evidence is created
• no proof or website files are changed

Validation:

• validate-ho-det-012.py
• verify-ho-det-012-result-parity.py
• scan-ho-det-012-claim-boundaries.py
• verify_detection_proof_status_index.py
• ho_factory.py status --detection HO-DET-012
• git diff --check

[raylee-hawkins]

Reviewed the HO-DET-012 source/validation/platform drift fix.

This PR aligns stale NO_PROOF_RECORD expectations with current proof truth: HO-DET-012 has a governed CONTROLLED_TEST_VALIDATED proof record/card while runtime, signal, and public-safe runtime claims remain blocked.

Boundary preserved:

• runtime remains NOT_PROVEN
• signal remains NOT_PROVEN
• public-safe remains NOT_PUBLIC_SAFE
• no runtime-active, public signal, public-safe runtime, production, fleet-wide, autonomous SOC, AI-approved, or analyst-approved claim is promoted
• no runtime evidence is created
• no proof or website files are changed

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0e79e0464f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add HO-DET-012 proof files to required surfaces list

Setting proof_record/proof_card here makes proof artifacts a hard dependency, but build_packet only tracks dependency presence through spec.surfaces before assembling repo_surfaces_found and missing-surface diagnostics. Because HO-DET-012’s surfaces tuple was not updated, proof files are not reported in surface inventory and absent proof files skip the structured dependency-missing path, then fail later in assert_proof_record with a generic file-missing error instead of a consistent dependency report.

Useful? React with 👍 / 👎.