Edward Langley
b1a989d8cf
CI / Build all bundles (push) Has been cancelled
CI / Test and lint (host) (push) Has been cancelled
CI / wasm32 check (browser bundle crates) (push) Has been cancelled
CI / Browser JS unit tests (node --test) (push) Has been cancelled
CI / Knowledge base consistency (push) Has been cancelled
CI / Lint the harness crate (push) Has been cancelled
CI / Browser harness (OPFS contract + shell) (push) Has been cancelled
CI / Deploy to GitHub Pages (push) Has been cancelled
From PRs #144/#148/#151. `AGENTS.md`'s remote note gains the worktree-base vector: a branch cut from the orchestrator's local `main` inherits whatever that checkout merged but did not push, and nothing in the branch says so — which is how #148's diff came to name the three orchestrator-only files and read as a rule violation rather than a base problem. Four facts. A fold test must fold the batch the producer really emits — a `Binding::Sequence` flattens into one vec, and a per-step batching cannot see intra-batch order at all. A type name is not a field, measured: one 14-site rival left 14 of 16 assertions passing, while an assertion on a *fieldless* effect is complete rather than smoke. A registry with two arms demotes the weaker caller, and neither direction is safe by default. And a clean text merge can delete an evidence entry that no gate checks. Two gate traps: `--check-evidence` prints the comment cap FIRST, so reading it through `tail -1` drops the half that was always there; and a compound command refused by the worktree shell guard runs NEITHER part. kb_consistent: TRUE, 798 facts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FC2jVn8Au7E9JPkw6bwXXH