Piotr Magiera

Test collector part done in https://github.com/software-mansion/scarb/pull/1271

We can update the gif, roadmap - move some points to `Features` section, add our yt tutorial,

Blocked by #846

Maybe we can reuse this https://github.com/cairo-book/cairo-book/tree/main?tab=readme-ov-file#work-locally-cairo-programs-verification https://rust-lang.github.io/mdBook/format/mdbook.html#including-files

Isn't it done already? We use the block number instead of the tag so it will be cached https://github.com/foundry-rs/starknet-foundry/blob/802dc2330c2e16573b98ba2c5b8139199d18fff8/crates/forge-runner/src/running.rs#L324 cc @war-in

@orizi I don't really need it, just accidentally encountered this panic lately

Isn't it covered by pprof features already?

I would argue that we should just return an error in this case - the only other solution I see is adding stuff to `Scarb.toml` which I would consider potentially...

This will work if someone hasn't specified any other target, which is a rare case in sncast scripts - usually starknet target is needed to compile contracts. Scarb just defaults...

For creating the entry code all the compiler really need to know that is sierra specific are the names of the args (`GenericTypeId` is basically a newtype for `SmolStr`), we...