feat(orchestrator): ci-excluded task types#639
Draft
gewenyu99 wants to merge 1 commit into
Draft
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
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jun 10, 2026
The CI harness can exclude task types from a run via a CI-build-only env var (a comma-separated list, e.g. dashboard — CI runs must not create dashboards). Excluded types do not exist for the run: the seed cannot enqueue them and no agent is spun up. The policy lives with the harness that owns it; the wizard and the served content stay run-mode agnostic. Published builds strip the path, smoke-enforced alongside the flag overrides. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
850ce7d to
3c02336
Compare
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
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.

The CI harness can exclude task types from a run.
WIZARD_CI_EXCLUDE_TASKSis a comma-separated list, the registry drops those types, the seed cannot enqueue them, and no agent is ever spun up for them. The policy lives with the harness that owns it (the workbench workflow setsdashboard, CI runs must not create dashboards), so the wizard and the served agent content stay run-mode agnostic. CI-build only, same dead-strip and smoke enforcement as the flag overrides. The seed prompt plans around missing types, soreportfollowsbuildwhendashboardis absent.