Skip to content

Generate execution orchestration split #560

Description

@flyingrobots

Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.

  • Source path: docs/method/backlog/bad-code/RUNTIME_generate-execution-orchestration-split.md
  • Original filesystem lane: bad-code
  • Canonical Method lane label: lane:bad-code
  • Legend: RUNTIME
  • Migration issue: Migrate Wesley Method backlog to GitHub Issues #548
  • Migrated on: 2026-06-04

Original Local Backlog Card

Generate execution orchestration split

  • Lane: bad-code
  • Legend: RUNTIME

Why now

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

Repo Evidence

  • packages/wesley-cli/src/commands/generate-execution.mjs
  • packages/wesley-cli/src/utils/runtime-events.mjs
  • packages/wesley-cli/src/utils/schema-ir-cache.mjs
  • docs/audit/2026-05-05_code-quality.md
  • docs/audit/2026-05-05_ship-readiness.md

Activity

  1. added
    triage:bad-codeDebt intake that still needs scheduling, closure, or a repo move
    legend:RUNTIMERuntime/tooling/host/operator flow work
    on Jun 4, 2026
  2. coderabbitai commented on Jun 4, 2026

    @coderabbitai
    🔗 Related PRs

    #187 - fix(ci): repair holmes comment template indentation [merged]
    #472 - [codex] Advance Continuum inspectability and METHOD closeout [merged]
    #476 - Release/v0.1.0 [merged]
    #521 - Add Rust IR performance baseline [merged]
    #529 - Retire leaf legacy packages [merged]


    📝 Issue Planner

    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!

  3. flyingrobots commented on Jun 24, 2026

    @flyingrobots
    OwnerAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    legend:RUNTIMERuntime/tooling/host/operator flow worktriage:bad-codeDebt intake that still needs scheduling, closure, or a repo move

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions