v0.1.2 — LangGraph recovery across checkpoint boundaries

This release adds a runnable LangGraph integration using the official SQLite checkpointer and the installed tool-journal package. It reproduces two recovery boundaries: an HTTP service commits but loses its response, and the journal saves a receipt before LangGraph records the node's result.

The graph uses a stable operation identity across threads. Idempotent recovery retrieves the original downstream receipt; a journal-confirmed operation replays without another HTTP call; an expired manual operation stays indeterminate. The tests kill actual child processes and reopen the official graph checkpoints. No model, API key, or external service is needed.

Source: d46d4fa0c971d5eb9cf8d221e9029efbd36c5632.

• LangGraph example and guarantees
• Process-kill integration tests
• Release-source CI
• Release-source CodeQL
• Reviewed change

Validation covers 93 core tests, seven targeted mutation checks, real package installation with a TypeScript consumer, and seven LangGraph integration tests. The six Linux/Windows/macOS × Node 24.15.0/26 jobs also install the native SQLite checkpointer and run the demo. Framework dependencies remain isolated from the core library's zero-runtime-dependency package. Dependabot now monitors the example independently.

The public-tree guard uses Git's candidate-file list and checks tracked ignored files without traversing installed dependencies. Node ambient types are declared explicitly. GitHub Actions updates are pinned by commit.

Release assets include the installable npm archive, the raw local protocol-2 experiment with source and runtime metadata, a provenance record, and SHA-256 checksums. The experiment has 100 runs: five strategies × four boundaries × five repetitions. It is a controlled correctness experiment, not a throughput benchmark or 100 distinct failure types. This remains source/archive distribution; the package has not been published to the npm registry.

The downstream idempotency contract prevents duplicate effects in both idempotent controls. The journal adds local receipt replay, operation coordination and explicit uncertainty. It cannot extend the provider's key-retention period, fence an external service, or establish cross-service exactly-once execution. SQLite remains synchronous and local to one host; neither this release nor its passing checks establishes multi-host availability, a production SLA, or an independent security audit.