# Resume compatibility proof

Web client base: 3a51807da05203bc2dbfbc489f976e3ba0dc609a
Web client head: 7e6af5728bc16554e6d3bcb029409bb180c88499
Old server: 651accb10002a1c4fbee2d3fa552ef56ef41f523 (parent of native-resume support).

Use current main for the scenario harness. Apply old-server-harness.patch, and put resume-older-server.e2e.ts in scripts/scenarios. Install dependencies in both the harness checkout and an old-server checkout. Copy resume-replay.ndjson over the old server's apps/server/scripts/dev-replay/showcase_transcript.ndjson. This only replaces the synthetic model recording; server and client behavior are unchanged.

Run with T3CODE_DEV_SEED=0, T3_SCENARIO_OLD_SERVER_DIR pointing to the old-server checkout, and T3_SCENARIO_INHERIT_ENV=T3CODE_DEV_SEED,T3_SCENARIO_OLD_SERVER_DIR:

    vp run scenarios:prove scripts/scenarios/resume-older-server.e2e.ts --base 3a51807da05203bc2dbfbc489f976e3ba0dc609a --head 7e6af5728bc16554e6d3bcb029409bb180c88499 --upload-command "ghdrop upload"

Each side uses a fresh isolated server database and a Chromium browser at 1280x800 in the light theme. The project is created through the real server API. The replay agent streams the showcase recording with relative synthetic file paths. Stop generation, let Stop's 500 ms click guard expire, and click Resume with an empty composer and no attachments. The scenario requires a visible nonempty continuation message.

The replay model accepts empty prompts, so this proves the blank-message client defect, not Antigravity's provider-specific rejection. No real provider account is used.
