mirrors/pikasTech-unidesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add monitor evidence inspect cli

Browse Source
This commit is contained in:
Codex
2026-07-07 00:38:50 +00:00
parent acc21b191b
commit e9c91c78e6
8 changed files with 356 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/unidesk-monitor/SKILL.md
+4
View File
@@ -30,6 +30,8 @@ bun scripts/cli.ts web-probe sentinel control-plane status --node <node> --lane
bun scripts/cli.ts web-probe sentinel validate --node <node> --lane <lane> --sentinel <id>
bun scripts/cli.ts web-probe sentinel dashboard verify --node <node> --lane <lane> --sentinel <id>
bun scripts/cli.ts web-probe sentinel dashboard screenshot --node <node> --lane <lane> --sentinel <id>
bun scripts/cli.ts web-probe sentinel inspect-url 'https://monitor.pikapython.com/?run=<runId>'
bun scripts/cli.ts web-probe sentinel inspect-id <id> --node <node> --lane <lane> --sentinel <id>
bun scripts/cli.ts web-probe sentinel report --node <node> --lane <lane> --sentinel <id> --latest --view summary
bun scripts/cli.ts web-probe sentinel report --node <node> --lane <lane> --sentinel <id> --latest --view summary --raw
bun scripts/cli.ts web-probe sentinel report --node <node> --lane <lane> --sentinel <id> --latest --view summary --full
@@ -41,6 +43,8 @@ trans <node>:k3s kubectl -n <namespace> create job --from=cronjob/<quick-verify-
For WebUI manual validation, use `web-probe sentinel dashboard trigger` so the remote browser clicks the monitor-web button. Direct `kubectl create job --from=cronjob/...` is a last-resort diagnostic only, not acceptance evidence. For k3s cadence validation, first use the controlled control-plane status/trigger commands, then inspect the rendered CronJob in the target k3s namespace. Persistent cadence changes must be made through YAML/GitOps and redeployed.
When a user gives a monitor-web URL or an evidence id from the page, first use `web-probe sentinel inspect-url` or `web-probe sentinel inspect-id`. These commands map `run`, `observer`, `traceId`, `sampleSeq`, `turn`, `commandId`, `artifact` and finding ids to controlled report/observe drill-down commands. Do not use public monitor-web HTTP API probes as HWLAB business evidence; reserve them for explicit monitor-web shell/API/render diagnostics and label them separately.
For long Workbench/user-path evidence, use the normal Web probe surface:
```bash