fix(cli): Correct handling of compilation skipping in trace decoder

crates/cast/tests/cli/main.rs

@@ -2003,7 +2003,16 @@ contract LocalProjectScript is Script {
         .stdout_eq(str![[r#"
 Executing previous transactions from the block.
 Compiling project to generate artifacts
-Nothing to compile
+No files changed, compilation skipped
+Traces:
+  [..] → new <unknown>@0x5FbDB2315678afecb367f032d93F642f64180aa3
+    ├─  emit topic 0: 0xa7263295d3a687d750d1fd377b5df47de69d7db8decc745aaa4bbee44dc1688d
+    │           data: 0x000000000000000000000000f39fd6e51aad88f6f4ce6ab8827279cfffb92266
+    └─ ← [Return] 62 bytes of code
+
+
+Transaction successfully executed.
+[GAS]
 
 "#]]);
 

crates/cli/src/utils/cmd.rs

@@ -339,7 +339,14 @@ pub async fn handle_traces(
         let _ = sh_println!("Compiling project to generate artifacts");
         let project = config.project()?;
         let compiler = ProjectCompiler::new();
+
+        // We need to handle the case where compilation is skipped due to no changes
+        // This is a valid outcome and should not be treated as an error
         let output = compiler.compile(&project)?;
+
+        // If output.is_unchanged() would be true, the compiler already printed
+        // "No files changed, compilation skipped" for us
+
         (
             Some(ContractsByArtifact::new(
                 output.artifact_ids().map(|(id, artifact)| (id, artifact.clone().into())),