pdurlej/platform

Fork 0

feat(status): add public dashboard publisher #820

Merged

pdurlej merged 1 commit from codex/status-dashboard-autopublish into main

2026-06-19 09:52:41 +02:00

codex commented

2026-06-19 09:52:01 +02:00

Collaborator

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

Canary Context Pack

Product story

The platform status dashboard should receive fresh public-safe status.json snapshots without giving the dashboard runtime access to Tailnet, RS2000, VPS1000, Docker, SSH, Infisical, or logs.

What changed

Added platformctl status publish-dashboard.
Added platform-side validation for the existing platform-status.v1 contract.
Added leakage scan for secret-like literals, private/tailnet IPs, host paths, and internal port endpoints.
Added a GitHub Contents API publisher that can update only public/status.json in pdurlej/platform-status-dashboard when --publish-github is explicitly passed.
Added systemd service/timer examples and updated the v0 handoff doc.

Why it changed

The dashboard repo is ready to render richer status data, but it needs an autonomous outbound delivery path from the trusted platform side. This PR keeps Vercel/GitHub passive and makes publication fail closed before any external write.

Files touched

control-plane/platformctl/status_publish.py
control-plane/platformctl/cli.py
control-plane/platformctl/tests/test_public_status.py
scripts/status-dashboard/README.md
scripts/status-dashboard/systemd/platform-status-dashboard-publish.service.example
scripts/status-dashboard/systemd/platform-status-dashboard-publish.timer.example
docs/platform-status-dashboard-v0-prompt.md

Relevant context

Existing exporter: platformctl status export --public
Existing dashboard contract: schema_version: platform-status.v1
Dashboard repo reads only committed public/status.json.

Runtime evidence

No live runtime mutation performed. Local dry validation against the real 88-module snapshot returned validation_errors=[], safety_findings=[], export_errors=0, exitCode=0.

Known constraints

No GitHub token value is stored, printed, or committed.
The publisher requires PLATFORM_STATUS_DASHBOARD_GITHUB_TOKEN at runtime and should use a dashboard-repo-scoped token with contents write only.
The command refuses to publish any path except public/status.json.
This PR does not install or enable the systemd timer.

Explicit out-of-scope

Real service health probes.
Installing the runtime timer on RS2000.
Creating or rotating the GitHub token.
Changing dashboard UI behavior.
Any inbound runtime connector from Vercel/GitHub.

Requested decision

Approve the platform-side autonomous outbound publisher after canary/full review.

Merge blockers

Any leak of secret values, private IPs, host paths, or internal endpoints into public/status.json.
Any path that lets the dashboard call back into runtime.
Any broad GitHub write surface beyond public/status.json.

Spec sources read

control-plane/platformctl/public_status.py — existing exporter contract.
control-plane/platformctl/cli.py — CLI integration point.
control-plane/platformctl/tests/test_public_status.py — existing test surface.
docs/platform-status-dashboard-v0-prompt.md — dashboard handoff/contract.
scripts/status-dashboard/README.md — new operator runbook for this slice.
scripts/status-dashboard/systemd/*.example — new timer/service examples.

Tests

UV_CACHE_DIR=/Users/pd/Developer/platform/.uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m pytest control-plane/platformctl/tests/test_public_status.py
# 8 passed

UV_CACHE_DIR=/Users/pd/Developer/platform/.uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli status publish-dashboard --json
# services=88, validation_errors=[], safety_findings=[], export_errors=0, exitCode=0

git diff --check
# passed

No closing issue: requested directly by operator in live thread.

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story The platform status dashboard should receive fresh public-safe `status.json` snapshots without giving the dashboard runtime access to Tailnet, RS2000, VPS1000, Docker, SSH, Infisical, or logs. ### What changed - Added `platformctl status publish-dashboard`. - Added platform-side validation for the existing `platform-status.v1` contract. - Added leakage scan for secret-like literals, private/tailnet IPs, host paths, and internal port endpoints. - Added a GitHub Contents API publisher that can update only `public/status.json` in `pdurlej/platform-status-dashboard` when `--publish-github` is explicitly passed. - Added systemd service/timer examples and updated the v0 handoff doc. ### Why it changed The dashboard repo is ready to render richer status data, but it needs an autonomous outbound delivery path from the trusted platform side. This PR keeps Vercel/GitHub passive and makes publication fail closed before any external write. ### Files touched - `control-plane/platformctl/status_publish.py` - `control-plane/platformctl/cli.py` - `control-plane/platformctl/tests/test_public_status.py` - `scripts/status-dashboard/README.md` - `scripts/status-dashboard/systemd/platform-status-dashboard-publish.service.example` - `scripts/status-dashboard/systemd/platform-status-dashboard-publish.timer.example` - `docs/platform-status-dashboard-v0-prompt.md` ### Relevant context - Existing exporter: `platformctl status export --public` - Existing dashboard contract: `schema_version: platform-status.v1` - Dashboard repo reads only committed `public/status.json`. ### Runtime evidence No live runtime mutation performed. Local dry validation against the real 88-module snapshot returned `validation_errors=[]`, `safety_findings=[]`, `export_errors=0`, `exitCode=0`. ### Known constraints - No GitHub token value is stored, printed, or committed. - The publisher requires `PLATFORM_STATUS_DASHBOARD_GITHUB_TOKEN` at runtime and should use a dashboard-repo-scoped token with contents write only. - The command refuses to publish any path except `public/status.json`. - This PR does not install or enable the systemd timer. ### Explicit out-of-scope - Real service health probes. - Installing the runtime timer on RS2000. - Creating or rotating the GitHub token. - Changing dashboard UI behavior. - Any inbound runtime connector from Vercel/GitHub. ### Requested decision Approve the platform-side autonomous outbound publisher after canary/full review. ### Merge blockers - Any leak of secret values, private IPs, host paths, or internal endpoints into `public/status.json`. - Any path that lets the dashboard call back into runtime. - Any broad GitHub write surface beyond `public/status.json`. ## Spec sources read - `control-plane/platformctl/public_status.py` — existing exporter contract. - `control-plane/platformctl/cli.py` — CLI integration point. - `control-plane/platformctl/tests/test_public_status.py` — existing test surface. - `docs/platform-status-dashboard-v0-prompt.md` — dashboard handoff/contract. - `scripts/status-dashboard/README.md` — new operator runbook for this slice. - `scripts/status-dashboard/systemd/*.example` — new timer/service examples. ## Tests ```bash UV_CACHE_DIR=/Users/pd/Developer/platform/.uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m pytest control-plane/platformctl/tests/test_public_status.py # 8 passed UV_CACHE_DIR=/Users/pd/Developer/platform/.uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli status publish-dashboard --json # services=88, validation_errors=[], safety_findings=[], export_errors=0, exitCode=0 git diff --check # passed ``` No closing issue: requested directly by operator in live thread.

codex added the

risk/process

phase/03

class/security-sensitive

tier/full

agent/codex

safety:secret-touch

safety:external-write

type:feat

labels

2026-06-19 09:52:01 +02:00

codex added 1 commit

2026-06-19 09:52:01 +02:00

feat(status): add public dashboard publisher

canary-required / collect-diff (pull_request) Successful in 4s

Details

python-ci / Python 3.11 (pull_request) Successful in 39s

Details

python-ci / Python 3.12 (pull_request) Successful in 40s

Details

python-ci / Python 3.13 (pull_request) Successful in 41s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 3s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Successful in 16s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 17s

Details

pyfallow / Pyfallow gate (control-plane) (pull_request) Successful in 15s

Details

base-is-main / guard (pull_request) Successful in 1s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 53s

Details

patchwarden-client-dry-run / dry-run (pull_request) Successful in 15s

Details

e10d0f93b2

pdurlej merged commit b992e87dbf into main

2026-06-19 09:52:41 +02:00

pdurlej deleted branch codex/status-dashboard-autopublish

2026-06-19 09:52:41 +02:00

pdurlej referenced this pull request from a commit

2026-06-19 09:52:42 +02:00

Merge pull request 'feat(status): add public dashboard publisher' (#820) from codex/status-dashboard-autopublish into main

patchwarden commented

2026-06-19 09:58:29 +02:00

First-time contributor

Patchwarden PR sanity

Status: eligible_sanity_clean
PR: 820
Commit: e10d0f93b2eab5d98685b7cf60b06922c48321f2
Security-sensitive label: present
Authority: advisory model review plus deterministic blockers only
3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

`global-glm` / `glm-5.1:cloud`

Status: ok
Verdict: OK
Findings: none

`global-deepseek` / `deepseek-v4-pro:cloud`

Status: ok
Verdict: ABSTAIN
blocker Missing diff prevents review
- Evidence: The diff is empty; no changed files/hunks provided.
- Next: Provide the actual diff for review to verify safety claims (no secret leaks, no broad write surface, etc.).

`redteam` / `kimi-k2.6:cloud`

Status: ok
Verdict: OK
Findings: none

Policy notes

GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
Auto-merge is not enabled here.

# Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `820` - Commit: `e10d0f93b2eab5d98685b7cf60b06922c48321f2` - Security-sensitive label: `present` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `ABSTAIN` - **`blocker`** Missing diff prevents review - Evidence: `The diff is empty; no changed files/hunks provided.` - Next: Provide the actual diff for review to verify safety claims (no secret leaks, no broad write surface, etc.). ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.