prodockit 0.36.2

Four fixes. Three are one cause seen from different angles: a process already running never receives the PATH an installer has just set, so a bare command name fails on exactly the machine that has the software.

Fixed

Pandoc and Node reported missing while installed (#450). Both checks ran a bare pandoc/node and so saw only this process's PATH. A winget install sets the machine's PATH; a running process does not get it. The stage then offered to install what was already there, winget answered "already up to date", and the check failed again - so the run could not move on. git and VS Code had been given full-path resolution in #390 and #424; these two never were.

sync-repo could not find git (#451). It invoked git by bare name and died with could not run git: [WinError 2] on the same stale PATH. The Jinja macros and the source bundle had the same exposure. All of them now resolve through one shared list of install locations, so the stages and the commands cannot hold two answers about the same machine.

A sync check that could not run was reported as a difference (#451). sync-repo --check exits non-zero both for "there is a difference" and for "I could not look", and the stage said "the project config still needs syncing" to both - naming a cause nobody had established, and sending the reader to run something that would not have fixed it. It now says what actually stopped the check.

The site stage described the wrong host's interface (#444). Every instruction was a literal about GitHub, so GitLab readers were sent looking for a gear beside 'About' and a Settings > Pages that do not exist there. One was worse than merely wrong: it said the site "will be public", true of GitHub and false of GitLab, where a private project's site stays behind the instance's own sign-in - contradicting what the project stage had told the same reader about the same project.

Full notes: changelog