fix(modules): align dashboard smoke with tailnet exposure #256

Merged
pdurlej merged 1 commit from codex/cutover/dashboard-health-smoke-contract into main 2026-05-13 08:10:38 +02:00
Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

Dashboard auto-apply smoke now reaches plan/apply and validates the manifest/container. The remaining failure is a stale HTTP health contract: https://pdurlej.com/health is not a valid Homepage health endpoint for the deploy runner path. This PR aligns the manifest with the actual runtime exposure and health signal.

What changed

  • Changes dashboard user-facing outcome from public homepage to Tailnet-allowlisted homepage.
  • Changes exposure metadata from public/none to tailnet-only/tailscale with ts-allowlist@file and security-headers@file.
  • Removes the invalid /health HTTP smoke URL and records compose health as the intended health source.
  • Updates acceptance criteria to match the container healthcheck and running container evidence.

Why it changed

Run #612 / API run #748 showed:

  • auto-apply scope eligible
  • plan/apply no-op succeeded
  • strict-v2 manifest OK
  • container home-platform-dashboard-1 running
  • smoke failed only on health-http:FAIL-403-vs-expected-200

Homepage already has a container healthcheck for http://127.0.0.1:3000/; /health is not the right manifest contract here.

Files touched

  • modules/dashboard/module.yaml

Relevant context

  • Issue #142 cutover lane
  • PR #255 dashboard strict-v2 manifest fix
  • compose/apps/compose.yaml dashboard labels: com.home.exposure: tailnet, ts-allowlist@file
  • Run #612 / API run #748 evidence artifact

Runtime evidence

  • RS2000 docker exec home-platform-dashboard-1 wget -qSO- http://127.0.0.1:3000/ returned HTTP 200.
  • RS2000 external curl to https://pdurlej.com/health returned 403 in smoke context.
  • Local Mac curl to https://pdurlej.com/health returned 404, confirming /health is not a stable Homepage health endpoint.

Known constraints

  • This PR changes manifest truth only; it does not change Traefik, compose, or runtime routing.
  • risk.internet_exposed remains true because the route is internet-facing with access control. exposure.classification now captures the Tailnet allowlist behavior.

Explicit out-of-scope

  • No production mutation.
  • No workflow change.
  • No runner change.
  • No stateful service apply.

Requested decision

Merge this manifest contract correction, then Codex will sync /opt/pdurlej-platform/current and rerun dashboard workflow_dispatch.

Merge blockers

  • Evidence shows dashboard should actually be public unauthenticated.
  • Removing health.http would hide a real required external health check.

Spec sources read

  • modules/dashboard/module.yaml — changed manifest.
  • compose/apps/compose.yaml — dashboard exposure labels and container healthcheck.
  • tests/smoke.sh — HTTP health behavior for manifest health.http.
  • Forgejo Actions run #612 / API run #748 artifact evidence — failure cause.
  • RS2000 read-only docker inspect / docker exec wget evidence — container health source.

Verification

/tmp/platformctl-test-venv/bin/python -m platformctl validate --strict-v2 modules/dashboard/module.yaml
/tmp/platformctl-test-venv/bin/pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_health_phase3.py -q

Result: strict-v2 validation OK; 25 passed.

Refs #142

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story Dashboard auto-apply smoke now reaches plan/apply and validates the manifest/container. The remaining failure is a stale HTTP health contract: `https://pdurlej.com/health` is not a valid Homepage health endpoint for the deploy runner path. This PR aligns the manifest with the actual runtime exposure and health signal. ### What changed - Changes `dashboard` user-facing outcome from public homepage to Tailnet-allowlisted homepage. - Changes exposure metadata from `public`/`none` to `tailnet-only`/`tailscale` with `ts-allowlist@file` and `security-headers@file`. - Removes the invalid `/health` HTTP smoke URL and records compose health as the intended health source. - Updates acceptance criteria to match the container healthcheck and running container evidence. ### Why it changed Run #612 / API run #748 showed: - auto-apply scope eligible - plan/apply no-op succeeded - strict-v2 manifest OK - container `home-platform-dashboard-1` running - smoke failed only on `health-http:FAIL-403-vs-expected-200` Homepage already has a container healthcheck for `http://127.0.0.1:3000/`; `/health` is not the right manifest contract here. ### Files touched - `modules/dashboard/module.yaml` ### Relevant context - Issue #142 cutover lane - PR #255 dashboard strict-v2 manifest fix - `compose/apps/compose.yaml` dashboard labels: `com.home.exposure: tailnet`, `ts-allowlist@file` - Run #612 / API run #748 evidence artifact ### Runtime evidence - RS2000 `docker exec home-platform-dashboard-1 wget -qSO- http://127.0.0.1:3000/` returned HTTP 200. - RS2000 external curl to `https://pdurlej.com/health` returned 403 in smoke context. - Local Mac curl to `https://pdurlej.com/health` returned 404, confirming `/health` is not a stable Homepage health endpoint. ### Known constraints - This PR changes manifest truth only; it does not change Traefik, compose, or runtime routing. - `risk.internet_exposed` remains `true` because the route is internet-facing with access control. `exposure.classification` now captures the Tailnet allowlist behavior. ### Explicit out-of-scope - No production mutation. - No workflow change. - No runner change. - No stateful service apply. ### Requested decision Merge this manifest contract correction, then Codex will sync `/opt/pdurlej-platform/current` and rerun dashboard workflow_dispatch. ### Merge blockers - Evidence shows dashboard should actually be public unauthenticated. - Removing `health.http` would hide a real required external health check. ## Spec sources read - `modules/dashboard/module.yaml` — changed manifest. - `compose/apps/compose.yaml` — dashboard exposure labels and container healthcheck. - `tests/smoke.sh` — HTTP health behavior for manifest `health.http`. - Forgejo Actions run #612 / API run #748 artifact evidence — failure cause. - RS2000 read-only `docker inspect` / `docker exec wget` evidence — container health source. ## Verification ```bash /tmp/platformctl-test-venv/bin/python -m platformctl validate --strict-v2 modules/dashboard/module.yaml /tmp/platformctl-test-venv/bin/pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_health_phase3.py -q ``` Result: strict-v2 validation OK; 25 passed. Refs #142
fix(modules): align dashboard smoke with tailnet exposure
All checks were successful
canary-required / collect-diff (pull_request) Successful in 4s
platformctl plan / auto-apply scope (pull_request) Successful in 19s
canary-required / canary (pull_request) Successful in 13s
base-is-main / guard (pull_request) Successful in 1s
5478a1a35c
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!256
No description provided.