chore(compat): cover ponder@0.16.9 — add 0.16.9-sqd.1 row (published:false)

Upstream `ponder` published 0.16.9 as `latest` on 2026-07-10, so a fresh
`npm install ponder` now resolves to a version the fork didn't yet cover.
This adds the compat row + wiring/0.16.9.patch (a verbatim copy of
wiring/0.16.8.patch).

Verification (`scripts/sync-upstream.sh 0.16.9 --test`):
- 0.16.8→0.16.9 is a single-file upstream change: src/indexing-store/cache.ts
  only (ponder-sh/ponder#2323 — fix p.bytes() bytea encoding on the Postgres
  COPY flush path, emitting \x<hex> for Buffer values to fix "DelayedInsertError:
  invalid byte sequence for encoding UTF8: 0x00"). Confirmed by diffing the
  0.16.8 and 0.16.9 npm tarballs.
- indexing-store/cache.ts is off the graft surface (sync-historical,
  runtime/historical, sync-store, rpc, sync, sync-realtime); every upstream file
  the wiring patch modifies is byte-identical between 0.16.8 and 0.16.9, so the
  patch applies cleanly (zero rejects).
- builds, and the full Portal suite is 328/328 green on ponder@0.16.9.
- The fork passively inherits the upstream bytea-COPY correctness fix.

published:false — publishing to npm is a deliberate, human-reserved step;
0.16.8-sqd.1 stays --tag latest until then.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: dzhelezov