docs(contract): P4's violations and §6's backlog shipped — reconcile them

[rejifald]

The contract advertises work that is already done. P4 lists four live violations — all four
shipped — and §6's own Shipped record, sitting a few lines below its backlog table, already
says so. The two halves of the same section contradict each other, which makes the rule read
as one nobody enforces.

Complements #528: that PR reconciles the violation lists on P3/P5/P7/P8/P9/P14/P16/P17/P20 and
leaves P4 and §6's table untouched. This is those two.

P4 — verified against source, not against the record

Listed violation	Reality
ReconnectOptions.maxAttempts → attempts	shipped; maxAttempts survives only as engine.ts's resolved reconnect policy
CacheConfig.maxEntries → entries	shipped; cache.ts reads config.entries, maxEntries is a local
CircuitOptions.failureThreshold → failures	shipped with the P17 CircuitOptions overhaul; resilience.ts reads opts.failures, failureThreshold is a local
paginate.max → pages	shipped, on the extracted PaginateOptions

Three of the four leave a max*/*Threshold name behind on a resolved internal, and that
pattern is the rule's own boundary — so P4 now states it rather than leaving the next reader to
grep and wonder: a max* spelling names a computed value; P4 governs the authoring surface.

§6 — seven of eight rows shipped

Only bodyKind (from-curl) is still live (from-curl.ts:24), so the table is down to that row.
The rest are recorded in §6's Shipped list below it; each verified in source:

• cross-package StitchStore/StitchLike/RequestSeam clashes — qualified per-framework
  (SolidStitchStore, SvelteStitchStore) and per-ecosystem (ExpressRequestSeam, …); the
  ratchet's UNIQUE_WATCH de-listed StitchLike with a written rationale
• queryOptions → stitchQueryOptions across all five framework bindings
• OAuth2Opts/CookieSessionOpts → OAuth2Options/CookieSessionOptions
• anonymous paginate shape → exported PaginateOptions
• SSE helper → streamStitchSse (the old names appear in no src/)
• error-options → StitchErrorOptions
• RedisDriver async close — quit survives only on the upstream client duck-types, which
  P18 keeps at their upstream
  spelling, so the house contract is conformant

Deliberately not touched

The "New shorthand/toggle slots to add" line below the table (.inspect() scalars,
idempotency boolean, throttle string). throttle: string looks shipped — seam.ts folds it
via envelope(t, 'rate') — but the other two need the same per-item verification, and #528 is
already editing P12/P13/P20 territory. Left for a follow-up rather than guessed at here.

Verification

• docs-only; no source, no type, no runtime change
• contract ratchet 0 violations; check-docs-links green (110 routes)
• prettier clean; full-tree pre-push gate green

🤖 Generated with Claude Code