Replace `#[allow(dead_code)]` with `#[cfg(test)]` for test-only constants
Intent: Four SSH-related environment variable constants in `jerichoci/src/run.rs` were annotated with `#[allow(dead_code)]` to suppress compiler warnings, but they are actually only used in test code. Replacing the annotation with `#[cfg(test)]` is more precise: it communicates intent, removes the constants from production builds entirely, and avoids masking genuinely dead code in the future.
Affected files: crates/jerichoci/src/run.rs
Evidence
@@ -101,15 +101,15 @@ const PREPARED_OUTPUT_FULFILLMENT_SSH_BINARY_ENV: &str =
-#[allow(dead_code)]
+#[cfg(test)]
const PREPARED_OUTPUT_FULFILLMENT_SSH_HOST_ENV: &str = "PIKACI_PREPARED_OUTPUT_FULFILL_SSH_HOST";
-#[allow(dead_code)]
+#[cfg(test)]
const PREPARED_OUTPUT_FULFILLMENT_SSH_REMOTE_LAUNCHER_BINARY_ENV: &str =
-#[allow(dead_code)]
+#[cfg(test)]
const PREPARED_OUTPUT_FULFILLMENT_SSH_REMOTE_HELPER_BINARY_ENV: &str =
-#[allow(dead_code)]
+#[cfg(test)]
const PREPARED_OUTPUT_FULFILLMENT_SSH_REMOTE_WORK_DIR_ENV: &str =In crates/jerichoci/src/run.rs, four constants related to SSH fulfillment configuration (SSH_HOST_ENV, SSH_REMOTE_LAUNCHER_BINARY_ENV, SSH_REMOTE_HELPER_BINARY_ENV, SSH_REMOTE_WORK_DIR_ENV) had their #[allow(dead_code)] attributes replaced with #[cfg(test)].
Why this matters:
#[allow(dead_code)]silences the compiler warning but still compiles the constant into production builds. It also masks the possibility of detecting truly dead code later.#[cfg(test)]tells the compiler these constants exist only in test builds, which is the correct semantic: they are environment variable keys used exclusively in integration/unit tests for SSH fulfillment.- This is a low-risk, high-signal cleanup that aligns with the broader theme of this branch — removing ambiguity and tightening contracts.