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

Upstream `ponder` published 0.16.8 as `latest`, so a fresh `npm install ponder`
now resolves to a version the fork didn't yet cover. This adds the compat row.

Verification (`scripts/sync-upstream.sh 0.16.8 --test`):
- wiring/0.16.8.patch is byte-identical to 0.16.6/0.16.7 (sha256 ddd12dd5…, 10/10 files) —
  the wiring is version-agnostic across the seam-stable range.
- patch applies cleanly (zero rejects), builds, full Portal suite 310/310 green on ponder@0.16.8.
- 0.16.7→0.16.8 is a realtime-only upstream change (isAsyncExecutionChain / chainId 143,10143
  in sync-realtime/index.ts + utils/finality.ts, so async-execution chains can surface blocks
  before logsBloom is execution-ready). Neither file is on the graft surface (sync-historical,
  runtime/historical, sync-store, rpc, sync) → seam untouched; the 81 Portal realtime tests pass.

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

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

Author: dzhelezov