Skip to content

basic: proxy port fallbacks is red on main — the antigravity-direct guard row still requires an opencode.jsonc baseURL after the #1414 native-provider repoint #5497

Open

Description

@dezren39

What is broken

basic: proxy port fallbacks (.github/workflows/proxy-port-fallbacks.yml → .github/scripts/check-proxy-port-fallbacks.sh) fails on every PR and on main:

::error::.opencode/opencode.jsonc has no {env:ANTIGRAVITY_DIRECT_PORT:-18751} baseURL — the fallback must match the antigravityDirectProxyPort definition (18751); a bare {env:ANTIGRAVITY_DIRECT_PORT} resolves to an empty port outside a home-manager shell (#434).

Because basic: proxy port fallbacks is the required check for the main merge queue (.github/ci-policy.md), no PR can currently merge.

Why

The guard table (check-proxy-port-fallbacks.sh, line ~57) still marks the antigravity-direct door has_config=yes:

"ANTIGRAVITY_DIRECT_PORT|antigravityDirectProxyPort|bin/antigravity-direct.mjs|yes"

But the provider was deliberately repointed in .opencode/opencode.jsonc on 2026-11-04 (opencode#1414 / #5483): antigravity-direct now rides the native in-fork provider (opencode#1457) and has no baseURL/apiKey, so the {env:ANTIGRAVITY_DIRECT_PORT:-18751} fallback no longer exists by design.

This is the same shape as the codex precedent already recorded in the script header: the door program still exists, only its opencode.jsonc provider was re-seated elsewhere, so the row keeps its script check and drops the config expectation.

Fix

One character-class change: set the antigravity-direct row's last field to no (keep the bin/antigravity-direct.mjs fallback check, which still passes), and update the retirement note in the script header to name the #1414/#5483 repoint. The :18751 door unit and bin/antigravity-direct.mjs retire later after the zero-traffic window; when the script retires too, the row goes away entirely.

Evidence

  • main ffc19be78: bash .github/scripts/check-proxy-port-fallbacks.sh → exit 1 with the error above.
  • Confirmed on the merged tree of PR feat(id): resume tokens and bounded screen baselines — #805 Phase 2 #5036 (queue/5906-805-screenpatch-phase-2) — the failure is not caused by that branch.
  • Reproduced in CI on run 41846464347 job 126632250062 (re-run after a runner-less cancellation).

Impact

Fleet-wide: it blocks the merge queue, not just one PR.

Activity

  1. added
    kind/ciCI/CD pipelines, workflows, and build automation
    priority/highImportant and time-sensitive
    area/ciCI/CD pipelines, workflows, and build automation (area)
    main-brokenmain branch full-suite (main tier) is red; remediation chain owns this
    on Nov 4, 2026
  2. developing-today commented on Nov 4, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 5, 2026
  4. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off

  5. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  7. 112 remaining items

  8. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    queue/claimedQueue worker lifecycle state
    on Nov 6, 2026
  9. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  10. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  11. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off (second cycle this shift)

  12. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    work/assignedQueue worker lifecycle state
    on Nov 7, 2026
  13. dezren39 commented on Nov 7, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: task 10072; monitor run 2026-11-07 04:12 CST
    • Found via: monitor reconciliation (claim/label divergence)
    • Task: Claim evaporated — task 10072 is queued and unclaimed in repo-health-code-pilot (no live lease) while this issue still carried claimed/assigned labels. Labels reset to the truth: queue/queued + status/needs-triage. Last checkpoint stage on the task: probe_lane_check.
    • Expectation: the next queue claimant picks up task 10072 from its checkpoint; no work was lost.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/ciCI/CD pipelines, workflows, and build automation (area)kind/ciCI/CD pipelines, workflows, and build automationmain-brokenmain branch full-suite (main tier) is red; remediation chain owns thispriority/highImportant and time-sensitivequeue/queuedHas a queued task in the Supabase agent queuestatus/needs-triageNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions