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

1.9 KiB

Raw Blame History

name	description
teleo-gcp-parity-ops	Use for Teleo/Leo GCP parity, Cloud SQL/cutover readiness, account selection, non-interactive auth blockers, and separating GCP from VPS Telegram proof.

Teleo GCP Parity Ops

Job

Handle GCP parity as its own lane, with precise auth/account/project facts and no overclaiming from VPS or local proof.

Trigger Phrases

"GCP parity"
"move Leo to GCP"
"Cloud SQL Teleo"
"teleo-501523"
"GCP blocker"
"VPS then GCP"

Current Known Facts

Project: teleo-501523
Expected project-access account: billy@livingip.xyz
Retained blocker: selected account cannot refresh access token non-interactively.
Other locally available accounts refresh but lack access to teleo-501523.
Current artifact: docs/reports/leo-working-state-20260709/gcp-db-parity-current-blocker-20260709.json

Always refresh if cheap before making a current claim.

Status Split

Never claim GCP complete from:

VPS service health,
Telegram group canaries,
local DB rehearsals,
GCP account selection alone.

GCP parity needs its own:

auth readback,
project access readback,
Cloud SQL or target DB readback,
runtime/config parity readback,
Telegram or operator path proof if the target is GCP-hosted Leo.

Safe Actions

Allowed:

gcloud config list / account list readbacks,
non-secret auth status checks,
project access probes,
read-only SQL or service discovery where auth works,
blocker artifact updates.

Stop for:

password/OTP/KYC,
raw secret requests,
irreversible cloud changes,
production cutover without explicit authorization.

Blocker Format

If auth is still blocked, retain:

{
  "current_canary": "gcloud account can read teleo-501523 and target DB metadata",
  "attempted_routes": [],
  "exact_gate": "",
  "clear_CTA": "",
  "next_non_user_action": ""
}

The CTA must name the exact account and what the operator should do, not a vague "reauth needed."

1.9 KiB Raw Blame History