fix: bump node images to Karst-capable releases

[Alicepoltora]

op-node v1.13.2 (Apr 2025) and op-geth v1.101503.4 predate the Jovian (Nov 2025) and Karst (Jun 2026) forks — see karst_time in the superchain-registry ink.toml — so a fresh stack cannot follow Ink past Jovian: op-node runs with --rollup.halt=major and the node stalls behind the head (the "divergence" symptom reported in #66, #51, #45).

This bumps to op-node v1.19.8 and op-geth v1.101702.2, the newest stable images published in us-docker.pkg.dev/oplabs-tools-artifacts/images (Karst support starts at op-node v1.17.0 / op-geth v1.101609.x).

It is also time-sensitive: op-node v1.19.8's release notes say Sepolia OP Stack chains must be on op-node v1.19.5+ before the Glamsterdam hardfork of 2026-10-06. (Ink itself is still at Karst — no Lagoon/Glamsterdam time is scheduled for either Ink chain — so this is a forward-compatibility requirement rather than a current breakage.)

Verification

check	result
both tags in the OP Labs registry	yes — manifest fetch returns 200 with linux/amd64 + linux/arm64 for each
newest stable op-node image	v1.19.8 (2026-10-01); v1.19.9 is tagged in git but only v1.19.9-rc.1 is published as an image
newest stable op-geth image	v1.101702.2 (v1.101702.3 exists as a git tag, only rc images published)
--network=ink-mainnet / ink-sepolia resolve in v1.19.8	yes — flag in op-service/flags, names resolve as Name-Network from the embedded superchain registry
Ink config still carried	yes — registry pin has Ink with keep_karst_upgrade_gas = true, matching Ink's post-Karst history
every flag in start-op-geth.sh still exists in op-geth v1.101702.2	yes — checked cmd/utils/flags.go: state.scheme (hash/path), history.state, history.transactions; --txlookuplimit is deprecated but still accepted, and its removal is left to #82

Scoped to the two image tags in docker-compose.yml, so it does not conflict with #82, #88, #90 or #91. Supersedes the pre-Karst bump proposals #72 and #74.

A fresh-sync smoke test before merging would still be appreciated.

[Alicepoltora]

Version-pick verification for reviewers (all checked against sources, Sep 2026):

• Karst support starts at op-node v1.17.0 / op-geth v1.101609.x (per their release notes); both pinned versions here predate Jovian, so a fresh stack halts at Jovian with the configured --rollup.halt=major.
• Both target tags (op-node v1.19.7, op-geth v1.101702.2) exist in us-docker.pkg.dev/oplabs-tools-artifacts/images/ (newest stable tags there).
• --network=ink-mainnet/ink-sepolia still resolves: the flag exists in v1.19.7 (op-service/flags) and names resolve as Name-Network from the embedded registry, which still carries Ink.
• Ink's keep_karst_upgrade_gas = true is present in the registry commit pinned by v1.19.7 (superchain-registry @ 2026-08-21), so derivation matches Ink's post-Karst history.
• --txlookuplimit still exists in op-geth v1.101702.2 but is deprecated in favor of --history.transactions (already set to 0 here), so dropping it preserves behavior.

A fresh-sync smoke test on your side would still be appreciated before merging.