Files
proxmox/.cursor/rules/operator-lan-access-check.mdc
defiQUG 3f76bc9507
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: update master documentation and push to Gitea (2026-03-06)
- MASTER_INDEX: Last Updated 2026-03-06; status 59/59 contracts; add NEXT_STEPS_LIST, CONTRACT_NEXT_STEPS_LIST
- docs/README, NEXT_STEPS_INDEX, 06-besu/MASTER_INDEX: Last Updated 2026-03-06
- Contract check script: 59 addresses (PMM, vault/reserve, CompliantFiatTokens); canonical CCIP/router
- New docs: EXECUTION_CHECKLIST, NEXT_STEPS_LIST, DOTENV_AUDIT, ADDITIONAL_PATHS, deployer gas runbook, WEMIX_ACQUISITION_TABLED, etc.
- Config: deployer-gas-routes, cro-wemix-swap-routes, routing-registry, token-mapping
- Scripts: check-contracts-on-chain-138, check-pmm-pool-balances-chain138, deployer-gas-auto-route, acquire-cro-and-wemix-gas
- Operator rule: operator-lan-access-check.mdc

Made-with: Cursor
2026-03-06 19:11:25 -08:00

46 lines
2.5 KiB
Plaintext

---
description: Check for Operator/LAN access before running operator scripts; then run or recommend accordingly
alwaysApply: false
globs:
- "scripts/run-all-operator-tasks-from-lan.sh"
- "scripts/run-operator-tasks-from-lan.sh"
- "docs/00-meta/OPERATOR*.md"
- "docs/00-meta/STEPS_FROM_PROXMOX*.md"
---
# Operator/LAN access check
When the user asks to run **operator tasks**, **LAN tasks**, or scripts that require 192.168.11.x (NPMplus, Chain 138 RPC, Blockscout, Proxmox), **check for Operator/LAN access first**, then run or recommend accordingly.
## 1. Check (before running operator scripts)
Run from **repo root**:
```bash
# RPC reachable?
curl -s -o /dev/null -w "%{http_code}" --connect-timeout 3 http://192.168.11.211:8545
# Env files present (operator scripts load these automatically)
test -f .env && test -f smom-dbis-138/.env && echo "env OK" || echo "env missing"
```
- **RPC 200/201 or 400** and **env OK** → treat as **Operator/LAN available**; operator scripts can be run.
- **Timeout / unreachable** or **env missing** → treat as **no Operator/LAN**; do not run `run-all-operator-tasks-from-lan.sh`; suggest `./scripts/run-completable-tasks-from-anywhere.sh` and note that operator tasks require a host on 192.168.11.x with `.env` and optional `NPM_PASSWORD` (see OPERATOR_CREDENTIALS_CHECKLIST).
## 2. When access is available
- Run operator scripts from repo root. They **load dotenv automatically** via `scripts/lib/load-project-env.sh` (no need to `source .env`).
- **Primary:** `./scripts/run-all-operator-tasks-from-lan.sh` (use `--skip-backup` if `NPM_PASSWORD` not set; add `--deploy` or `--create-vms` if needed).
- **Completable first (optional):** `./scripts/run-completable-tasks-from-anywhere.sh` then operator script.
## 3. When access is not available
- Suggest: `./scripts/run-completable-tasks-from-anywhere.sh` (config validation, on-chain check, reconcile output).
- Tell the user that NPMplus backup, Blockscout verify, RPC proxy updates, and deploy require a host on **LAN (192.168.11.x)** with root `.env` and `smom-dbis-138/.env`; see **docs/00-meta/OPERATOR_CREDENTIALS_CHECKLIST.md** and **OPERATOR_READY_CHECKLIST.md**.
## 4. References
- **Operator context (always):** `.cursor/rules/operator-context-lan-proxmox.mdc` — this machine is assumed LAN/operator when that rule applies.
- **Credentials:** `docs/00-meta/OPERATOR_CREDENTIALS_CHECKLIST.md` — per-task LAN, PRIVATE_KEY, NPM_PASSWORD, RPC_URL_138.
- **Commands:** `docs/00-meta/OPERATOR_READY_CHECKLIST.md` — copy-paste operator commands.