stacked-impl-laneslisted

Run the `stacked-impl-lanes` dynamic workflow bundled with this plugin by calling the Workflow tool with its bundled script path: ``` Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/.claude/workflows/stacked-impl-lanes.js", args: { /* fill from the request */ } }) ``` Fill `args` from the user's request. Common args: `lanes` (required), `mode`, `base`, `repo`. Concurrency is bounded twice: `batchSize` caps concurrent **lanes** (default 4) and `agentCap` caps total in-flight **agents** (default 12) — the lane cap alone does not bound agents, because each lane fans one issue relay out per issue. For the full, current argument list, read the header comment / `meta` block in `${CLAUDE_PLUGIN_ROOT}/.claude/workflows/stacked-impl-lanes.js`, or the repo README "Arguments" table. WRITES — opens PRs; needs write scope. Do NOT run under a read-only token; see the workflow header for its safety gates. `repo` only redirects this workflow's *reads* (the issue-text relay and the idempotency preflight) — its writes (the impl agent's worktree, `gh pr create`) always target the session's own checked-out repository, and cannot be pointed elsewhere. Passing a `repo` that disagrees with the session's own repo now aborts the run before any lane agent is dispatched, naming both repos, rather than silently reading one repo and writing to another. Omit `repo` (or pass the session's own repo) unless you need to scope reads to a fork. ### Mixed wave plans `mode` (`parallel` | `sequential`) is the *