Primitive version alignment

How this rule is fixed

Pilot deterministic fixer: plan_only · harness mode repo_overlay · verify expect_rule_clean.

See fixer module for plan_only in lib/ux-deterministic-fixers/.

Detection module: docs/design/ux-audit/deterministic-design-rules.md#det-ks-primitive-version-match. Scroll down for Before / After examples and Evidence and remediation steps.

Purpose

When a react-primitive root or registry row declares a primitive version, the DOM attribute data-ks-primitive-version must match primitive_version in visual-registry.yaml or the contract Primitive version line. Scope: rulesScope ks / auto; generic sites skip with skipped_scope.

Passing signals

• data-ks-primitive-version equals catalog version for each governed hash, or neither side declares a version.
• DET.KS.PRIMITIVE_VERSION_MATCH returns no findings.

Failing signals

• version-mismatch: DOM v2 vs registry v1 on hash Fsb.
• missing-runtime-version: registry declares version; DOM omits attribute.

Before example

After example

Deterministic checks

• DET.KS.PRIMITIVE_VERSION_MATCH — det-ks-primitive-version-match.check.js crosswalks DOM and visual-registry.generated.json.

Remediation

Set primitive_version in the registry and contract, then emit matching data-ks-primitive-version from ksReactPrimitiveAttrs or the consumer mount.