feat(cli): add --artifacts-path flag to override .so program location

[procdump]

Summary

cargo-build-sbf --debug emits artifacts in target/deploy/debug on purpose to prevent accidental deployments on mainnet so in that sense:

• Add --artifacts-path CLI flag to support loading debug-compiled .so programs (e.g. surfpool start --artifacts-path ./target/deploy/debug)
• Thread artifacts_path through framework detection, .so existence checks, in-memory template generation, and the --watch file watcher

While working on this PR I've unearthed a calculation overflow bug in txtx-addon-network-svm (details in the PR): solana-foundation/txtx#399

[MicaiahReid]

Hmm, I just ran cargo-build-sbf --tools-version v1.52--debug on a project and it didn't generate a /target/deploy/debug folder. Instead, it put a binary in deploy: deploy/my_program.debug. Are you sure this functionality is consistent across versions?

[procdump]

Hmm, I just ran cargo-build-sbf --tools-version v1.52--debug on a project and it didn't generate a /target/deploy/debug folder. Instead, it put a binary in deploy: deploy/my_program.debug. Are you sure this functionality is consistent across versions?

The change dates back to anza-xyz/agave#9263 . What you observe is most probably because you use cargo-build-sbf from stable. However with agave 4.x the path for debug builds is changed to target/deploy/debug and in that sense surfpool needs some instrumentation to specify the different directory hence the PR.

[procdump]

@MicaiahReid - is it possible that you have a look on this one again?

[MicaiahReid]

@MicaiahReid - is it possible that you have a look on this one again?

@procdump I was able to get this tested, it looks good to me! One question - it looks like the debug build also generates a new keypair / program id. Should this artifacts-path also be updating the keypair used for the deployment?

Something like

            let bin_path = format!("{}/{}.so", artifacts.trim_end_matches('/'), program_name);
            let keypair_path = format!("{}/{}-keypair.json", artifacts.trim_end_matches('/'), program_name);
            // Pass bin_path as the 4th argument (program_name, keypair_path, idl_path, bin_path)
            let old = format!("program = {}(\"{}\") ", get_program_fn, program_name);
            let new = format!(
                "program = {}(\"{}\", \"{}\", null, \"{}\") ",
                get_program_fn, program_name, keypair_path, bin_path
            );

[procdump]

@MicaiahReid - is it possible that you have a look on this one again?

@procdump I was able to get this tested, it looks good to me! One question - it looks like the debug build also generates a new keypair / program id. Should this artifacts-path also be updating the keypair used for the deployment?

Something like

            let bin_path = format!("{}/{}.so", artifacts.trim_end_matches('/'), program_name);
            let keypair_path = format!("{}/{}-keypair.json", artifacts.trim_end_matches('/'), program_name);
            // Pass bin_path as the 4th argument (program_name, keypair_path, idl_path, bin_path)
            let old = format!("program = {}(\"{}\") ", get_program_fn, program_name);
            let new = format!(
                "program = {}(\"{}\", \"{}\", null, \"{}\") ",
                get_program_fn, program_name, keypair_path, bin_path
            );

@MicaiahReid - Good point. I've fixed it as you suggest 7346dbc.

[MicaiahReid]

Thanks @procdump!