You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
packages/wesley-cli/src/commands/generate-execution.mjs is the release
branch's largest CLI orchestration hotspot. It coordinates preconditions, IR
cache resolution, unit filtering, event emission, transmutation execution,
artifact writing, snapshot persistence, evidence enrichment, history merging,
git SHA lookup, dirty-worktree policy, and failure attachment in one file.
Hill
runSequentialGeneration stays as the command-facing facade, while source/git
policy, transmutation execution, and evidence/history persistence each become
small, testable modules.
Done looks like
source/git policy checks are extracted behind focused helpers
transmutation execution and git SHA resolution are extracted and unit-tested
evidence bundle, score, and history persistence are extracted and
unit-tested
emitted event shapes and command return shapes remain backward compatible
regression coverage includes --emit-bundle, --dry-run, --print-ir, --resume, and dirty-worktree enforcement
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Closing as obsolete after the legacy Node CLI/generate-execution path was retired. The issue targets packages/wesley-cli/src/commands/generate-execution.mjs; that package/command path no longer exists in the active repo, and the current release front door is the Rust-native CLI plus cargo xtask preflight. Evidence: docs/LEGACY_NODE_MIGRATION.md, docs/ENTRYPOINTS.md, and PR #619 validation.
Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.
docs/method/backlog/bad-code/RUNTIME_generate-execution-orchestration-split.mdbad-codelane:bad-codeRUNTIMEOriginal Local Backlog Card
Generate execution orchestration split
bad-codeRUNTIMEWhy now
packages/wesley-cli/src/commands/generate-execution.mjsis the releasebranch's largest CLI orchestration hotspot. It coordinates preconditions, IR
cache resolution, unit filtering, event emission, transmutation execution,
artifact writing, snapshot persistence, evidence enrichment, history merging,
git SHA lookup, dirty-worktree policy, and failure attachment in one file.
Hill
runSequentialGenerationstays as the command-facing facade, while source/gitpolicy, transmutation execution, and evidence/history persistence each become
small, testable modules.
Done looks like
unit-tested
--emit-bundle,--dry-run,--print-ir,--resume, and dirty-worktree enforcementRepo Evidence
packages/wesley-cli/src/commands/generate-execution.mjspackages/wesley-cli/src/utils/runtime-events.mjspackages/wesley-cli/src/utils/schema-ir-cache.mjsdocs/audit/2026-05-05_code-quality.mddocs/audit/2026-05-05_ship-readiness.md