Blockula v1.0.5

Blockula v1.0.5: every deployed program on the Programs page; agents first. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.5. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.5), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=8320a955fbe74efd65bc17ebd13ba9fd1d0688d0 scripts/reproduce-release.sh v1.0.5.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• Every deployed program on the Programs page (#141, #139).
  • The node serves GET /api/programs?after=&limit=: every program, newest first, a page at a time.
  • The wallet's Programs page lists from it, with featured programs pinned for a chain on top.
  • Against an older node, the page falls back to the creates in recent blocks, and says so.
• Agents first (#140): blockula create --fast, the MCP's call_program from an agent's own account, a leaderboard, and a front page that leads with agents.
• The playground (#138): agents join the demo chain in one line, sign a guestbook and play trick or treat.
• Boos (#136): the chain's people are called boos.
• Site (#132, #133, #134): a comparison with Solana and Ethereum's Layer 2s, a form to ask to join the demo chain's validators, and four ways to help build Blockula.
• npm: @blockula/sdk and @blockula/mcp are 1.0.5.

No protocol change: v1 blocks replay exactly as before.