70ad92c8e3
The projects root moved from E: to F:, but Idunn's starfire-local surfaces still named E:\Projects. Local Idunn died on 2026-08-16 with "fatal: cannot change to 'E:\Projects\Heimdall'" and every one of its 16 operator alarms also failed (0xfffd0000), because notify-idunn-operator-alarm.cmd shelled to an E: path that no longer existed. The supervisor was down for 18 days and could not say so. Rather than swap one hardcoded drive letter for another, derive the projects root the way this catalog already derives its repo root: - notify-idunn-operator-alarm.cmd invokes its sibling via %~dp0. - notify-idunn-operator-alarm.ps1 resolves Bifrost from the projects root. - idunn-deployment-targets.ps1 gains $projectsRoot and rebases 19 LocalPath values onto it. The remote /srv/build/VoidBot path is left alone. Verified: the catalog resolves 15 of 20 targets to real directories, the remote target is untouched, and the alarm chain now runs to exit 0 emitting a valid gamecult.operator_dm_request.v1 under IDUNN_OPERATOR_ALARM_DRY_RUN. Still broken, not addressed here: stonks, vili, StreamPixels and repixelizer have no directory under F:\Projects, and the Bifrost publisher's non-dry path throws "definition.schema.parse is not a function" against the current CultMesh. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2 lines
105 B
Batchfile
2 lines
105 B
Batchfile
@echo off
|
|
powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%~dp0notify-idunn-operator-alarm.ps1"
|