# PR #72 VPS Auto-Deploy Runtime Readback

Observed UTC: `2026-07-10T16:00:14Z`

## Result

The VPS auto-deploy timer fast-forwarded `/opt/teleo-eval/workspaces/deploy-infra`
and `/opt/teleo-eval/.last-deploy-sha` to merge commit
`771679061f0a0b6463fb7d9cf530eb9d2d4e5440` at `15:53:13-20Z`.

This was a source-checkout synchronization, not a live Leo behavior change:

- The auto-deploy journal says `No Python changes - services not restarted`.
- PR #72 changed neither `hermes-agent/leoclean-bin` nor
  `hermes-agent/leoclean-skills/vps`.
- `leoclean-gateway.service` remained active/running on PID `2999690`, with
  `NRestarts=0` and start time `2026-07-10T03:47:11Z`.
- `teleo-kb-apply-worker.service` remained disabled, inactive, and dead.
- No production permission migration or canonical proposal apply ran.

## Database Readback

The read-only transaction returned:

| Table | Rows |
| --- | ---: |
| `public.claims` | 1837 |
| `public.sources` | 4145 |
| `public.claim_evidence` | 4670 |
| `public.claim_edges` | 4916 |
| `public.reasoning_tools` | 17 |
| `kb_stage.kb_proposals` | 26 |

## Claim Ceiling

PR #72 source and repo-native skills are present in the VPS deploy checkout.
The gateway process was not restarted, its committed profile source paths were
unchanged by the commit, the apply worker stayed disabled, and the count
endpoints stayed unchanged. This is not byte-for-byte database proof and does
not predict behavior after a future restart.
