Repository navigation
Tags
Tags
test: update the runner dispatch pin for the generalized resume gate implement-task now forwards WORKTREE PATH / TASK BRANCH / RESUME EXISTING WORKTREE for runner-supplied worktrees and interactive resume-gate results alike; pin both the new wording and the resume-gate conditional.
fix: honor explicit --project in batch skills (v3.6.7)
Concurrent batch sessions on the same monorepo collided on project
selection: just-do-it and just-do-it-swarming ignored their argument and
Step 0 unconditionally invoked select-project whenever {{project_name}}
resolved empty, flipping the workspace-level selection shared by all
pane-less sessions (notably ZCode, which has no pane identity and keys
selection state on the repository).
- Add --project <name> as the highest-precedence Step 0 resolution in
both batch skills: resolve from .groundwork.yml, never invoke
select-project, never persist a selection change, skip the CWD
mismatch check, and map {{specs_dir}}/{{plans_dir}} to the resolved
project root.
- Thread the explicit project downstream: --project on validate and
finalize-task, worktree-identity.js TASK-NNN --project <name>,
GROUNDWORK_PROJECT=<name> on lib calls, and an ACTIVE PROJECT line in
swarming teammate spawn prompts.
- Advertise the flag in portable description prose that survives the
export installer's slash-hint strip, so all export targets and the
ZCode marketplace bundle show it.
- Add tests/batch-project-argument.test.js pinning precedence, the
select-project prohibition, and downstream threading.
PreviousNext