699a9e7917
Some checks are pending
CI / lint-and-test (push) Waiting to run
- 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`
87 lines
2.3 KiB
Markdown
87 lines
2.3 KiB
Markdown
---
|
|
name: teleo-vps-runtime-ops
|
|
description: Use for Leo VPS navigation, service health, Docker/Postgres readbacks, clone DB rehearsals, report sync, and runtime stability verification without changing live Leo behavior.
|
|
---
|
|
|
|
# Teleo VPS Runtime Ops
|
|
|
|
## Job
|
|
|
|
Navigate and verify the VPS safely, with exact readbacks and no surprise live-runtime changes.
|
|
|
|
## Trigger Phrases
|
|
|
|
- "Leo on VPS"
|
|
- "check VPS stability"
|
|
- "navigate Teleo VPS"
|
|
- "leoclean service"
|
|
- "run DB rehearsal on VPS"
|
|
- "sync reports to VPS"
|
|
|
|
## Known Surfaces
|
|
|
|
- Host: `77.42.65.182`
|
|
- SSH user: `root`
|
|
- Local key path is available; never print private key contents.
|
|
- Service: `leoclean-gateway.service`
|
|
- DB container: `teleo-pg`
|
|
- DB: `teleo`
|
|
- Profile reports: `/home/teleo/.hermes/profiles/leoclean/kb_stage/reports/`
|
|
- Deploy/source area: `/opt/teleo-eval/workspaces/deploy-infra`
|
|
|
|
## Required Fresh Readbacks
|
|
|
|
Before claiming runtime state, read:
|
|
|
|
```bash
|
|
systemctl show leoclean-gateway.service -p ActiveState -p SubState -p MainPID -p NRestarts -p ExecMainStartTimestamp -p User -p WorkingDirectory
|
|
```
|
|
|
|
Before claiming DB state, use `docker exec teleo-pg psql -U postgres -d teleo` and query exact tables/rows.
|
|
|
|
Before claiming cleanup, query disposable DBs:
|
|
|
|
```sql
|
|
select datname from pg_database where datname like 'teleo%rehearsal%20260709' or datname like 'teleo%packet%20260709';
|
|
```
|
|
|
|
## Mutating Boundaries
|
|
|
|
Allowed when needed:
|
|
|
|
- read-only service/DB inspection,
|
|
- disposable clone DB creation and drop for rehearsal,
|
|
- SQL rollback transactions,
|
|
- syncing report artifacts to the report directory,
|
|
- no-secret file checks.
|
|
|
|
Not allowed from this skill alone:
|
|
|
|
- restarting or changing the live Leo service,
|
|
- changing live runtime config,
|
|
- production DB commit/apply,
|
|
- exposing secret contents,
|
|
- deleting non-disposable data.
|
|
|
|
## Rehearsal Rules
|
|
|
|
For DB rehearsals:
|
|
|
|
1. Capture production preflight counts.
|
|
2. Create a disposable DB from live state.
|
|
3. Run commit SQL only in the disposable DB.
|
|
4. Run postflight counts.
|
|
5. Run delete rollback if applicable.
|
|
6. Drop the disposable DB.
|
|
7. Verify production counts stayed unchanged.
|
|
8. Verify the disposable DB no longer exists.
|
|
|
|
## Blocker Format
|
|
|
|
Do not say "blocked" without:
|
|
|
|
- `current_canary`
|
|
- `attempted_routes`
|
|
- `exact_gate`
|
|
- `clear_CTA`
|
|
- `next_non_user_action`
|