Repository navigation
feat(agents): stop publishing the orchestrator prompts - #536
Conversation
The wizard bundles its orchestrator prompts, so context-mill publishes skills only. A release carries no `agent-menu.json` and no `agents-<flow>-<type>.md`, the dev server serves no prompt routes, and the mirror copies and verifies the skill menu alone. `context/agents/`, its generator and the graph script are gone, with the tests that read prompt files. The old-wizard compatibility test reads the names it checks from its snapshot. Co-Authored-By: Claude Fable 5.2 <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
Test against a wizard branch:
Add Results will be posted here when complete. |
johncwaters
left a comment
There was a problem hiding this comment.
Verdict: APPROVE WITH NITS
See inline comments.
Automated review by Glimmervoid. Not written by a human
| @@ -1,188 +0,0 @@ | |||
| /** | |||
There was a problem hiding this comment.
[boundary] MEDIUM
#474 (spend audit flow) is still open and merges cleanly with this, but its new spend-audit-flow.test.js imports buildAgents from ../agent-generator.js and reads agents/agent-menu.json. Once both land, npm test on main fails, and its 11 prompts under context/agents/spend-audit/ never ship. That flow probably wants to move into the wizard's bundled prompts before either merges.
Automated review. Not written by a human
gewenyu99
left a comment
There was a problem hiding this comment.
Stale ownership in .github/CODEOWNERS: these lines point at context/agents/ folders this PR deletes. Suggested fix:
-/context/agents/error-tracking/ @PostHog/team-error-tracking
-/context/agents/metrics/ @PostHog/team-apm
-/context/agents/integration-v2/ @PostHog/team-growth
-/context/agents/replay-vision/ @PostHog/team-replayCo-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
main stopped publishing the agent prompts (#536), which removed context/agents from the dev server's watch list. Keep context/shared there, drop context/agents. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What this does
context-mill publishes skills only. The wizard bundles its orchestrator prompts, so a release carries none.
After this change a release has:
agent-menu.jsonagents-<flow>-<type>.mdand everything else it has today.
What goes with them:
context/agents/, 49 prompt files across six flows, and its READMEscripts/lib/agent-generator.js, and the prompt build inscripts/build.jsandscripts/dev-server.js/agent-menu.jsonand/agents-…routesscripts/mirror-dist.js, and the prompt menu check inscripts/verify-mirror.jsbuild-release.ymlscripts/visual-dags.jsand itsvisual-dagspackage script, which drew its graphs fromcontext/agents/agent-generator-flow,integration-observability-flow,error-tracking-env-loading, and one case oferror-tracking-link-releasesThe old-wizard compatibility test keeps checking skill resolution. It reads the names it checks from its snapshot, which no longer lists prompt files.
.github/CODEOWNERSis not changed. Its four/context/agents/…lines now match no path.Verification
npm test: 419 tests pass.scripts/mirror-dist.jsruns on its output.agents/agent-menu.jsonand the 49agents/agents-*.md. No other published file differs.Rollout
Stacked on the
matchchange.A wizard that fetches its prompts from the latest release cannot plan a run once this ships. Merge it only when all of these hold:
wizard-agent-dagandwizard-agent-dag-skillsare both still on🤖 Generated with Claude Code