ContextLattice v3.20.2: One Source. Every Lane.

The release gate found two test files whose only difference was a deleted reference to developer-only configuration. Runtime behavior was identical. Source identity was not. ContextLattice stopped the paid installer before a single asset escaped.

v3.20.2 removes that split without smuggling developer-only configuration into paid builds. The same test source now treats premium_dev.env as an optional development fixture that is intentionally absent from distributed lanes.

The CLI remains the primary interface. HTTP remains the integration fallback.

What changed

• Canonical and public-paid now execute one byte-identical commercial-truth and boundary-test source.
• The shared tests conditionally recognize the intentional absence of developer-only configuration instead of deleting assertions per lane.
• The exact paid behavioral-source comparator now proves the tagged candidate against the approved release proof before compilation or packaging.
• v3.20.1-public-paid remains asset-free and is superseded by v3.20.2-public-paid.

What did not change

• Utility Ledger recording, exact token accounting, outcome verification, analytics, advisory policy, durability, or rollback behavior.
• Paid entitlement boundaries remain unchanged, and distributed artifacts contain no developer-only profile.
• Public core boundaries, quickstart requirements, third-party harness policy, and the CLI-first product contract.

Verification

The patch must reproduce one source-identical canonical/paid test pair, pass both lane suites, regenerate the closed-world manifests, bind the exact release proof, and complete every installer job before assets publish.

Rollback

Use public v3.20.2 or paid v3.20.2-public-paid. Earlier paid patch tags intentionally carry no installer assets.