[mohammadfawaz]

Prepare Leo 4.4.6 with snarkVM 4.12.0 and snarkOS 4.12.0.

Release changes

• Bump all workspace package versions and internal dependency pins to 4.4.6. Update tree-sitter metadata and CLI version fixtures.

• Upgrade all locked snarkVM crates to 4.12.0 and set snarkOS to 4.12.0 for CI and release metadata.

• Support up to 128 mappings per program from consensus V22. Update the mapping boundary fixtures and documentation.

• Use the current snarkVM view evaluation API and pass the deployment consensus version to the static fee calculation.

• Calculate test transaction fees from the ledger’s current consensus version so fixtures at earlier block heights use the correct fee rules.

• Refresh deployment and upgrade fee expectations for the snarkVM 4.12.0 consensus V22 synthesis fee calculation. It uses variable and constraint counts instead of circuit density.

• Write network dependency checksums in leo.lock as 64 lowercase hexadecimal characters. Use lock version 3 and continue to read version 1 and 2 locks and legacy byte arrays. Accept uppercase hexadecimal input and write it in lowercase. Older Leo versions cannot read version 3 locks.

Changes since Leo 4.4.5

• Move CI checks from CircleCI to GitHub Actions. Discover local test files in name order so compilation messages and test results are deterministic across filesystems. (Migrate Leo CI to GitHub Actions #29664)
• Lock network dependency editions and checksums. Change leo update to refresh dependency locks. Remove the built-in Leo updater and automatic release checks. (Lock network dependencies and add explicit dependency updates #29641)
• Keep storage operations in an else if condition inside their branch, so skipped conditions do not execute those operations. (Keep else-if storage operations inside their branch #29642)
• Use full function identities for mandatory inlining, so functions with the same name in different libraries remain distinct. (Use full function identities for mandatory inlining #29646)

Historical view evaluation

snarkVM 4.12.0 removes the historical view API. Current-state view fn evaluation remains supported. The devnode endpoint with an explicit height now accepts only the latest block height. Requests at past or future heights return an error (400 Bad Request under the v2 API). Update the endpoint documentation and CLI fixtures for this behavior.