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

docs: record sentinel frpc active-root conflict

Browse Source
This commit is contained in:
Codex
2026-06-28 09:30:21 +00:00
parent 57d28533da
commit a37e52fe47
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/unidesk-monitor/references/full.md
+2
View File
@@ -109,6 +109,8 @@ Classify a monitor page issue in this order:
Do not treat public root/CSS/JS 200 as dashboard success. Browser console and DOM render evidence are required.
When a Pod and its ClusterIP Service return the expected monitor-web asset but `https://monitor.pikapython.com/monitor-web/assets/...` still returns an old file, check the public FRP hop before changing UI code again. On D518 this has happened when a stale legacy `hwlab-web-probe-sentinel-frpc` Argo app still owned PK01 remote port `22093`, while the active `hwlab-web-probe-sentinel-fake-echo-frpc` logged `start error: port already used`; Caddy then served the old runner even though the new Pod and runtime image were healthy. Retire the stale Argo/frpc owner through a controlled YAML/CLI path and then rerun `dashboard verify`.
## Rollout Closeout
For a Web sentinel fix, closeout needs four independent evidence surfaces: