stack-encrypt: enroll value-kind and query-operator fixtures in conformance #1474

Existing Rust/Go value-kind and query-operator fixtures provide wider coverage than the initial conformance profiles, but are not part of the named contract or its local command. Enroll that evidence without copying vectors or replacing its typed/generated API assertions.

Implementation: #1469.

Acceptance criteria:

• Define record-value-kinds-v1 and record-query-operators-v1 with stable requirement IDs mapped to the existing test functions.
• Keep value_kinds.json and query_operators.json at their original paths, unchanged; select their original runners in the conformance command.
• Cover typed frames, frozen-record opening, stored terms, decimal/timestamp normalization, query metadata/operands, match verification and bounded/unbounded fetch limits.
• Retain typed-versus-dynamic Rust comparisons and generated Go encryption, decryption and query checks.
• Guard requirement-to-test mapping and selection in CI, without a duplicate suite.
• Fail required runs when the guest is absent, and reject fixture regeneration during required checks; exercise both safeguards.
• Update the roadmap and coverage inventory with the remaining gaps.

This is representative fixture coverage, not an exhaustive type/operator matrix or fresh cross-opening of every wider value kind. Shared query refusals, context composition and EQL/JSON profiles remain follow-ups. Python fixture parity is already tracked by #1393; its runner should reuse this evidence. Binding-author documentation remains #1254.

Depends on #1473 (implemented by #1462).