docs: align value frontier after VALUE-02 software integration

[daniele21]

Outcome

Align the canonical repository state and incremental delivery workstream with the actual integrated software state after PR #141.

• VALUE-01A/B/C remain software DONE; VALUE-01D VALUE-01D — Execute and retain the representative real-device run #120 remains the real acceptance gate.
• VALUE-02A/B/C are recorded as software integrated on dev; VALUE-02 itself remains blocked until VALUE-01D — Execute and retain the representative real-device run #120 and VALUE-02D VALUE-02D — Execute representative real multi-model decision #132 REAL_ENVIRONMENT PASS.
• The required convergence order is explicit: fresh exact-head PRE_REAL -> VALUE-01D — Execute and retain the representative real-device run #120 -> VALUE-02D — Execute representative real multi-model decision #132.
• VALUE-03A VALUE-03A: consume declared generation domains #149, VALUE-04A VALUE-04A: distinguish decision-grade device evidence #148 and VALUE-08A VALUE-08A: add an artifact-owned launcher #147 are recorded only as prepared isolated lanes, not integrated capability.

Documentation impact

• README_IDENTITY: N/A — product identity unchanged.
• README_USAGE: N/A — usage unchanged.
• FEATURE_DOCS / ARCHITECTURE / ADR / SECURITY_DATA / OPERATIONS / PRODUCT_EXPERIENCE: N/A — no behavioral contract change.
• CURRENT_STATE: UPDATED — this is the canonical owner of integrated/blocked/next truth.
• Active delivery workstream: UPDATED — delivery dependencies and convergence state changed when VALUE-02 software was integrated.

Validation

Documentation/governance-only INTEGRATION change. Use the repository selector and automatic PR validation; no REAL_ENVIRONMENT claim is made by this PR.