docs: record the two example test gaps left by the review fixes

[btravers]

Follow-up to #11. That PR shipped two deliberate shortcuts in
examples/order-api whose reasoning lived only in the PR description — which is
exactly where a deferral goes to be forgotten. Both are now in CLAUDE.md's
"Deferred, deliberately" list, alongside the rest of this repo's deferrals.

Gap	Ceiling	Trigger to revisit
No test for the permanent server 'error' listener	needs vi.mock("node:http") hoisted above describe, breaking Test conventions rule 1 in the teaching-surface workspace; vi.spyOn cannot patch a node builtin (Cannot redefine property: createServer)	a second example needing the same capture, at which point a shared fixture earns its keep
closeAfterResponse's headersSent branch is uncovered	unreachable through this router — endWith puts writeHead and end adjacent, and oRPC serialises these small bodies in one go	adding a streamed route

Each entry records why the gap is acceptable, not just that it exists: the
first is guarded by its kernel twin (probes.spec.ts → "does not throw when
the server emits an error after binding" — the same two lines for the same
reason), and the second costs nothing at the gate because examples/ carries no
coverage threshold.

Recorded here rather than marked inline.CLAUDE.md already states that
rationale belongs in it and not in comments, with one carve-out — a comment
guarding a specific line against a plausible "simplification". The headersSent
branch already has that comment; neither of these is a line needing a guard, so
both belong in the list.

Docs only: no code, no changeset (CLAUDE.md is not in the published tarball —
files: ["dist"]).

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates the repository’s root CLAUDE.md to permanently document two known, deliberate test/coverage gaps in examples/order-api that were previously only captured in PR #11’s description, keeping deferral rationale centralized alongside other documented tradeoffs.

Changes:

• Add a deferral entry explaining why examples/order-api’s permanent server 'error' listener fix lacks a dedicated test (and what would trigger revisiting it).
• Add a deferral entry explaining why closeAfterResponse’s headersSent branch remains uncovered (and what would make it coverable).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.