2992d1bbea
The windows hermes-update leg fails at "Missing published launcher under <install>/.hermes/bin" -- the same checkpoint the linux and macOS harnesses were failing before they were taught to drive the next ordinary startup. Port that: when the published launcher is missing, run one ordinary startup WITHOUT the lazy-install ban so prepare_launch can complete the update, then re-ask for the launcher. Only when it is missing, so a healthy update is still judged by the strict checks; `--version` probes keep their ban. Get-SourceHermesForStartup() is the windows twin of source_hermes_for_startup: it hands out the legacy venv command for that startup only, while Get-SourceHermes stays strict for every probe. Verified: pwsh's parser accepts both files (PARSE OK, 6102 and 199 tokens).
42 lines
1.9 KiB
PowerShell
42 lines
1.9 KiB
PowerShell
# Dot-source only. Prefer the published command; never rescue a broken one
|
|
# through PATH, the user's shared bin, or an obsolete checkout venv.
|
|
function Get-SourceHermes([string]$Root) {
|
|
foreach ($name in @('hermes.exe', 'hermes.cmd')) {
|
|
$command = Join-Path $Root ".hermes/bin/$name"
|
|
if (Test-Path -LiteralPath $command) {
|
|
if (-not (Test-Path -LiteralPath $command -PathType Leaf)) {
|
|
throw "Invalid published launcher: $command"
|
|
}
|
|
return $command
|
|
}
|
|
}
|
|
if (Test-Path -LiteralPath (Join-Path $Root 'pm/lock.json')) {
|
|
throw "Missing published launcher under $Root/.hermes/bin"
|
|
}
|
|
$legacy = Join-Path $Root 'venv/Scripts/hermes.exe'
|
|
if (Test-Path -LiteralPath $legacy -PathType Leaf) { return $legacy }
|
|
throw "No installed Hermes command under $Root"
|
|
}
|
|
|
|
# Hand out a command to DRIVE the next ordinary startup, even when the
|
|
# published launcher is not there yet.
|
|
#
|
|
# A pre-handoff release cannot flip during `hermes update` -- there is no
|
|
# retired-hook seam on its update path to reach, so the update ends with the
|
|
# tree at HEAD and no `.hermes/bin/*`. The NEXT ordinary startup is what
|
|
# completes it: hermes_bootstrap calls prepare_launch() before importing
|
|
# anything, which syncs PM, publishes the launchers and re-execs.
|
|
#
|
|
# Deliberately NOT used for `--version` probes: those stay under
|
|
# HERMES_DISABLE_LAZY_INSTALLS so a probe can never complete an unfinished
|
|
# update. Only a real startup may heal.
|
|
function Get-SourceHermesForStartup([string]$Root) {
|
|
foreach ($name in @('hermes.exe', 'hermes.cmd')) {
|
|
$published = Join-Path $Root ".hermes/bin/$name"
|
|
if (Test-Path -LiteralPath $published -PathType Leaf) { return $published }
|
|
}
|
|
$legacy = Join-Path $Root 'venv/Scripts/hermes.exe'
|
|
if (Test-Path -LiteralPath $legacy -PathType Leaf) { return $legacy }
|
|
throw "No installed Hermes command to start under $Root"
|
|
}
|