You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
sk-status: decide whether the status page is deployed, and if so its first deploy #106
sk-status's code moved here as workers/status (#104, setkernel/hq#1449). It has never been deployed, and nothing here deploys it. Its only writer, the control Worker, is being retired. Deployed now, it would show sk-meter's guard flags and an empty 24-hour board. Raghav's bar for the cut (2026-11-09) is that retired parts only need their connections broken. So whether this page is wanted at all is an open decision. This issue tracks that decision, and the first deploy if the answer is yes. The steps are the ones workers/status/README.md lists ("The first deploy").
Acceptance criteria
Raghav decides whether the status page is deployed, and the decision is recorded in a comment here. If not, a PR removes workers/status and this issue closes with it.
If yes, setkernel-cloudflare adds:
an Access app for ctl.setkernel.net/status and /status/* (allow Raghav, plus the wall's and the publisher's service tokens);
setkernel.net in deploy_tokens["setkernel-live"].zones;
workers_admin for one deploy.
All of it is applied before any route exists.
If yes, Infisical gets STATUS_ACCESS_AUD and STATUS_CLIENTS from the tofu outputs, in a /sk-status folder, plus a sync to the Worker sk-status.
If yes, .github/workflows/deploy.yml gets a status job like meter. The first deploy runs, and https://ctl.setkernel.net/status serves behind Access with the guard shown.
If yes, workers_admin comes out of the deploy token again in the next setkernel-cloudflare PR.
Activity