Build Log · July 20, 2026

Alloy First Live Execution Proof

One authenticated Ignite action reached a real Claude session, persisted ordered provider events in Neon, completed durably, and rendered in Forge.

  • Alloy
  • Milestone 1
  • Runner
  • Claude Code
  • Neon
successful live execution
1

successful live execution

ordered provider events
5

ordered provider events

proof-blocking fixes
3

proof-blocking fixes

Timeline

  1. Orient

    Loaded the approved proof Charge

    Bound the session to WP-9426 and one UI-to-runner causal proof.

  2. Ignite

    Found and repaired the first boundary

    Windows could not spawn the extensionless Claude command; the failed Execution was preserved honestly.

  3. Forge

    Completed the controlled retry

    Claude read Alloy package metadata, emitted five ordered events, and reached a durable completed state.

What shipped

  • products/alloy/components/ChargeContractPanel.tsx — exposed the authenticated finalized-Charge transition into Ignite.

  • products/alloy/lib/actions.ts — captured persona and execution mode before the awaited Charge save.

  • products/alloy/runner/providers/claude-cli.ts — resolved the real Windows Claude executable without a shell and emitted a terminal failure event on spawn errors.

  • Preserved one failed attempt and one successful UI-initiated execution against Arc 72cf12e1-48c8-419f-bc9b-723b38f7cdec.

“A queued command alone is not completion.”
— Milestone 1 proof boundary