PR #15190: test(gateway): make systemd refresh tests hermetic with user D-Bus preflight

• Repository: NousResearch/hermes-agent
• Author: WadydX
• State: closed | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/15190

Description (problem / solution / changelog)

Summary

Fixes a test regression introduced by user D-Bus preflight checks in systemd user-scope commands.

This keeps runtime behavior unchanged and makes the affected unit tests hermetic again by stubbing _preflight_user_systemd where tests are specifically validating command sequencing / refresh behavior.

Changes

• Add monkeypatch.setattr(gateway_cli, "_preflight_user_systemd", lambda: None) in:
  • TestSystemdServiceRefresh::test_systemd_start_refreshes_outdated_unit
  • TestSystemdServiceRefresh::test_systemd_restart_refreshes_outdated_unit
  • TestGatewaySystemServiceRouting::test_systemd_restart_self_requests_graceful_restart_and_waits
  • TestGatewaySystemServiceRouting::test_systemd_restart_recovers_failed_planned_restart

Why

systemd_start() and systemd_restart() now call _preflight_user_systemd() before the mocked subprocess.run path. In non-systemd environments, those tests fail early with UserSystemdUnavailableError and never reach their intended assertions.

Validation

• pytest -q -n 0 tests/hermes_cli/test_gateway_service.py::TestSystemdServiceRefresh::test_systemd_start_refreshes_outdated_unit tests/hermes_cli/test_gateway_service.py::TestSystemdServiceRefresh::test_systemd_restart_refreshes_outdated_unit tests/hermes_cli/test_gateway_service.py::TestGatewaySystemServiceRouting::test_systemd_restart_self_requests_graceful_restart_and_waits tests/hermes_cli/test_gateway_service.py::TestGatewaySystemServiceRouting::test_systemd_restart_recovers_failed_planned_restart
• pytest -q -n 0 tests/hermes_cli/test_gateway_service.py

Closes #15187

Changed files

• tests/hermes_cli/test_gateway_service.py (modified, +4/-0)

PR #15420: fix(nix): refresh tui + web npmDepsHash to unblock CI on every PR (#15244, #15272, #15314)

• Repository: NousResearch/hermes-agent
• Author: briandevans
• State: closed | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/15420

Description (problem / solution / changelog)

What does this PR do?

The `Nix Lockfile Check` on `main` has been failing across every open PR for several days because two pinned `fetchNpmDeps` hashes drifted out of sync with the actual `package-lock.json` contents in `ui-tui/` and `web/`.

The CI run prints the correct hash on each failure, so this is a one-character-precision drive-by — both new hashes are exactly what every recent `Nix Lockfile Check` run is reporting (e.g. run 24916813199 from a few minutes ago):

The drift was caused by recent dependency-touching commits in:

• `ui-tui/`: PTY WebSocket bridge (`f49afd31`), package.json updates across the chat-unification series (`c61547c0`), `fix(tui): warn on bare null sections in config.yaml` (`bfa60234`)
• `web/`: docs embedding (`0fdbfad2`), sidebar layout (`e5d2815b`), dashboard extension points (`f593c367`)

None of those PRs ran the `nix flake update` follow-up, so the cached hashes never got refreshed.

Related Issues

• Closes #15244 (`nix ubuntu check failing on main again`)
• Closes #15272 (`nix CI broken on main — npmDepsHash out of date`)
• Closes #15314 (`hermes-tui npmDepsHash is out of date`)

Type of Change

• 🐛 Bug fix (CI infrastructure)
• No tests required — pure config update; the existing `Nix Lockfile Check` workflow IS the regression guard for this kind of drift

Test plan

• Both new hashes are taken verbatim from `Nix Lockfile Check` failure output: the CI computes the correct hash from the actual `package-lock.json` and prints "To correct the hash mismatch for npm-deps, use ..."
• No production code touched — only the two pinned hashes
• Once merged: every open PR's `Nix Lockfile Check` lane goes from FAILURE to SUCCESS on its next CI run

Why a separate PR (vs piggybacking on another fix)

This fix unblocks ~30 open PRs at once, including all of mine. Keeping it isolated makes the merge low-risk (1 line per file), explicit in git history, and easy to cherry-pick onto release branches if needed.

Out of scope

• Automating the hash refresh on every `package-lock.json` change (would need a CI job to compute and commit the hash). `#13136` proposed this with `automatic lockfile fixing to keep main building with nix` but was reverted in `688c9f5b`. Restoring that automation is a bigger conversation; this PR is a narrow unblock for today.

Changed files

• nix/tui.nix (modified, +1/-1)
• nix/web.nix (modified, +1/-1)