ci(wizard): flag-override + task-exclude dispatch inputs#1879
Open
gewenyu99 wants to merge 1 commit into
Open
Conversation
Adds optional `flag_overrides` (JSON) and `exclude_tasks` (comma list)
dispatch inputs, threaded resolve-inputs → discover outputs → the Execute
wizard env as WIZARD_CI_FLAG_OVERRIDES / WIZARD_CI_EXCLUDE_TASKS. Default
empty, so normal runs are unaffected; lets a run force the orchestrator
arm (`{"wizard-orchestrator":true}`) and skip dashboard in CI.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
sarahxsanders
approved these changes
Jun 18, 2026
gewenyu99
added a commit
to PostHog/wizard
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.
Adds optional
flag_overrides(JSON) andexclude_tasks(comma list)dispatch inputs, threaded resolve-inputs → discover outputs → the Execute
wizard env as WIZARD_CI_FLAG_OVERRIDES / WIZARD_CI_EXCLUDE_TASKS. Default
empty, so normal runs are unaffected; lets a run force the orchestrator
arm (
{"wizard-orchestrator":true}) and skip dashboard in CI.Co-Authored-By: Claude Fable 5 noreply@anthropic.com