feat(orchestrator): surface per-framework SDK docs to task agents#686
Open
gewenyu99 wants to merge 3 commits into
Open
feat(orchestrator): surface per-framework SDK docs to task agents#686gewenyu99 wants to merge 3 commits into
gewenyu99 wants to merge 3 commits into
Conversation
Collect the reference skill's per-framework docs (everything in references/ except EXAMPLE.md, COMMANDMENTS.md, and the monolith's numbered workflow files) and inject them via a new docsReference, so docs-only frameworks (Go, Elixir, Flutter) and every non-JS framework get their real SDK reference instead of the step-skill's wrong JS/Node docs or nothing. Also watch the event plan in the run cache dir as well as the project root: the orchestrator capture step now writes .posthog-events.json under .posthog-wizard-cache (torn down with the run), while the linear flow still writes it at the root. The TUI can't tell the flows apart, so it watches both. Pairs with the context-mill basic-integration skill changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🧙 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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
The SDK-divergent step-skills (install, init, capture, error-tracking) now ship per-framework variants ided as <baseId>-<framework>. Resolve each agent's bare skill id to the variant for the run's framework before installing, mirroring resolveReferenceSkillId: exact match, else first granular variant, else the bare id unchanged for the generic single-variant steps (identify, report, dashboard, build). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The orchestrator's cache-dir event-plan watcher ran in the default RunScreen, hitting every flow ungated. All orchestrator behaviour must sit behind the wizard-orchestrator flag. Restore RunScreen to its main version; the orchestrator event-plan surfacing will be re-added inside the flag-gated orchestrator path. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Orchestrator task agents now get the framework's own SDK docs.
go.md,next-js.md, …), skipping the structural files (EXAMPLE.md,COMMANDMENTS.md) and the monolith's numbered workflow files. For docs-only frameworks with noEXAMPLE.mdthese docs are the only HOW signal.<baseId>-<framework>) when one is published, else falls back to the bare skill.