OSS-Singularity/zcode-dispatch-observatory
OSS-Singularity/zcode-dispatch-observatory
Watch
1
0
Fork
You've already forked zcode-dispatch-observatory
 0
Code Issues Pull requests Projects Releases 137 Packages Wiki Activity Actions
137 releases 137 tags
  • v1.28.0 dc00d2c981

    v1.28.0 — Pinky X: service robustness
    All checks were successful
    Checks / Functional checks (push) Successful in 17s
    Details Explain this check
    Stable

    ClaudiuSchuster released this 2026-09-26 10:17:15 +00:00 | 91 commits to main since this release

    Two owner-reported defects from the 2026-09-26 station reboot, fixed in one round.

    Reboot-proof steering (S-1)

    After a reboot the user manager starts the service with the default PATH — which lacks ~/.local/bin, where the zcode-dispatch launcher symlink lives — and every steer died with "zcode-dispatch not found on PATH". Fixed at BOTH layers:

    • the systemd unit ships Environment="PATH=%h/.local/bin:…" (%h home-dir specifier, no hardcoded username; verified live via /proc//environ under a stopgap-free fresh-boot manager environment)
    • the steer spawn resolves the launcher PATH-independently (resolve_dispatcher): ZDO_DISPATCH_BIN override (a set-but-missing override is a loud error, never a silent fall-through) → absolute ~/.local/bin/zcode-dispatch → the tracked install dirs (observatory sibling checkout, ~/tools/zcode-dispatch, ~/.local/share/zcode-dispatch) → bare PATH lookup as the last resort; the 503 refusal lists every candidate tried. Both spawn sites use it (steer console + fastlane turn-boundary delivery).

    Boot-start baked into install/update (S-2)

    install.sh now runs systemctl --user enable --now after daemon-reload (owner decision 2026-09-26) — the dashboard comes back after a reboot without a manual step; README documents it.

    Validation

    84/84 unittests (+15: resolution-precedence units; a real boot-env integration rig — server under the scrubbed fresh-boot environment on a free port, steer spawns via the absolute candidate, override wins; station-unit contract for the Environment line + enablement; v1.27.0 validation follow-up F1 — the missing invalidation mutation tests: stream-history delivered flag, stream-dropped rewrite, provider-config touch, live-driver/alive-steer digest flips). Pinned Super-Linter green (BASH, BASH_EXEC, MARKDOWN, PYTHON_PYLINT, PYTHON_RUFF, YAML). G5 CPU envelope re-check: 0.72 % of one core over 22 poll cycles on a 120-session fixture rig (pre-v1.27.0 failure mode ~170 %). Fixture CDP probes green (page builds, version marker v1.28.0). Station: install triple-checked, unit enabled (G3), service PATH proven via /proc, dashboard live on 127.0.0.1:8767 at v1.28.0.

    Downloads