fix: make conformance test scope explicit for the blocking-call ratchet

The harness already had an inner cfg(test), but the per-file ratchet follows explicit module declarations. Gate the existing registration and family declarations as tests, preserving active test bodies and production exclusion without increasing a blocking-call budget. This is only eight cfg attributes; the compiled f3bf08e58a test binary runs the identical test body under cfg(test).

At f3bf08e58a the governed all-feature focused build completed in 4m16s: test result: ok. 13 passed; 0 failed; 0 ignored; 0 measured; 14319 filtered out; finished in 7.51s. The macOS linker reported oversized __eh_frame compact-unwind warning. Frozen-binary repeat, deliberate drift/UPDATE timeout controls and final ratchet verification follow this checkpoint. No TypeScript/platform/provider/release proof claimed.

Signed-off-by: CodeWhale Bot <[email protected]>

crates/tui/src/conformance.rs

@@ -35,12 +35,19 @@
 #![cfg(test)]
 
 #[cfg(unix)]
+#[cfg(test)]
 mod events;
+#[cfg(test)]
 mod golden;
 #[cfg(unix)]
+#[cfg(test)]
 mod hooks;
+#[cfg(test)]
 mod mcp;
 #[cfg(unix)]
+#[cfg(test)]
 mod prompt;
+#[cfg(test)]
 mod sse;
+#[cfg(test)]
 mod stream_json;

crates/tui/src/lib.rs

@@ -36,6 +36,7 @@ pub mod computer_meter;
 mod config;
 pub mod config_keys;
 mod config_persistence;
+#[cfg(test)]
 mod conformance;
 mod context_report;
 mod core;