Track CI duration wins from slim shells + committed artifacts #2607

Goal

Track the CI duration wins from the slim-shell / committed-artifacts work, so we can see what's actually moved on main vs what's still pending in PRs.

Baseline on main (latest run per workflow as of 2026-05-30)

Wins already landed

• rain.cli remove input and output from take orders #19 + raindex Pin rain.cli via flake input for build-meta (deterministic Cachix hit) #2604: rain.cli is Cachix-published, raindex's script/build-meta.sh uses the flake-locked rain via .#rain-cli. copy-artifacts 6m → 5m.

Pending PRs and their expected gains

• raindex Commit subgraph/abis + subgraph/generated; use rainix-subgraph-test reusable #2606 (subgraph committed artifacts + thin rainix-subgraph-test wrapper, slim #subgraph-shell): drops forge build + graph codegen from the test path; matchstick runs over committed subgraph/abis/ + subgraph/generated/. Expected: Subgraph unit tests 16m -> low single-digit minutes.
• rainix Token detail page #212 (pkgs.sqlite in rust-build-inputs + subgraph-test task npm ci): unblocks raindex's rust matrix on #wasm-shell (rusqlite needs system sqlite), and makes subgraph-test self-contained over committed bindings.
• Phase 2 — rainix.yaml slim-shell refactor (not yet opened, depends on Token detail page #212): drop ./pointers.sh, switch each matrix task (rs-test, cargo build --release, rs-static, wasm-artifacts/test/browser-test, test-js-bindings) to nix develop github:rainlanguage/rainix#wasm-shell -c <inlined cmd>. Expected: Rainix CI 25m -> meaningfully less; biggest unknown, will be measured post-merge.

Other observations

• forge build in ./pointers.sh is dead weight for the rust matrix — none of the crates compile-time or runtime depend on out/ (no sol! macros pointing at it, no include_bytes!, no shell-outs to forge/cast/anvil). Phase 2 above drops it.
• Test webapp / Test ui-components and Rainix CI's js bindings are next-tier targets but not currently scoped.