CI / lint-and-test (push) Waiting to run

Details

- Add reusable Teleo/Leo skills for VPS, GCP, Telegram, KB changes, provenance, and handoff onboarding.
- Add guarded KB proposal tooling for approved rich proposals, apply packets, and rollback proof.
- Add Cory-style open-ended benchmark prompts and tests alongside the precise regression canaries.

`.agents/skills/leo-telegram-canary-ops/SKILL.md`
`.agents/skills/teleo-gcp-parity-ops/SKILL.md`
`.agents/skills/teleo-infra-provenance/SKILL.md`
`.agents/skills/teleo-kb-db-change-workflow/SKILL.md`
`.agents/skills/teleo-leo-onboarding/SKILL.md`
`.agents/skills/teleo-proof-handoff/SKILL.md`
`.agents/skills/teleo-vps-runtime-ops/SKILL.md`
`.agents/skills/working-leo-cory-outcomes/SKILL.md`
`docs/reports/leo-working-state-20260709/claim-source-contract-preview-current.md`
`docs/reports/leo-working-state-20260709/cory-expected-working-leo-outcomes-20260709.md`
`docs/reports/leo-working-state-20260709/current-truth-index.md`
`docs/reports/leo-working-state-20260709/fable-leo-teleo-onboarding.md`
`docs/reports/leo-working-state-20260709/gcp-db-parity-current-blocker-20260709.json`
`docs/reports/leo-working-state-20260709/helmer-7powers-creation-plan.json`
`docs/reports/leo-working-state-20260709/kb-apply-canary-execute-current.md`
`docs/reports/leo-working-state-20260709/kb-apply-canary-plan-current.md`
`docs/reports/leo-working-state-20260709/leo-db-state-13-skill-pack.svg`
`docs/reports/leo-working-state-20260709/operator-surface-map.md`
`docs/reports/leo-working-state-20260709/production-apply-packet-current.md`
`docs/reports/leo-working-state-20260709/rich-proposal-creation-plan-mapped-current.md`
`docs/reports/leo-working-state-20260709/skill-pack-manifest.json`
`docs/reports/leo-working-state-20260709/skill-pack-readme.md`
`docs/reports/leo-working-state-20260709/telegram-gateway-handler-canary-current.json`
`docs/reports/leo-working-state-20260709/telegram-gateway-handler-canary-current.md`
`docs/reports/leo-working-state-20260709/telegram-live-canary-current.json`
`docs/reports/leo-working-state-20260709/telegram-live-canary-current.md`
`docs/reports/leo-working-state-20260709/telegram-live-db-write-canary-20260709.json`
`docs/reports/leo-working-state-20260709/telegram-live-db-write-canary-20260709.md`
`docs/reports/leo-working-state-20260709/working-leo-current-state-20260709.md`
`docs/reports/leo-working-state-20260709/working-leo-definition-20260709.md`
`docs/reports/leo-working-state-20260709/working-leo-execution-plan-current.md`
`docs/reports/leo-working-state-20260709/working-leo-open-ended-benchmark-spec.json`
`scripts/approve_proposal.py`
`scripts/kb_claim_source_contract_preview.py`
`scripts/kb_rich_proposal_apply_packet.py`
`scripts/kb_rich_proposal_creation_plan.py`
`scripts/working_leo_open_ended_benchmark.py`
`tests/test_approve_proposal.py`
`tests/test_kb_claim_source_contract_preview.py`
`tests/test_kb_rich_proposal_apply_packet.py`
`tests/test_kb_rich_proposal_creation_plan.py`
`tests/test_working_leo_open_ended_benchmark.py`

2026-07-09 22:56:48 +02:00

2.9 KiB

Raw Blame History

Telegram Live DB Write Canary - 2026-07-09

Generated UTC: 2026-07-09T20:09:37Z

Scope

Live Telegram-visible test in the authenticated Chrome Telegram Web Leo group (web.telegram.org/a/#-5146042086). User explicitly authorized Leo bot test messages. The test asked Leo to stage a review proposal in kb_stage only and explicitly forbade canonical public.* mutation or runtime-memory changes.

Result

Turn 3 sent at 2026-07-09 22:06 Europe/Zurich.
Leo replied LIVE_TG_TURN3_STAGED.
Leo staged proposal 8dfedb3f-3aa4-4200-970f-4c0016f6869f in kb_stage.kb_proposals.
VPS Postgres verified the proposal row exists:

id                                      status          proposal_type  proposed_by_handle  channel  source_ref
8dfedb3f-3aa4-4200-970f-4c0016f6869f  pending_review  add_edge       leo-telegram-live   canary   telegram:leo:-5146042086:WL-LIVE-TG-CORY-20260709-T3
created_at: 2026-07-09 20:06:34.042946+00
rationale: Marker WL-LIVE-TG-CORY-20260709-T3: prove Telegram to Leo to DB proposal write path. Read-only canary -- no public table mutation.

Canonical tables stayed untouched after the T3 timestamp:

claims_marker_rows  sources_marker_rows
0                   0

claims_created_after_t3  sources_created_after_t3  edges_created_after_t3  evidence_created_after_t3
0                        0                         0                       0

Turn 4 sent at 2026-07-09 22:08 Europe/Zurich.
Leo replied LIVE_TG_TURN4_READBACK.
Leo remembered T3, read back proposal 8dfedb3f-3aa4-4200-970f-4c0016f6869f, confirmed pending_review, confirmed source_ref=telegram:leo:-5146042086:WL-LIVE-TG-CORY-20260709-T3, and reported zero new rows in public.claims, public.sources, public.claim_edges, and public.claim_evidence after 2026-07-09 20:06:30 UTC.

VPS Stability

leoclean-gateway.service remained stable after T3 and T4:

MainPID=3252143
NRestarts=0
ExecMainStartTimestamp=Thu 2026-07-09 06:59:44 UTC
ActiveState=active
SubState=running

Screenshots

Turn 3 staged reply: /Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/telegram-live-canary-20260709/telegram-live-turn3-staged.png
Turn 4 readback reply: /Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/telegram-live-canary-20260709/telegram-live-turn4-readback.png

Claim Ceiling

This proves the live VPS Leo Telegram path can:

Receive a live group instruction.
Write a guarded review proposal to kb_stage.kb_proposals.
Remember that write in the next conversational turn.
Read back the staged row and distinguish staging from canonical application.
Leave canonical public.* tables unchanged.

It does not prove production application of rich Cory-approved packets. Those still require reviewed mappings and a full production apply authorization.

2.9 KiB Raw Blame History