Clément SAILLANT
5efb380da5
* feat: automate yiacad pr review lane * fix: stabilize yiacad review and spec gates * fix: scope kicad exports to repo hardware * fix: ignore kicad block library sources in exports * feat: Add infra VPS monitoring runbook and healthcheck scripts - Created INFRA_VPS_RUNBOOK_2026.md detailing operational procedures for monitoring VPS services. - Added infra_vps_healthcheck.sh script for automated health checks on DNS, TLS, TCP, and HTTP for VPS services. - Introduced infra_vps_security_audit.sh for non-intrusive security checks on external VPS services. - Established JSON schema for infra VPS inventory in infra_vps.schema.json. - Developed integration for runtime status reporting in the Next.js API route. - Implemented Playwright tests for smoke testing the application and ensuring core functionalities. - Updated Makefile for development dependencies and testing commands. - Created various test files for unit and end-to-end testing across different components. * feat(agentics): update mesh agents, gates, prompts, and workflows
1.6 KiB
1.6 KiB
description, name
| description | name |
|---|---|
| Use when running autonomous execution workflows, operator runbooks, cockpit commands, runtime diagnosis, or evidence generation in Kill_LIFE. Focuses on action order, safety checks, and prioritized command paths. | Autonomous Execution |
Autonomous Execution - Runbook First
Intent
Use this instruction for execution-heavy requests (operate, verify, recover, produce evidence), not for pure code review.
Preferred Execution Order
- Read current runtime state first.
- Execute the smallest high-signal command chain.
- Verify expected artifacts and status output.
- Only then widen scope to secondary lanes.
Priority Commands
- Runtime health and routing:
bash tools/cockpit/runtime_ai_gateway.sh --action status --refresh --json
- YiACAD operator entry:
bash tools/cockpit/yiacad_operator_index.sh --action status --json
- Backend/UIUX lane:
bash tools/cockpit/yiacad_uiux_tui.sh --action status --jsonbash tools/cockpit/yiacad_backend_proof.sh --action status --json
- CI/spec integrity:
python3 tools/validate_specs.py --strictbash tools/test_python.sh --suite stable
Safety Rules
- Never use destructive git commands unless explicitly requested.
- Preserve unrelated user changes.
- Prefer idempotent commands and explicit
--jsonoutputs. - Record evidence/log outputs in
artifacts/and link them in summaries.
Completion Criteria
- Report: current status, blockers, and exact failing lane.
- Provide: next executable command(s) in priority order.
- Confirm: produced artifact/log paths.