RSR applicability: workspace and named ABI layouts need a canonical decision #1262

Measured alignment gap, not a request to waive gates

While aligning hyperpolymath/rpa-elysium with Standards 80014df42eb81f09396c948299febb258cec4719 and rsr-template-repo c9bce256a3812575f509c9c90c64a1277a999a3b, the exact scripts/check-rsr-profile.sh reports:

MISSING (rust): src/**/*.rs
MISSING (ffi): src/interface/ffi/
MISSING (abi): abi.ipkg
MISSING (abi): src/interface/abi/|src/interface/Abi/
MISSING (abi): src/interface/generated/

The application has eight Cargo workspace crates at crates/*/src/, implemented FFI at ffi/zig/, an Idris package rpa-elysium-abi.ipkg, and ABI modules at src/abi/. These capabilities are declared truthfully in its new profile. No empty scaffold, carrier exemption or false passing checker was introduced. Generated ABI output is genuinely absent and remains a separate local engineering gap.

Decisions/acceptance criteria

• Decide whether conventional Cargo workspace source should satisfy the Rust gate (e.g. an alternative crates/*/src/**/*.rs). Add positive/negative controls; do not accept empty directories as source.
• Decide whether a named ABI .ipkg and real legacy ABI/FFI source paths are valid alternatives, or require a source/build migration. Preserve actual compiler inputs and ownership in either case.
• Clarify whether generated ABI artefacts must be tracked, generated and validated in CI, or represented by a build/generation contract. An empty generated directory is not evidence.
• Implement the chosen table/checker or repository migration and rerun the exact canonical checker.

Evidence: rpa-elysium/docs/STANDARDS-ALIGNMENT.adoc, merged in #145 and clarified by hyperpolymath/rpa-elysium#146. Repository community health is 100%, private vulnerability reporting is enabled, but those facts are explicitly NOT called full RSR certification. This is an honest remaining applicability/layout discrepancy, not a completed estate rollout.

Additional parser interoperability found during validation: valid unquoted YAML from yq/YAML stringification is rejected by deployed Hypatia (expected_version_or_workflows). The follow-up adds official single-quoted rendering plus regression controls; no detection rule was suppressed. Track any upstream YAML-reader modernization separately from the capability decisions above.