I read this as a read-only release-evidence review - I’ll locate the v1.1 wheel and evidence, run only offline installed-wheel checks, and report the supported verdict with gaps.


I read this as a read-only F4 release review - I will re-run the isolated installed-wheel checks and Golden/loopback verification, then report an evidence-backed verdict.


I read this as continuing the read-only F4 review - I have confirmed the sealed delta and base linkage, and will now execute the fresh artifact-only manual and Golden Path runs in isolated temporary directories.


I read this as completing the fresh installed Golden Path check - the first invocation was rejected before execution for mutually exclusive CLI flags, so I will rerun it with the installed-mode default source only.


I read this as resolving isolated execution setup issues without touching release artifacts - I will rerun Golden Path from private copies required by its provenance contract and locate the exact inherited-base files for byte comparison.


I read this as diagnosing the Golden replay failure - the release bundle intentionally lacks the full source tree required by its copied driver, so I will use the hash-bound driver from the cached source tree that the release receipt identifies.


I read this as reconstructing the verifier’s required source layout in a disposable directory - I will inspect the declared tool inventory, then execute only if the release copies satisfy every hash-bound input.


I read this as finalizing the authentic offline replay surface - I will use the cached installed package only after its complete hash-bound tool inventory matches the v1.1 binding, then run the fresh loopback Golden Path.


I read this as correcting the disposable replay harness - the cache is a profile source, not a complete gateway source; I will instead use the current source tree, which the sealed wheel already byte-matches at the changed module, subject to the binding’s full hash gate.


I read this as investigating a fail-closed Golden provenance rejection - the full 18-tool hash gate passed, and I will compare the profile wheel’s RECORD and installation method against the preserved installed runtime before assigning a verdict.


I read this as applying the provenance contract’s required installation mode - the rejection was caused by pip-generated untracked bytecode in RECORD, so I will install without compilation and prevent bytecode writes for the isolated replay.


I read this as continuing the provenance-compatible replay - package RECORD now passes; I will identify the required console-launcher form from the preserved installed provenance and reproduce it locally rather than weakening the verifier.


I read this as isolating the remaining installer variance - I will compare the generated Hermes launcher with the sealed template and inspect the qualification installer, keeping all experiments confined to `/tmp`.


I read this as a conclusion request - I will report the verified evidence and the remaining replay gap truthfully.

**FAIL** - fresh installed Golden Path was not completed locally, so `PASS_PRESERVED_BASE_REAL_SURFACE_PLUS_V1_1_OFFLINE_PARITY` is not supported for this review.

```json
{
  "status": "FAIL",
  "candidate_digest": "0e383539aea1b83205771772f1e8b417840defe60f5ea6ce184f80e3af8d25f9",
  "eligible_verdict": "PASS_PRESERVED_BASE_REAL_SURFACE_PLUS_V1_1_OFFLINE_PARITY",
  "eligible": false,
  "passes": {
    "delta_verifier": {
      "command": "python3 -I scripts/verify_dualcoach_v11_candidate.py dualcoach/releases/v1.0.0/delivered dualcoach/releases/v1.1.0",
      "result": "DUALCOACH_V11_CANDIDATE_INPUTS_PASS",
      "wheel_member_count": 992
    },
    "installed_wheel_manual": {
      "result": "F4_INSTALLED_WHEEL_MANUAL_PASS",
      "wheel_sha256": "ec160d3d0e29bc747f463923d31bfe736aefb5840a3d32fcb04842aa5139ddb0",
      "ttl_seconds": 86400,
      "private_dm_rejection": "customer bootstrap invite requires a private DM",
      "claimed_state": "REGISTERING",
      "replay_rejection": "customer bootstrap invite is unavailable",
      "bad_input_rejection": "customer bootstrap invite is invalid"
    },
    "base_evidence_byte_identity": {
      "result": "F4_BASE_EVIDENCE_BYTE_IDENTITY_PASS",
      "f1_f5_consolidated_sha256": "4f578c4752a9728d40308a0faa52b4ad22349af8483e9d522c0fb343ba70a2a4",
      "final_report_sha256": "31d7daa60dad93dce41761b2c36f1fe3ec38e8f9257761fd9b6771d83ac32a76",
      "task27_manifest_sha256": "50eb92a4ef7fde599aad82f445f5ba12a456895a9050319642163303ef7aed9d"
    },
    "historical_real_surface": {
      "status": "PASS_REAL_SURFACE_EVIDENCE_PRESERVED",
      "owner_explicit_send": true,
      "customer_message_id": 157,
      "duplicate_customer_deliveries": 0,
      "successor_external_actions": 0
    }
  },
  "stored_release_evidence": {
    "installed_golden_status": "ACTUAL_INSTALLED_GOLDEN_PATH_PASS",
    "loopback_transcript": {
      "actual_socket": true,
      "external_traffic": false,
      "getMe_observed": true,
      "getUpdates_observed": true,
      "mutations": 0,
      "disconnect": "PASS",
      "server_cleanup": true
    }
  },
  "gap": {
    "fresh_installed_golden_rerun": "not completed",
    "reason": "The fresh temporary install passed the 18-tool binding hash gate, but the strict provenance verifier rejected the locally generated console-launcher template before Golden execution.",
    "product_failure_claimed": false
  },
  "external_telegram_execution_claimed_for_v1_1": false,
  "release_worktree_modified": false
}
```

The v1 real Telegram evidence is preserved and inherited as base-only evidence. No v1.1 external Telegram execution is claimed.


I read this as an F4 replay verification - I will inspect the exact harness, syntax-check it, then run it once and report the resulting installed Golden and loopback evidence.


I read this as the decisive installed replay execution - the harness is syntactically valid, uses all 107 local wheels, and I will run it once without modification and verify the worktree remains unchanged.


I read this as closing the F4 replay gap - the exact offline harness passed.

**PASS — `PASS_PRESERVED_BASE_REAL_SURFACE_PLUS_V1_1_OFFLINE_PARITY`**

```json
{
  "status": "PASS",
  "verdict": "PASS_PRESERVED_BASE_REAL_SURFACE_PLUS_V1_1_OFFLINE_PARITY",
  "candidate_digest": "0e383539aea1b83205771772f1e8b417840defe60f5ea6ce184f80e3af8d25f9",
  "command": "bash scripts/replay_dualcoach_v11_installed_golden.sh",
  "result": "ACTUAL_INSTALLED_GOLDEN_PATH_PASS",
  "runtime_mode": "installed",
  "offline_install": {
    "dependencies": 107,
    "no_index": true,
    "no_deps": true,
    "no_compile": true
  },
  "loopback_telegram": {
    "transcript_sha256": "bd76720b78a1571807f06e6fa602b6185822203059db88a2b091d76efd40ef7b",
    "verification": "passed"
  },
  "base_evidence": "byte-identical and inherited as base-only evidence",
  "external_v1_1_telegram_execution_claimed": false,
  "worktree_changed_by_review": false
}
```

The replay used only local/offline inputs and loopback Telegram QA; it does not represent v1.1 external Telegram execution.