Files
planning-with-files/scripts
OthmanAdi bb2ee81404 fix: resolve plans by literal path and validate the attester pin without IsPathFullyQualified
resolve-plan-dir.ps1 tested candidate plan directories with wildcard-interpreting
Test-Path and listed .planning with Get-ChildItem -Path. In a project path
containing [ or ] those calls match nothing under pwsh, so a valid .active_plan
pointer, the newest-plan fallback, and even an explicit PLAN_ID resolved to an
empty result and every PowerShell route injected nothing. Every path test is
now literal, like the rest of the file.

attest-plan.ps1 still validated PWF_PLAN_ROOT with [IO.Path]::IsPathFullyQualified,
which Windows PowerShell 5.1 does not have, so the attester aborted whenever the
pin was set. It now uses the same drive-qualified check PR #251 gave the
resolver. Both changes are synced to all 15 shipped copies.

Found by the v3.20.0 review of PR #251.
2026-09-17 23:09:26 +02:00
..
2026-04-29 14:44:20 +08:00