feat(ci): flag overrides that exist only in CI builds#635
Merged
gewenyu99 merged 1 commit intoJun 18, 2026
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
Collaborator
Author
gewenyu99
force-pushed
the
experiment/orchestrator-ci-flag-overrides
branch
from
6fa5a9e to
a66f029
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-email-targeting
branch
from
2804e98 to
52f3310
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-ci-flag-overrides
branch
from
a66f029 to
2dc8205
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-email-targeting
branch
from
52f3310 to
d306bbf
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-ci-flag-overrides
branch
from
2dc8205 to
cf2068f
Compare
This was referenced Jun 10, 2026
gewenyu99
force-pushed
the
experiment/orchestrator-ci-flag-overrides
branch
from
cf2068f to
a152b1c
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-email-targeting
branch
from
d306bbf to
06915e5
Compare
This was referenced Jun 16, 2026
gewenyu99
force-pushed
the
experiment/orchestrator-email-targeting
branch
from
06915e5 to
751692d
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-ci-flag-overrides
branch
from
a152b1c to
49b7368
Compare
gewenyu99
force-pushed
the
experiment/orchestrator-email-targeting
branch
from
751692d to
b695c9a
Compare
POSTHOG_WIZARD_CI_FLAG_OVERRIDES (a JSON object of flag key → value) merges over the flags PostHog returns, so CI routes deterministically — a run that tests the orchestrator arm says so instead of depending on a live flag. Published builds inline NODE_ENV and tsdown strips the entire override path from the bundle; the smoke test asserts the env var's name is physically absent from production output and present in CI output, on every build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Base automatically changed from
experiment/orchestrator-email-targeting
to
experiment/orchestrator-01-bootstrap-gating
June 18, 2026 14:22
gewenyu99
force-pushed
the
experiment/orchestrator-ci-flag-overrides
branch
from
49b7368 to
552c7be
Compare
gewenyu99
merged commit 0f0d223
into
experiment/orchestrator-01-bootstrap-gating
5 checks passed
gewenyu99
added a commit
that referenced
this pull request
Jun 18, 2026
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gewenyu99
added a commit
that referenced
this pull request
Jun 18, 2026
…rd-orchestrator flag) (#606) Experimental task-queue orchestrator, collapsed from an 11-PR stack into this single branch. Behind the `wizard-orchestrator` feature flag, off by default — with the flag off it is a no-op and the existing linear flow runs unchanged. ## Wizard PRs folded in (squash-merged into this branch) - #607 — queue persistence - #608 — orchestrator MCP tools: enqueue_task / complete_task / read_handoffs, with guards - #609 — executor - #619 — agent loader - #620 — email targeting - #635 — CI flag overrides - #637 — ephemeral skills - #638 — telemetry (responsiveness A/B spine) - #639 — CI task filter - #677 — run cache + responsiveness analytics - #678 — CI health-check advisory ## Related PRs, other repos - PostHog/context-mill#181 — `agents` content type: agent prompts plus the `basic-integration` step-skills, built and served alongside skills - PostHog/wizard-workbench#1879 — CI flag-override and task-exclude dispatch inputs (dev/CI stack) ## Flag gating — why this is a no-op with the flag off - `runProgram` forks on `isOrchestratorEnabled(flags)` = `flags['wizard-orchestrator'] === 'true'` (default false). Off, it runs `runLinearProgram`, the existing path, untouched. - The shared `runAgent` threads the same flag through, so its orchestrator-specific message handling is gated too. - The CI flag-override (`WIZARD_CI_FLAG_OVERRIDES`) is guarded by `NODE_ENV === 'production'` and stripped from published builds — a smoke test asserts the env-var names are physically absent — so it cannot flip the flag for real users.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WIZARD_CI_FLAG_OVERRIDES, a JSON object of flag key to value, merges over whatever PostHog returns, so CI routes deterministically instead of depending on a live flag someone can edit. The override path exists only inbuild:cibundles. Published builds inline NODE_ENV and tsdown strips it entirely, and the smoke test asserts the env var's name is physically absent from production output and present in CI output, on every build. A malformed override fails the run loudly, and a valid one applies even when the flag fetch fails.