security(workforce-validation): prevent public forging of corroborated component resolutions

[seonghobae]

Finding

FinalWeightComponentEvidenceResolution is an exported proof-bearing success type. The original public constructor accepted caller-created base/specialized projections and therefore allowed callers to manufacture the same success type returned by corroborate_final_weight_component_evidence(...) without the final-weight/binding owner evidence or governed-use checks.

Repair lineage and #415 refinement

• 4d9269174600c154b17690b7f347ac64fec22480 — source-first RED: ordinary FinalWeightComponentEvidenceResolution(base_weight=..., adjustments=...) must not mint a proof-bearing result.
• 29e2f11d4dfb335459a98c9e39301e1accee9201 — first causal repair: public __new__ became non-issuing and the corroborator used a private issuer after science(workforce-validation): bind final-weight lineage to exact typed component receipts #411/security(workforce-validation): bind component projections to tenant and validity-study authority #412 checks.
• Fresh review then found security(workforce-validation): close tuple.__new__ bypass on component-resolution issuance #415: because that first repair kept FinalWeightComponentEvidenceResolution as a tuple subclass, tuple.__new__(FinalWeightComponentEvidenceResolution, raw_items) bypassed the class __new__ entirely.
• security(workforce-validation): close tuple.__new__ bypass on component-resolution issuance #415 ordinary-forward successor ceb7f4b0b993e24729e2805cd09c647ff0c5bc1e → 5a67b2c07414a79a9b580180b56991ff6ec79156 → e38909985e604e0ba605f22944f39334b2aa9f08 → ab7a968e0109176f0d5862373d0a15d3f1832e92 removes tuple-subclass issuance, seals privately issued canonical state, makes generic uninitialized allocation fail closed on proof-property access, and explicitly regression-tests public immutability of normally issued results.

Canonical #235 is now exact ab7a968e0109176f0d5862373d0a15d3f1832e92, open · Draft · mergeable=true. The current #415 delta fully carries #413's valid ordinary-constructor objective and strengthens it against the newly verified low-level bypass. #413 is therefore not closed: hosted exact-head acceptance, qualifying independent review, protected integration, and durable consumer adoption are still outstanding.

These commits are source-established evidence only until hosted acceptance completes. No new #407 application-owner family is introduced; the active owner-family set remains twenty-two.

Required contract

• Ordinary public construction of FinalWeightComponentEvidenceResolution is rejected.
• Low-level tuple construction is not an alternate proof issuer.
• Only corroborate_final_weight_component_evidence(...) is the supported production issuer after exact receipt identity, owner scope, semantics, construction/current-use chronology and security(workforce-validation): authorize component-evidence resolution before owner reads #414 purpose-bound authorization pass.
• Unsealed exact runtime objects fail closed rather than exposing proof-bearing properties.
• Canonically issued results are immutable through the public mutation surface.
• Component projections remain public value-minimized adapter values and retain existing canonical reconstruction.
• No weakening of packaging, docstring, edge, security or review gates.

Completion boundary

Keep open until current exact-head owned test/docstring/edge evidence, installed-wheel/package/PostgreSQL/security gates, qualifying independent review, normal protected integration, and durable #248 (or verified successor) adoption are complete.

[seonghobae]

Fresh current-head refinement: #413's ordinary-constructor objective remains valid, but #422 proves the proof-bearing result still has a distinct module-capability minting path after #415. final_weight_component_evidence_resolution.py exposes _RESOLUTION_ISSUANCE_MARKER; _require_issued() trusts that exact module object. Source-first RED a27f50d12ccca27ca3b6c0e4a184fc32e1a31888 requires the marker to disappear from ordinary module state and proves a caller-populated raw exact result with an obtainable marker must remain unreadable. Keep #413 open; #422 is additive successor hardening, not a rollback or reason to close the earlier valid delta.