Release 0.1.3: eleven closed defects, and the version everywhere it is stated

pyproject and __version__ move together (0.1.0 shipped with them apart, and
PyPI is immutable), the healthz and --version transcripts re-record, and the
CHANGELOG's Unreleased section becomes 0.1.3.

The release closes, in order of how much they could cost someone: a policy
whose node rules were compiled by nobody, a Slack gate walked past by typing
a flag twice, a deny rule that failed open when the tool name was also a
glob, fan-out payloads that shared one live object between parallel workers,
an unauthenticated 500 on the /live token check, an index that advertised
traces the reader refuses, unknown input keys dropped at the front door, a
Ctrl-C'd node that left no trace event, four unreadable-input tracebacks,
and a --json document that would not parse.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: Shashankss1205

CHANGELOG.md

@@ -7,7 +7,7 @@ and "used to be true" — the two things a reader most needs kept apart.
 
 Entries are newest-last within a release, matching the order they were written.
 
-## Unreleased
+## 0.1.3
 
 - `grapharc plan` drives the governed loop; `PolicyEngine.edge_policy()` compiles the TOML document into the gate `AdmissionChecker` consults, and `grapharc plan --policy` is the caller; `grapharc demo --memory PATH` hands the shipped graphs the durable SQLite store.
 - the shipped registry withheld the trace recorder from its `PlannerNode` and `Materializer`, so `grapharc plan` wrote a file with no `plan` event and **no `start`/`end` pair for any node it executed** — the paragraph above claiming otherwise was true of a hand-wired loop and false of the one the command drives. Both now get the recorder, and a test asserts the phase counts.

README.md

@@ -17,7 +17,7 @@
 
 Build production-grade multi-agent systems with built-in safety, auditability, and control. GraphARC adds a governance layer on top of LangGraph: a planner *proposes* a subgraph, a deterministic checker *admits* it, and only then does anything execute. Every transition is permitted, every loop is bounded, and afterwards you can prove what happened and why it stopped.
 
-**Status:** early days (`0.1.2`) — the API is not stable yet. Known limits are listed in [Status and limits](#status-and-limits); closed ones are in [CHANGELOG.md](CHANGELOG.md).
+**Status:** early days (`0.1.3`) — the API is not stable yet. Known limits are listed in [Status and limits](#status-and-limits); closed ones are in [CHANGELOG.md](CHANGELOG.md).
 
 ![One English question is decomposed by a local model into a nine-node graph — four parallel evidence pulls fanning out of START, a correlate join, a hypothesis fork, and a final report — shown live in the browser: the proposed graph waits grey for human approval, then each node turns amber while it runs and green when it is done.](docs/media/grapharc-decompose.gif)
 

docs/cookbook/01-basics.md

@@ -14,7 +14,7 @@ projection instead and says which fields it dropped.
 `tests/test_cookbook_basics.py` reproduces every recipe here and asserts these
 exact strings, so the page cannot rot quietly.
 
-Verified against `grapharc 0.1.2`, Python 3.14.6, `langgraph 1.2.9`,
+Verified against `grapharc 0.1.3`, Python 3.14.6, `langgraph 1.2.9`,
 `langchain-core 1.5.1`, `pydantic 2.13.4`.
 
 Each snippet is a complete file. Save it and run it; nothing carries over between
@@ -41,7 +41,7 @@ uv run grapharc --version
 Output:
 
 ```
-grapharc 0.1.2
+grapharc 0.1.3
 ```
 
 Everything below uses only the base install — no API key, no network, no optional

docs/cookbook/06-serving-and-ops.md

@@ -1062,7 +1062,7 @@ with TestClient(app) as client:
 ```
 
 ```
-health : {'status': 'ok', 'version': '0.1.2', 'graphs': ['qa']}
+health : {'status': 'ok', 'version': '0.1.3', 'graphs': ['qa']}
 created: 201 queued
 status : succeeded
 answer : Budgets cap iterations, tokens and time.
@@ -1259,7 +1259,7 @@ graphs   : qa
 ctrl-c to stop
 
 $ curl -s localhost:8124/healthz
-{"status":"ok","version":"0.1.2","graphs":["qa"]}
+{"status":"ok","version":"0.1.3","graphs":["qa"]}
 
 $ curl -s -X POST localhost:8124/sessions -H 'content-type: application/json' \
       -d '{"graph":"qa","input":{"question":"how do budgets work?"}}'

grapharc/__init__.py

@@ -9,7 +9,7 @@
 from grapharc.runtime.graph import GraphARC, WritePermissionError
 from grapharc.runtime.state import GraphARCState
 
-__version__ = "0.1.2"
+__version__ = "0.1.3"
 
 __all__ = [
     "GraphARC",

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "grapharc"
-version = "0.1.2"
+version = "0.1.3"
 description = "A graph engineering toolkit on LangGraph: typed state contracts, per-node write permissions, enforced budgets, and JSONL traces that double as replay points."
 readme = "README.md"
 license = "MIT"

tests/test_cookbook_basics.py

@@ -55,7 +55,7 @@
 
 
 def test_version_matches_the_page():
-    assert __version__ == "0.1.2"
+    assert __version__ == "0.1.3"
 
 
 # -- "How do I build and run my first graph?" ------------------------------