ci: host-eval job (#705) runs in the merge queue but is not a required check — it cannot gate a merge #3039

Activity

1. dezren39

   added

   kind/ciCI/CD pipelines, workflows, and build automationCI/CD pipelines, workflows, and build automation

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   area/ciCI/CD pipelines, workflows, and build automation (area)CI/CD pipelines, workflows, and build automation (area)

   on Oct 31, 2026
2. github-actions

   assigned

   dezren39

   on Oct 31, 2026
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator job

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 3, 2026
4. developing-today commented on Nov 3, 2026

   

   developing-todayBot

   on Nov 3, 2026 – with developing.today

   Contributor

   More actions

   agent-note:v1
   state: triaged (coverage pass)
   Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
   Found via: coverage pass 2026-11-03
5. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 3, 2026
6. developing-today commented on Nov 3, 2026

   

   developing-todayBot

   on Nov 3, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane M shift
   • Session / ID: queue task 8008 (triage, coverage pass 2026-11-03)
   • Found via: queue claim · coverage join
   • Task: Triage ci: host-eval job (#705) runs in the merge queue but is not a required check — it cannot gate a merge #3039 at current main: verify whether the host-eval job still cannot gate a merge, and route the fix or record the decision path.
   • Expectation: effort/xs for the triage itself — done = verdict with fresh-main evidence + follow-up enqueued or blocker recorded
   • Links: issue ci: host-eval job (#705) runs in the merge queue but is not a required check — it cannot gate a merge #3039 · PR ci(nix-ci): add PR-tier NixOS host evaluation job (#705) #3025 · issue ci: no PR check evaluates a NixOS host — PR #699's broken amd service merged green and failed only on the laptop switch #705
7. developing-today commented on Nov 3, 2026

   

   developing-todayBot

   on Nov 3, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · done (triage verdict: STILL LIVE in substance, premise SUPERSEDED — routed as a docs-decision fix)

   • Agent: queue worker (repo-worker-code), lane M shift
   • Session / ID: queue task 8008 (triage, coverage pass 2026-11-03)
   • Found via: queue claim · coverage join
   • Task: Re-verify ci: host-eval job (#705) runs in the merge queue but is not a required check — it cannot gate a merge #3039 at current main and route it

   Evidence (fresh, 2026-11-03, main 77f911fbfc5):

   • PR ci(nix-ci): add PR-tier NixOS host evaluation job (#705) #3025 is MERGED (2026-10-31) and the basic: NixOS host evaluation job exists in .github/workflows/nix-ci.yml (line 53) — the job itself landed.
   • But the gating premise changed after filing: commit 285e425b7 (2026-11-02, "ci: no PR triggers — workflows run on main push, schedule, or manual dispatch only") removed the merge_group/pull_request triggers. On current main nix-ci.yml runs on push[main], schedule, and workflow_dispatch only — host-eval does not run in the merge queue at all now, so it still cannot gate a merge, for a stronger reason than the one filed.
   • .github/ci-policy.md (§ Merge queue, lines 47–60) is stale against that policy: it still says the queue enforces basic: proxy port fallbacks and that "nix ci also runs on merge_group events".
   • Verification limit: gh api repos/developing-today/code/rulesets and branches/main/protection return empty for the worker token, so the ruleset's current required-check list could not be read directly this run.

   Routing — follow-up queue task 8675 enqueued (small_fix, docs-only, dedupe repo-health:v1:fix:developing-today/code:issue:3039): take acceptance route (b) — update .github/ci-policy.md to record that host-eval stays advisory under the 2026-11-02 main-only CI policy, naming the accepted main-tier controls (host-eval on push-to-main; ci-fix dispatch on host-eval failure, commit 43807e56f; main-broken.yml), and reconcile the merge-queue section with the current triggers; then close #3039 on that record.
   Explicitly NOT routed: acceptance route (a) — adding host-eval to the ruleset's required checks — reverses Drew's 2026-11-02 main-only CI order and needs repo-admin access this token lacks. That is a Drew decision, not a worker fix; if it is ever wanted, task 8675's worker escalates rather than implements.

   This triage (task 8008) completes as triaged.
   (Note: posted via the developing.today GitHub App — the user-token content-creation secondary rate limit is still active this shift.)
8. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 3, 2026