CI-00 [TRACKER][decision]: Smart CI Fabric and private-repository readiness (ADR-0066) — go private for v0.3.0 on a personal GitHub Pro account

[Chris0Jeky]

Wave tracker for the Smart CI Fabric programme — the CI redesign that lets Taskdeck go private for the v0.3.0 release on a personal GitHub Pro account (no Team/Enterprise dependency) without weakening verification or burning hosted minutes. Decision record: docs/decisions/ADR-0066-smart-ci-fabric-and-private-repository-runner-trust.md. Evidence base and pack-versus-repository reconciliation: docs/analysis/2026-08-30-smart-ci/RECONCILIATION.md (the maintainer's 2026-08-30 Smart CI pack is archived beside it, as received).

Authority for this wave (recorded verbatim, 2026-08-30)

Do inspect it properly, understand it, and then act on it, starting from unbundling everything to set things up, update docs, seed issues, etc and then start scaffolding and structuring everything to make this happen. The repo will need to go private for v0.3.0 main release, and initially it should work with only my github pro account, without having to rely on teams/enterprise

Under that direction the agent pass ruled on the pack's open decisions (below) instead of parking them in a deck. Every ruling is the agent's, made under explicit delegation, and is revisable by the maintainer at any time — reply on this issue to overturn one. The four actions only the maintainer can perform (visibility change, spend ceiling, branch-protection/ruleset edits, runner registration) are not delegated; they sit in OUTSTANDING_TASKS.md §J and on CI-13.

Delegated rulings (ADR-0066 §Acceptance conditions)

#	Condition	Ruling	Why
1	Ownership model	Personal GitHub Pro account first. The organization runner-group / ruleset-required-workflow boundary is deferred to CI-14 as a later decision, not a prerequisite	Maintainer directive; a personal private repo has no external contributors, so the weaker check-name boundary is acceptable while the review pipeline reviews every workflow change
2	Control-plane placement in personal mode	Base-ref control plane. The planner and gate run from the PR's base commit on pull_request_target with read-only permissions and never check out or execute head code; head code runs only on pull_request jobs. A PR may request more verification, never less than the base policy ceiling	The closest personal-account equivalent of "the PR cannot edit its own gate"; the residual (same-repo check-name spoofing) is recorded, not hidden
3	Required gate	One stable context Smart CI / Required Gate, registered in branch protection only after shadow evidence (CI-03); strict (branch current) on at the same time; the three security contexts stay required through the migration	ADR-0035 already wanted an aggregate gate; strict mode replaces merge queue (unavailable on personal private repos)
4	Execution mode	hosted by default until CI-04 proves the isolated runners; hybrid after; no claimed transparent fallback — an explicit ci:hosted label / CI_EXECUTION_MODE variable forces hosted	GitHub queues offline self-hosted jobs; pretending otherwise creates false greens
5	Platform strategy	Linux is the semantic baseline; Windows becomes a bounded compatibility contract on ordinary PRs (CI-07); the full Windows suite stays weekly + release until parity evidence exists	Windows minutes count double on Pro; the API suite is 2.6x slower there and the delta is process-harness overhead, not semantics
6	Main-push behaviour	Full main re-qualification replaced by a landed verifier bound to the PR's qualified tree SHA (CI-03); direct/bypass pushes escalate to full hosted qualification	Merge commits get new SHAs; the tree is what was tested when the branch was current
7	Selection	Deterministic, fail-closed planner in shadow mode first (CI-02); selection enabled one lane family at a time only after a recall report over >=20 PRs (CI-05)	Never replace a known-expensive gate with an uncalibrated cheap one
8	Nightly / mutation	Change-driven nightly with a weekly full sweep (CI-10); mutation stays manual per ADR-0052	No new evidence = honest green receipt, not a rerun
9	Order of savings	Storage first (CI-09: 31,942 artifacts, cache at the 10 GB cap — Pro private storage allowance is 1 GB), then duplicate-event removal (CI-03), then platform right-sizing (CI-07/08), then self-hosted (CI-04)	Storage is billed daily the moment the repo is private; the rest is minutes

Issue map

ID	Issue	Milestone	Depends on	Owner
CI-01	#2325 Baseline ledger (measure cost, critical path, duplication, storage)	v0.3	—	agent
CI-02	#2326 Deterministic planner + policy in shadow mode	v0.3	CI-01	agent
CI-03	#2327 Smart CI / Required Gate, branch-current contract, landed verifier	v0.3	CI-02	agent + maintainer setting
CI-04	#2328 Isolated on-demand self-hosted runners (personal mode)	v0.3 (registration after cutover)	CI-02	agent prep + maintainer registration
CI-05	#2329 Test ownership / impact graph	v0.3	CI-02	agent
CI-06	#2330 API shards + Windows MCP/process harness repair	v0.4	CI-01, CI-05	agent
CI-07	#2331 Windows compatibility contract	v0.3	CI-05	agent
CI-08	#2332 One frontend lane, journey-aware E2E, risk-gated containers	v0.3	CI-05	agent
CI-09	#2333 Cache, artifact and storage budget	v0.3	CI-01	agent
CI-10	#2334 Change-driven nightly + clean release qualification	v0.4	CI-01, CI-03, CI-05	agent
CI-11	#2335 Full-SHA action pinning + hosted-only CI-control qualification	v0.3	CI-02	agent (+ sha_pinning_required setting)
CI-12	#2336 CI receipts, weekly report, budget regression	v0.4	CI-01, CI-02	agent
CI-13	#2337 [HUMAN GATE] private-repository cutover	v0.3	CI-02, CI-03, CI-09, CI-11	maintainer
CI-14	#2338 Organization control plane (deferred decision)	—	CI-13	maintainer decision
CI-15	#2339 Flake quarantine and retry governance	v0.4	CI-12	agent

Existing issues folded in or related (comments posted on each): #1872 (E2E apt hot path -> CI-08), #2157/#2159/#2161 (Windows dev-up flakes -> CI-07/CI-15), #1210 (ci-extended startup_failure -> CI-10), #1819 (CodeQL -> CI-11), #2149 (protected signing boundary -> CI-04/CI-10 release context), #2312 (Docker profile regressions in hosted CI -> CI-08), #1639 (evidence-collector lane -> CI-05).

Execution order

CI-01 baseline --> CI-02 shadow planner --> CI-05 ownership map --> enable selection per lane
      |                    |                       |
      +--> CI-09 storage   +--> CI-03 gate + topology (-> maintainer registers the gate, strict on)
      |                    +--> CI-11 pinning (-> maintainer flips sha_pinning_required)
      +--> CI-07 Windows contract / CI-08 frontend+E2E+containers
                                     |
                       CI-13 cutover rehearsal --> maintainer flips visibility --> CI-04 runners registered
                                     |
                       CI-06 / CI-10 / CI-12 / CI-15 (v0.4 depth)         CI-14 (later decision)

Done when

• ADR-0066 merged with the rulings above; ADR-0013/0035/0052 relationships recorded (retained / amended / superseded portions named).
• Every child has an owner-verifiable acceptance list and a milestone.
• Shadow planner + observation-mode gate run on every PR without changing existing job selection (CI-02 scaffold).
• The maintainer has performed the CI-13 cutover and recorded post-cutover evidence; the repository is private for the v0.3.0 release.
• Measured before/after: hosted minutes, critical path, storage — recorded in docs/ci/CI_BASELINE.md and its successor ledger.

[Chris0Jeky]

Progress 2026-08-30 (agent pass under the directive recorded above):

• PR ADR-0066 Smart CI Fabric: decision, reconciliation, measured baseline and human-action map (CI-00 #2324) #2341 — ADR-0066 (Accepted under delegation), the pack archived as received + RECONCILIATION.md (16 pack-vs-live corrections), docs/ci/ (architecture, runner threat model, cutover checklist, baseline), the measurement tool, and the docs/tracker/human-action reconciliation (OUTSTANDING_TASKS.md §J SC-1..SC-8). Ready for review.
• PR Smart CI control plane in shadow mode: policy, fail-closed planner, observation gate, pin inventory, runner broker (CI-02 #2326) #2342 — the control plane in shadow mode: ci/policy.v1.json, the fail-closed planner + gate evaluator with 35 fixtures, smart-ci-shadow.yml (base-ref pull_request_target planner/gate, read-only, no head execution; head-side self-tests on pull_request), the action-pin inventory, the runner broker skeleton. Changes no ci-required.yml job selection. Ready for review.
• Measured baseline (31 days to 2026-08-30): 2,707 runs; CI 1,198 (858 PR + 340 push: main re-runs; 384 cancelled); a green required run = 17 jobs, p50 critical path 24.7 min, ~126 allowance minutes under private accounting (Windows 88 of them); projection ~99,000 allowance min/month vs 3,000; 370.7 GB unexpired artifacts (357 GB exported container-image tars) vs 1 GB; cache at the 10 GB cap. Details: docs/ci/CI_BASELINE.md on ADR-0066 Smart CI Fabric: decision, reconciliation, measured baseline and human-action map (CI-00 #2324) #2341.
• Children CI-01..CI-15 = CI-01: Measure Taskdeck CI cost, critical path, duplication, storage and lane yield (baseline ledger) #2325–CI-15: Fail-visible flake classification, quarantine with expiry, and retry governance #2339; ten related issues re-pointed.

Nothing in either PR changes branch protection, visibility, billing, runners or secrets — those stay in §J for the maintainer.

[Chris0Jeky]

PR #2343 (CI-09 slice 1, ruling 9 "storage first"): explicit artifact retention classes — the required lane no longer uploads the ~170 MB image tars (no consumer), nightly 3 days, release 90 explicitly, frontend test artifacts 3 days, k6 14 — plus scripts/ci/smart-ci/artifact-cleanup.mjs (dry-run by default; delete needs --delete --confirm-count N). Dry run today: 1,926 old image-tar artifacts = 332 GB deletable on the maintainer's SC-2 authorization. Ready for review.

[Chris0Jeky]

PR #2341 MERGED (merge commit 3569a6f9b, 2026-08-30). On main now: ADR-0066 (Accepted under delegation; the nine rulings above are the record), the pack archived as received + RECONCILIATION.md, docs/ci/ (SMART_CI, runner threat model, cutover checklist, CI_BASELINE + the 31-day ledger), the measurement tool, and the docs/tracker/human-action reconciliation — OUTSTANDING_TASKS.md §J SC-1..SC-8 are the maintainer's queue. Review record: one fresh-context Opus review (1 HIGH + 5 MEDIUM + 9 LOW, all fixed) + one Codex round (5 P2, fixed). Behaviour-preserving: no workflow, protection, visibility, billing, runner or secret change.

[Chris0Jeky]

PR #2343 MERGED (merge commit 43de0d10a): CI-09 slice 1 — retention classes, no PR image-tar export/upload, per-class artifact names, the guarded cleanup command (1,412 PR-lane artifacts = 245.9 GB deletable on SC-2 authorization). Review record: one fresh-context Opus review (0 HIGH, 4 MEDIUM, 8 LOW) + one Codex round (1 P1, 5 P2) — all applied. Next: #2342 (shadow control plane) after its reopen head is green.

[Chris0Jeky]

PR #2342 MERGED (merge commit afdc4c454, 2026-08-30). On main now, in shadow mode: ci/policy.v1.json (+ schemas, README), the fail-closed planner and gate evaluator (40 fixtures), smart-ci-shadow.yml — Smart CI / Plan and the observation-mode Smart CI / Required Gate on pull_request_target from the PR's base commit (read-only, no head execution; trust bound to the head commit's identities) — and smart-ci-self-test.yml on pull_request, the action-pin inventory (152 references, 1 pinned), the runner broker skeleton. Changes no ci-required.yml job selection; nothing is required in branch protection. Review record: Codex round 1 (7 P1), one fresh-context Opus review (1 HIGH, 6 MEDIUM, 8 LOW), Codex round 2 (8 P1 + 6 P2 — one reopen for the HIGH introduced by a round-1 fix, six tracked on CI-03/CI-05 or declined). From the next PR on, every PR gets a shadow plan + gate receipt; CI-03 registers the gate only after >=20 PRs without a false red.

[Chris0Jeky]

Maintainer decision packet applied (2026-09-03). The packet is a ruling record from the maintainer's decision cockpit, not evidence that any external action was performed; docs and OUTSTANDING_TASKS.md are updated in PR #2442.

SC1 — the nine delegated rulings are confirmed, with the private-Pro approval-boundary amendment. Recorded in ADR-0066 (status line + Acceptance conditions section):

A personal GitHub Pro private repository has no organization ruleset, required workflow or restricted runner group, so the approval boundary the pack assumed an organization would supply is the maintainer's own account: workflow runs for outside or agent-authored changes require the maintainer's approval in the repository's Actions policy, the base-ref pull_request_target control plane stays read-only with no head execution, and control-plane (T0/T2) and runner changes are approved only by the maintainer's review — never by an agent, a bot review, or an environment binding alone. CI-13 #2337 J.6 re-checks the policy in private mode; CI-14 #2338 remains the path to an organization-supplied boundary.

The cockpit label was "confirm with private-Pro approval-boundary amendment"; the paragraph above is the agent's reading of that label. If the intended amendment differs, one reply here corrects it.

Same packet: SC-2 bounded artifact deletion authorized after a fresh dry run (outcome on #2333); SC-3 $10/month hard Actions ceiling (#2337); SC-4 no pre-ruling on branch protection (#2327); SC-8 private development repository + public release/source mirror (CI-16 #2439). SC-5/6/7 remain blocked as before.