[Loosen CLI Worktree Contract] Allow proven execution checkout outside session cwd

[lossyrob]

Closes #295

Summary

Loosen the Copilot CLI dedicated-worktree contract so PAW can operate on a proven execution checkout even when the session cwd remains outside that directory.

Changes

• update PAW agent and skill instructions to require a proven execution checkout rather than requiring the session cwd to already be inside it
• update workflow docs/spec text to describe out-of-checkout CLI worktree execution while preserving caller-checkout immutability
• add CLI-oriented regression coverage for both the positive out-of-cwd flow and the failure case where no execution checkout can be proven
• add prompt-content assertions to prevent the old wording from regressing

Testing

• ./scripts/lint-prompting.sh agents/PAW.agent.md
• ./scripts/lint-prompting.sh skills/paw-init/SKILL.md
• ./scripts/lint-prompting.sh skills/paw-git-operations/SKILL.md
• npm run compile
• npm run lint
• cd tests/integration && npx tsx --test tests/skills/execution-contract-content.test.ts
• cd tests/integration && npx tsx --test tests/workflows/worktree-bootstrap.test.ts
• npm test still reports two existing timeout failures in Git Validation Helpers dirty-state tests unrelated to the touched files

Breaking Changes

None.

Artifacts

• PAW workflow artifacts

🐾 Generated with PAW

[Copilot]

Pull request overview

Loosens PAW’s Copilot CLI dedicated-worktree execution contract so workflows can safely operate on a proven execution checkout even when the session working directory remains in a different checkout (caller checkout immutability preserved).

Changes:

• Updates agent/skill contract wording to require proving the execution checkout (vs requiring the session to already be inside it).
• Updates documentation/spec to describe out-of-cwd CLI worktree execution while keeping the caller checkout immutable.
• Adds/updates integration + content-regression tests covering the positive out-of-cwd flow and the “cannot prove execution checkout” failure mode.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tests/integration/tests/workflows/worktree-bootstrap.test.ts	Adds regression coverage for out-of-cwd execution and “cannot prove execution checkout” failure behavior.
tests/integration/tests/skills/execution-contract-content.test.ts	Adds prompt-content assertions to prevent the old “must already be in checkout” wording from regressing.
src/test/suite/initializeWorkItem.test.ts	Updates extension-side tests to match new contract wording present in skill templates.
skills/paw-init/SKILL.md	Updates CLI worktree initialization contract to allow session cwd ≠ execution checkout (with proof requirement).
skills/paw-git-operations/SKILL.md	Updates shared git contract wording to allow session cwd ≠ execution checkout (with proof requirement).
agents/PAW.agent.md	Updates top-level agent execution-checkout rules to align with the new “proven checkout” contract.
docs/specification/implementation.md	Updates spec text describing CLI behavior for worktree mode.
docs/guide/workflow-modes.md	Updates user guide wording for Dedicated Worktree behavior in Copilot CLI.

[Copilot]

The updated CLI worktree contract allows session cwd to differ, but it doesn’t explicitly state how git/file operations must be executed in the proven execution checkout when cwd is elsewhere. As written, “current repo/branch/worktree state” is ambiguous and can be misread as the caller checkout’s state, which risks mutations in the wrong checkout. Please clarify that when cwd differs, the agent must run git commands against the candidate execution checkout path (e.g., by changing directories or using path-scoped git commands) and must treat the caller checkout’s repo/branch state as non-authoritative for proof.

[Copilot]

This contract says the session cwd may differ from the execution checkout, but it doesn’t specify that all git operations must be performed in the proven execution checkout directory (not the session cwd). Without that explicit requirement, the “current repo/branch/worktree state” phrasing is ambiguous and can lead to running git commands in the caller checkout. Please tighten the wording to require path-scoped git operations (or an explicit cwd switch) whenever the session cwd isn’t the execution checkout.

Suggested change

	- If `Execution Mode: worktree`, continue only when the intended execution checkout can be proven from `WorkflowContext.md` metadata plus the current repo/branch/worktree state. The session cwd may differ from the execution checkout, but the caller checkout must never be mutated.
	- If the execution checkout is ambiguous or cannot be proven from this session, STOP and report recovery guidance instead of guessing.
	- If `Execution Mode: worktree`, continue only when the intended execution checkout directory can be proven from `WorkflowContext.md` metadata plus the repo/branch/worktree state **for that execution checkout**, not the caller checkout. The session cwd may differ from the execution checkout, but **all git operations MUST be performed in the proven execution checkout directory**, either by using path-scoped git commands (for example, `git -C <execution-checkout-path> …`) or by explicitly switching the process cwd to that directory. The caller checkout must never be mutated.
	- If the execution checkout directory is ambiguous or cannot be proven from this session, STOP and report recovery guidance instead of guessing; do not run git commands against the caller checkout as a fallback.

[Copilot]

The new rule allows the session cwd to differ from the execution checkout, but the agent instructions don’t explicitly require that all bash/git commands be executed in the proven execution checkout when cwd is elsewhere. This omission makes the “current repo/branch/worktree state” proof step ambiguous and risks accidental mutations in the caller checkout. Please add a concrete requirement that all git mutations and artifact writes must be performed via the proven execution checkout path (not the session cwd).

Suggested change

	- All branch creation, checkout, pull, push, PR-prep, and artifact writes happen only in the proven execution checkout.
	- In worktree mode, the caller checkout must never be mutated.
	- All branch creation, checkout, pull, push, PR-prep, git mutations, and artifact writes MUST execute **using the proven execution checkout path as the working directory**, never the session cwd when it differs (e.g., set the tool `cwd` to the execution checkout or use `git -C <execution-checkout> ...` and path-qualified file writes).
	- In worktree mode, the caller checkout must never be mutated. Do not run mutating git or filesystem commands in the caller checkout or any directory other than the proven execution checkout.