Skip to content

10 · Switchboard reshape → merge-readiness (audits + main merge) #788

Closed

Description

@gewenyu99

Sub-issue of epic #520. Merge-readiness gate for the switchboard reshape — PRs #778 (harnesses + sequences), #779 (CLI overrides), #780 (switchboard interface), all folded into #701, with latest main merged in.

Phase A — Audits

A1 · No flags, no rollout ⇒ identical to main — ✅ PASS (one telemetry caveat)

Every program resolves to linear / anthropic / sonnet, as on main.

  • resolveSequence/resolveHarness fall through to DEFAULT_BINDING when no CLI override and no PostHog flag are set. All 16 PROGRAM_BINDINGS = DEFAULT_BINDING.
  • The linear path runs the same initializeAgent + runAgent main runs inline; main did not touch that call in the merge window (verified by diff) — the feat(pi): harnesses and sequences #778 seam stays behavior-preserving.
  • Caveat (non-functional): telemetry changed variant (base/orchestrator) → sequence + harness tags. Nothing in the repo reads variant anymore, but external dashboards/gateway experiments keyed on it stop receiving it → migrate under 07 — Rollout + per-runner observability (canary via wizard-runner) #527. Not a merge blocker.

A2 · main moved — nothing broke — ✅ PASS

  • 5 merge conflicts resolved by keeping feat(pi): real PostHog MCP dashboard, env lockdown, perf parity #701's seam and porting main's features (composed sub-runs, HostResolution, formatYaraAbortMessage, getLlmGatewayUrlFromHost→getLlmGatewayUrl).
  • main's new work intact (agent-interface +159: credential-places auth screen, token/cost tracking, HostResolution). Build passes; 1144/1144 tests pass (main's ~108 new tests included).
  • Non-blockers: pre-existing main tsc type errors (AuthErrorScreen, ci-region.test) — CI doesn't run tsc; not introduced by the merge.

A6 · Orchestrator unreachable without a flag — ✅ PASS

  • Only decision point: binding.sequence === Sequence.orchestrator, sourced from resolveSequence → fallback linear. No binding sets orchestrator.
  • Prod: reachable only via wizard-orchestrator = true. --sequence is triple-gated out of published builds (undeclared under !IS_PRODUCTION_BUILD, rejected in init(), middleware tree-shaken).
  • Dev/test: additionally via --sequence orchestrator. Pinned by a guard test in 08 — Cross-runner parity test suite #528.

Phase B — Pre-merge sweep

  1. Default run (no flags) on Next.js app-router — proves A1 in a real run (snapshot 1)
  2. --harness pi --sequence linear — pi on anthropic (snapshot 2)
  3. --harness pi + OpenAI model, linear — pi openai-completions (snapshot 3; needs --model, see 08 — Cross-runner parity test suite #528)
  4. Orchestrator stays gated (guard test, 08 — Cross-runner parity test suite #528)
  5. Composed sub-run (self-driving → integration) skips outro (merge seam)
  6. Host resolution across US/EU (pi gateway + linear continue-URL) (main's refactor)
  7. YARA abort copy renders (main's change)
  8. Prod build rejects --harness/--sequence + env vars (verified)
  9. sequence/harness tags emit; variant dashboard migration (07 — Rollout + per-runner observability (canary via wizard-runner) #527)

Full plan + test scenarios: #528.

Activity

  1. gewenyu99 commented on Jul 3, 2026

    @gewenyu99
    CollaboratorAuthor

    Done — switchboard reshape merged via #701 (additive, default-off; anthropic + sonnet default untouched).

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