I read this as a read-only release reliability audit - I’ll inspect the candidate and release artifacts, independently rerun the specified boundary, suite, installation, timeout, and RECORD checks, then return a JSON-ready verdict with evidence and residual risk.


The artifact chain and code seam are now mapped: the candidate is bound to source commit `ae909026...`, and the shipped Hermes wheel differs from v1.0 only in the invite TTL member plus its RECORD row. I’m moving to independent execution and integrity recomputation, including explicit source/wheel boundary probes and reconciliation of the j24 diagnostic against clean reruns.


I read this as a read-only F3 reliability audit - I verified the TTL seam, exactly-once behavior, Golden Paths, suite receipts, timeout diagnosis, and wheel integrity.

## Verdict: PASS

### Evidence

- Candidate `0e383539...d25f9` is bound to source commit `ae90902686a66fd6b66dfacba0f373a8011a594a`.
- Independent source and installed-wheel probes passed:
  - TTL exactly `86,400` seconds.
  - Valid at `23:59:59`.
  - Claim succeeds at `23:59`, entering `REGISTERING`.
  - Unclaimed invite rejected exactly at `24:00`, entering `EXPIRED`.
  - Wrong-chat/private-DM mismatch rejected without consuming the invite.
  - Replay after claim rejected; generation remained exactly `2`.
- Fresh Golden Path executions completed successfully:
  - Source mode, candidate and wheel bindings exact.
  - Installed mode from the exact candidate wheels, candidate and wheel bindings exact.
  - Both exercised the full lifecycle, local Telegram loopback, duplicate rejection, durable delivery, cleanup, and terminal inventory.
- Candidate verifier: `DUALCOACH_V11_CANDIDATE_INPUTS_PASS`.
- Verifier and TTL tests: `6 passed`.
- Hash-bound qualification evidence:
  - Focused Task26: `306 passed`.
  - Expanded Task26: `76 passed`.
  - Full Gateway j8: `8,552 passed`, `0 failed`, from `8,609` collected across `385` files.
  - Serial timeout recheck: `225 passed`.
- j24 diagnostic was not hidden:
  - Initial j24/140-second run had two internal timeout failures and one long-file ceiling.
  - The same affected files passed serially (`225 passed`).
  - Full j8 rerun passed with a 600-second ceiling; slowest file took `326.47s`.
  - Classification as resource contention is justified, though it does not mathematically eliminate latent timing sensitivity.
- Exact wheel integrity:
  - Both wheels contain exactly `992` members and `992` complete RECORD rows.
  - Every size and SHA-256 RECORD binding recomputed successfully.
  - Only changed members:
    1. `gateway/platforms/telegram_customer_bootstrap.py`
    2. `hermes_agent-0.17.0.dist-info/RECORD`
  - Source change is exactly `timedelta(minutes=30)` to `timedelta(hours=24)`.
  - All inherited delivery/exactly-once code is therefore byte-identical outside the TTL seam.
- Release chain:
  - Qualification receipt SHA-256: `0bb05f14...b7fca`
  - Full Gateway receipt SHA-256: `0563de7f...79c3b`
  - Inventory SHA-256: `9478cab8...cc5d47`
  - All `212` inventoried files matched size and digest.

### Residual risk

- **Low:** the initial j24 timeouts remain a genuine observed stress-run failure. Clean serial and j8 runs strongly support contention, but timing-sensitive behavior can never be disproven solely by reruns.
- Raw v1.1 logs for the `306/76/8552/225` runs are not included in the compact release root; those counts were independently validated through the hash-bound qualification and Gateway receipts. Fresh Golden Paths and boundary behavior were executed directly during this audit.
- No project files were edited. A concurrent F5 review artifact appeared during the audit and was left untouched.

```json
{
  "task_id": "st_01a01fa2",
  "lane": "F3_reliability_exactly_once",
  "verdict": "PASS",
  "candidate_digest": "0e383539aea1b83205771772f1e8b417840defe60f5ea6ce184f80e3af8d25f9",
  "source_commit": "ae90902686a66fd6b66dfacba0f373a8011a594a",
  "ttl": {
    "seconds": 86400,
    "live_at_23_59_59": true,
    "claim_at_23_59": "REGISTERING",
    "expired_at_24_00": true,
    "wrong_chat_rejected_without_consumption": true,
    "replay_rejected": true
  },
  "golden_paths": {
    "fresh_source": "PASS",
    "fresh_installed": "PASS"
  },
  "tests": {
    "boundary_and_verifier": "6 passed",
    "focused_task26": "306 passed",
    "expanded_task26": "76 passed",
    "full_gateway": {
      "workers": 8,
      "collected": 8609,
      "passed": 8552,
      "failed": 0,
      "files": 385
    },
    "serial_timeout_recheck": "225 passed"
  },
  "j24_diagnostic": {
    "workers": 24,
    "timeout_seconds": 140,
    "observed": "two internal timeout failures and one long-file ceiling",
    "assessment": "resource contention supported by clean serial and j8 reruns; retained as residual timing risk"
  },
  "wheel_integrity": {
    "status": "PASS",
    "members": 992,
    "record_rows": 992,
    "changed_members": [
      "gateway/platforms/telegram_customer_bootstrap.py",
      "hermes_agent-0.17.0.dist-info/RECORD"
    ],
    "delivery_logic_byte_identical_outside_ttl_seam": true
  },
  "residual_risk": "LOW",
  "edits": 0
}
```