feat: add typed ESI transport extensions

docs/parallel-worktrees.md

@@ -8,6 +8,18 @@
 
 **Planning baseline:** `fdcc486` (`Initial Commit`). The roadmap records an earlier 97-test gate; each prototype change reruns the current local suite. Existing `jobs`, `userPreferences` and `referenceSyncMetadata` tables are placeholders, not services.
 
+**T06 evidence:** The centralized ESI client now has fixed typed asset, asset-name,
+asset-location, wallet-balance, and market-read strategies with bounded response
+bytes/rows/pages, bounded retries, abort-first cleanup, validators, canonical int64
+helper bodies, complete scoped authority-context cache identity, cooldown queries,
+and runtime schemas. Asset snapshots report bounded non-atomic coverage; page-one
+revalidation is not presented as a transaction. T07 durable scheduling/worker
+orchestration, T08 location/service orchestration, and T13 wallet persistence/UI/
+service orchestration remain unimplemented; production-readiness gates remain
+deferred. The narrow `beginSync` expected-authority fence is part of T06's atomic
+bridge contract: it prevents transport cache authority from being published under
+a different T05 grant/revision/credential fence; it is not T07 durable worker orchestration.
+
 ## Execution model
 
 - One task per branch/worktree; branch suggestions below are labels, not created branches.