[as992949791]

Closes #300.

The manual /plan-goal and topic-handoff instructions still selected the newest plan, although the resolver rejects ambiguous multi-plan selection. Those instructions could direct an agent into another task.

Both workflows now use the installed resolver with PLAN_ID and PWF_PLAN_ROOT, stop when selection is rejected or ambiguous, and use legacy root files only when the resolver selects that directory. The text also explains that .active_plan is a shared default and that parallel hosts need explicit task pins or separate worktrees.

Updated the canonical skill, its npm and .agents copies, and docs/workflow.md. The current sync script intentionally excludes SKILL.md, so the shared instructions were updated directly while preserving adapter frontmatter. Resolver, hooks, installers, and versions are unchanged.

Validation on macOS:

• The existing ambiguous-plan regression passes; a separate documentation assertion fails at the base and passes after the fix.
• Full pytest before and after the initial edit: 908 passed, 263 existing skips, 927 subtests. The final wording refinement was checked with the documentation assertion, sync verification, and 31 resolver/parity tests (120 subtests).
• Pi: 54 tests passed. OpenCode: build and 51 tests passed.
• sync-ide-folders.py --verify, mirror/frontmatter checks, and git diff --check passed.

The checkout was recovered from verified GitHub blobs after an archive transfer failed. An unrelated root banner was excluded from the local checkout and is not part of this patch. Remote Linux/Windows/macOS CI remains for the PR workflow. This contribution was prepared with AI assistance.

[OthmanAdi]

@as992949791, the manual newest-plan fallback in #300 is confirmed to contradict the resolver's ambiguity protection. Your change routes those workflows through the installed resolver and explains the parallel-session pin correctly.

I will make one small wording correction for legacy root plans: the resolver returns an empty result for that mode, so the guide must describe that convention accurately while still refusing invalid pins and ambiguous named plans. I will verify the resolver regression and skill mirrors before merging, and comment again when it ships.

[OthmanAdi]

@as992949791, this is fixed in v3.23.0. The manual workflows now use the installed resolver and stop on invalid pins or ambiguous plan selection. The follow-up correction handles the resolver's empty legacy-root result explicitly, so it cannot be mistaken for a selected directory.

Your commit was merged with its author preserved, and you are in CONTRIBUTORS.md. Release commit: 41f60ae.

The full Python suites passed on Linux, macOS and Windows, together with the Pi, OpenCode and DSH checks: https://github.com/OthmanAdi/planning-with-files/actions/runs/37493922170. The released master has the same tracked tree. All six post-push CI jobs passed: https://github.com/OthmanAdi/planning-with-files/actions/runs/37496399322.

The release is available on GitHub. ClawHub v3.23.0 is published as latest; all 32 remote file hashes match the verified staging bundle. The npm packages are published: planning-with-files 3.23.0 and dsh-planning-with-files 1.0.1. Registry availability was rechecked on 10 October 2026.