teleo-infrastructure/docs/reports/leo-working-state-20260709/leo-post-skill-repair-direct-claim-summary-current.md
twentyOne2x 63278b6354
Some checks are pending
CI / lint-and-test (push) Waiting to run
Record Leo post-repair direct-claim proof
2026-07-10 06:22:11 +02:00

1.4 KiB

Final State-Semantics Repair Direct-Claim Proof Summary

Result: passed.

  • Deployed SHA verified: 090becae1621436467610e529d6328d70964d11f
  • Deploy path: /opt/teleo-eval/workspaces/deploy-infra
  • Last deploy stamp: 090becae1621436467610e529d6328d70964d11f
  • Gateway after deploy and suite: active/running, MainPID=2999690, NRestarts=0, ExecMainStartTimestamp=Fri 2026-07-10 03:47:11 UTC

Handler Suite

  • Remote report: /tmp/leo-post-skill-repair-direct-claim-current.json
  • Remote report SHA256: 6fffdbafc18913c4fc62feb00906988dee2e696d279f22dd284951a79451f39c
  • Handler runtime: pass_runtime=true
  • DB counts changed: false
  • Prompt IDs: DC-01, DC-02, DC-03, DC-04, DC-05, DC-06

Strict Score

  • Score pass: true
  • Passes: 6/6
  • Failed prompt IDs: none
  • Failed signals: none
  • No-overclaim failures: none

Safety

  • Posted to Telegram: false
  • Production DB apply ran: false
  • Live profile changed: false
  • Temp profile removed: true
  • Cleanup readback: gateway active/running, no handler process left, this run's temp profile /tmp/leo-direct-claim-handler-q2bsc7sq absent

Still Not Done

  • Rich approved proposals are still not production-applied to canonical public.* rows.
  • The autonomous apply worker is not the stable production default.
  • GCP parity is not proven.
  • Telegram-visible DC-01..DC-06 was not posted or captured in this lane.