Windows: Full-mode manifest still gates open/open-link/last to macos+linux after #31 revert

[kursku]

Context

On Windows the manifest (bfe0de8, and current main) gates the Full-review entrypoints — the [[build]], the doc pane, and the open / open-link / last actions plus the markdown link_handler — to ["macos","linux"]. So Windows users get only capture / copy-* / manage; the whole plannotator-tui review flow is unreachable, even though scripts/fetch-plannotator-tui.ps1 exists and the tui ships an x86_64-pc-windows-msvc.exe asset.

I ran the ps1 locally: it fetches + sha256-verifies + stages bin/plannotator-tui.exe (0.7.0) cleanly, and plannotator-tui.exe --version runs. Flipping the three actions to include windows makes them work as-is, since Herdr's relative-program resolver applies to actions (they use ./bin/plannotator-tui.exe).

The real blocker (why #30 was reverted in #31)

The doc pane command can't use ./bin/… — the resolver doesn't apply to panes; they spawn with the review folder as --cwd. The Unix manifest sidesteps this with a wrapper resolving via $HERDR_PLUGIN_ROOT:

["sh","-c","exec bash \"$HERDR_PLUGIN_ROOT/scripts/plannotator-tui.sh\" herdr pane"]

That wrapper needs sh+bash, which native Windows (no Git Bash) lacks. That's the piece still missing for a clean Windows re-enable.

Question

Would a pwsh-based pane wrapper resolving the binary via $HERDR_PLUGIN_ROOT (mirroring the pattern herdr-file-viewer / herdr-sidebar already use for their -windows action variants) be the accepted path to re-land Windows Full-mode? Happy to open a PR along those lines if so.

[backnotprop]

Thanks, and yes, we want this. Two corrections and the shape we'll merge.

1. Flipping the three actions alone doesn't work: open and last launch the doc pane, which would still be gated off, so every review fails to open.
2. A second doc pane can't exist. Herdr rejects duplicate pane ids even with disjoint platforms, and a PowerShell wrapper in the middle is out: it puts a process between Herdr and the TUI, and on 0.8.2 the plugin root arrives as an extended-length \\?\ path that PowerShell mishandles.

Accepted design: a separate Windows install variant, windows-full/herdr-plugin.toml, requiring Herdr 0.9.0, where panes resolve relative programs against the plugin root. Its doc pane is direct argv: ["./bin/plannotator-tui.exe", "herdr", "pane"], no wrapper. Actions use the same direct argv. The root manifest stays as is; Windows on 0.8.2 keeps Lite.

The acceptance checklist (manifest parity, the fetch contract, and what the Windows CI runner must prove) is going into the repo shortly and I'll link it here. If you want to take the PR against it, say so. You have Windows hardware and we don't, so your live results would also count as the native qualification.

[backnotprop]

The acceptance checklist is in the repo now: https://github.com/plannotator/herdr-annotate/blob/main/docs/windows-full-acceptance.md. That's the target for the windows-full/ variant if you take it.