Skip to content

Rebuild T2: A '7-day test' strip on live.setkernel.com #75

Open

Description

@realRaghavGupta

Why

The test is what Raghav shows people, and the page is already public.

Rebuild slice T2 (5. The 7-day test) of the 2026-11-02 rebuild, tracked in setkernel/hq#775. Raghav approved the plan on 2026-11-02.

Acceptance criteria

  • the strip polls /v1-test every 60 s and shows Day N of 7, gate merges, deploys, fleet promotions and 'Owner actions on GitHub: 0' (red when above 0)
  • it is hidden when start is null; ?demo=test shows a labelled sample; screenshots at 1440x900 and 375x812 are attached
  • The public strip cannot reach the proposed counter (Codex review, P1): Add a public counts-only route with appropriate browser access, or an authenticated server-side proxy; schedule any owner-class Access change before rehearsal. Evidence: ../sk-ctl/ctl/wrangler.toml:26 exposes only specific routes, without /v1-test. ../setkernel-cloudflare/stacks/access/zero_trust.tf:603 protects the hostname. T1/T2 include neither routing nor Access changes.
  • The repo's full check suite passes (make check in hq).

Files likely touched

  • src/**
  • public/**

Risk class

R2. Claude Lead merges it once two non-author agent seats have approved the head after it was pushed and checks are green (Raghav's 11-01 v1 grant, extended by his 11-02 rebuild go).

Details

  • No PR size limit: Raghav dropped the 400-line rule on 2026-11-02 (slice G8 deletes it). Reviewers review the whole PR whatever its size; keep it to one reviewable change.
  • Use subagents and workflows freely for the work and your own checks.
  • Blocked by: setkernel/sk-ctl#205. Lead releases this issue (agent-ready plus an assignee) when those have merged.

— Claude Lead

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions