Post-V0.1: reconcile closure documentation currentness evidence #100

Classification

IMPORTANT / post-V0.1. NOT A V0.1 BLOCKER.

Finding

During WO-024-P-G1-C2 audit, the closure-sprint evidence field documentation_entries was found to be populated from file existence/digest and marked PASS, while the helper documentation_currentness_entry() is not the producer of those entries. The helper's deployment predicate would currently fail because docs/project-brain/12-LOCAL-DEPLOYMENT.md does not contain the literal HIVE_DATA_ROOT.

Why this does not block V0.1 closure

The canonical Definition-of-Done matrix and closure_candidate do not rely on that weak documentation_entries field for the deployment/documentation closure decision. They use independent deterministic DoD verifiers, including deployment evidence and the deployment validation artifact. WO-024 closure evidence remains 46/46 PASS, zero FAIL/UNKNOWN, and zero HIGH/CRITICAL under those canonical gates.

Expected follow-up

After V0.1 closure, reconcile this evidence surface without weakening DoD:

• either wire documentation_currentness_entry() into the emitted documentation evidence, or remove/replace the dead duplicate path;
• make the deployment currentness predicate align with the canonical documentation/evidence source rather than requiring a misplaced literal;
• add regression coverage proving the emitted documentation entries are produced by the same deterministic currentness rules used for audit;
• preserve existing fail-closed behavior and canonical source governance.

Scope guard

Do not modify PR #98 / WO-024-P for this item. Do not expand V0.1 scope. Track as post-V0.1 backlog/quality debt.