test: cover install and verify scripts

[TimInTech]

Summary

Adds subprocess-level regression coverage for the Linux install and verify scripts.

Covered

• scripts/verify.sh

  • config.json permission checks (0600 PASS, 0644 WARN with chmod 600, missing config INFO)
  • XDG_RUNTIME_DIR failure path
  • exit-code contract when checks fail
  • system binary discovery when required tools are present

• scripts/install.sh

  • daemon-reload warning when blitztext-linux is already running
  • no daemon-reload warning when the service is not running
  • BLITZTEXT_NO_HOTKEY validation
  • end-to-end fake-repo install smoke test through "Installation abgeschlossen"
  • service file generation

Verification

• git diff --check
• git diff --cached --check
• pytest tests/ -v
• Result: 366 passed, 70 skipped

Notes

• Tests run the bash scripts as real subprocesses in isolated fake repositories.
• System-facing commands are stubbed (dpkg-query, systemctl, pgrep, ydotool, sudo, pip), so no real apt, sudo, or systemctl calls affect the host.
• No workflow changes are required because CI already runs pytest tests/ -v.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a59f80de09

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Run install script tests as a non-root user

When pytest is run as root, which is common in Docker-based CI/dev containers, this launches install.sh with EUID=0. The script exits at its root guard before resolving BLITZTEXT_NO_HOTKEY or reaching the systemd setup, so all four install tests fail and only exercise the root check instead of the intended paths. Please run this subprocess under an unprivileged user or skip/xfail these install-script cases in root environments.

Useful? React with 👍 / 👎.