scientific(membership): bind design vocabulary version and owner name as one typed wire coordinate #642

Finding

#641 gives MembershipDesign a stable owner vocabulary (tepp.membership_design.v1) and fail-closed name parsing, but release consumers still receive the vocabulary version and design name as independent strings. A consumer can therefore pair a valid owner name with an unsupported/mistyped version unless every downstream projection reimplements the cross-field invariant.

That is the wrong boundary for #638/#639: the Membership owner should issue and validate the pair atomically so downstream code consumes one owner-derived coordinate rather than assembling {version, name} itself.

Required owner contract

Add a narrow immutable value object in membership_core that:

• is constructed from an owner-derived MembershipDesign and emits exactly MEMBERSHIP_DESIGN_WIRE_VERSION plus that design's wire_name();
• parses (version, name) only when the version is exactly supported and the name is in the closed owner vocabulary;
• returns UnsupportedWireVersion for a mismatched version and UnknownMembershipDesign for an unknown name;
• exposes the recovered MembershipDesign, version, and name without authorizing caller-asserted classification;
• keeps fix(release): bind fail-closed reconstructable topic-lineage results (#638) #639 from inventing its own cross-field validation or version/name pairing.

Acceptance

• realistic RED for a valid name paired with an unsupported version;
• RED for an unknown name under the supported version;
• round-trip coverage for all six design states;
• public rustdoc/export and CHANGELOG entry;
• exact-head Rust/docs/security gates + independent review before protected merge;
• release(contract): publish immutable temporal-analysis contract for Orgmetra consumers #638/fix(release): bind fail-closed reconstructable topic-lineage results (#638) #639 consume only after this owner PR lands normally; no mutable source copy.

This is a Membership serialization/value-object boundary only. It must not add estimator arithmetic, HR/person truth, or consumer-authorized design labels.