# Web Sentinel

Web sentinel operations stay YAML-first. Node, lane, sentinel id, cadence, Deployment, Service, PVC, route prefix, dashboard URL and Secret sourceRefs come from config.

Use controlled `web-probe sentinel ...` commands for status, report, control-plane, validate and dashboard operations. Direct `kubectl create job --from=cronjob` is diagnostic only, not acceptance evidence.

JD01 `jd01-web-probe-sentinel` CI follows the migrated Gitea/Pipelines-as-Code path. Source truth is `config/platform-infra/gitea.yaml#sourceAuthority.repositories.unidesk-master` plus `config/platform-infra/pipelines-as-code.yaml#consumers.sentinel-jd01-v03`; status evidence is `bun scripts/cli.ts platform-infra pipelines-as-code status --target JD01 --consumer sentinel-jd01-v03`. Do not re-enable `web-probe-sentinel-master` branch-follower, Gitea Actions or act_runner fallback.
