# Leo Post-Deploy Direct-Claim Repeat Proof

## Result

- Deployed commit: `0183a5c805fa3b51d638267afd20f67a1bc3777f`.
- Live skill SHA-256: `0af66196c20a25370dac88365e4df4ae5e634bc81140675379cf899404b249ba`.
- Repeated isolated trials: `3`.
- Replies scored: `18/18`.
- Strict score: `6/6` in every trial.
- Telegram messages sent: `false`.
- Production apply executed: `false`.

## Stability

Every trial preserved the same production readback:

- claims: `1837`;
- sources: `4145`;
- claim evidence: `4670`;
- claim edges: `4916`;
- proposals: `26`;
- gateway PID: `2403328`;
- restarts: `0`;
- start timestamp: `Sun 2026-07-12 09:14:10 UTC`.

Every temporary profile was removed. The final VPS cleanup readback found no
`/tmp/leo-direct-claim-handler-*` directories.

## Trials

- Trial 1: run `bdefcfe98ba2`, strict `6/6`.
- Trial 2: run `f68219fcbca7`, strict `6/6`.
- Trial 3: run `05810612557f`, strict `6/6`.

## Claim Ceiling

This proves repeated post-deploy no-post GatewayRunner behavior under fresh
temporary profiles. It does not correct the already-retained Telegram-visible
`DC-05` reply, send another Telegram message, or prove production KB mutation.

Machine-readable proof:
`docs/reports/leo-working-state-20260709/leo-post-deploy-direct-claim-repeat-current.json`.
