All scanning transactions fail with stack overflow ('Access violation in stack frame 3') after partial CU consumption

In Chapter 2 v1.2.25, scanning is completely broken for all players: every scanning transaction crashes with the error 'Access violation in stack frame 3'. The failure occurs after consuming only 7,137 CU out of 200,000 CU, preventing scans from completing and effectively disabling the scanning feature globally.

1. Open Holosim in a web browser and log in.
2. Go to the Scanning feature and start any scan that triggers an on-chain scan transaction.
3. Submit/confirm the scan transaction.
4. Observe the transaction failure with error 'Access violation in stack frame 3' after only ~7,137 CU of ~200,000 CU is consumed.

Scanning transactions should execute successfully within compute and stack limits, consume the expected CU, and return scan results without crashing.

### BUG-033 — Scanning Stack Overflow (All Scanning Broken)
Season 1 | Chapter 2v1.2.25

- Issue: Every scan transaction crashes with 'Access violation in stack frame 3' after consuming only 7,137 of 200,000 CU. Scanning completely down for all players.
- Root cause: Security zone check (commit b192a341) added ~25 account fields to scan instruction, pushing Anchor dispatcher frame to 4,248 bytes — 152 over the 4,096-byte SBF stack limit.
- Priority: P0
- Fix attempts: PR #1007 (pass-by-reference) merged — insufficient. Commit e7f8643b (function extraction) — insufficient. PR #1008 (Box heavy account fields) — pending merge + compile + deploy.
- Status: Awaiting on-chain program redeploy with PR #1008 fix