raspi-sentinel v0.9.0 — Open Beta

raspi-sentinel v0.9.0 - Open Beta

Beta Focus

v0.9.0 is an open beta focused on external usability and safe onboarding.

Primary goals:

• reduce trial friction for new users
• keep recovery behavior safe-by-default
• make issue reports reproducible and actionable
• validate install/config/runtime behavior across diverse Raspberry Pi environments

Highlights

• README/README.ja reshaped for beta onboarding:
  • explicit "who should try / who should not use yet"
  • 15-minute quickstart
  • emergency stop path
  • feedback-first issue flow
• Security and migration baseline:
  • SECURITY.md and Japanese security policy
  • upgrade guides (docs/UPGRADE.md, docs/UPGRADE.ja.md)
• Feedback intake hardening:
  • GitHub issue form for beta failures
  • label taxonomy for severity/area/repro context
• Diagnostics and operations tooling:
  • doctor --fix-permissions
  • doctor --support-bundle (sanitized output)
  • export-prometheus --textfile-path
  • verify-storage --no-cooldown for ad-hoc preflight checks
  • helper scripts for systemd install and sample failure injection
• Dry-run and recovery safety hardening:
  • --dry-run suppresses external notifications by default
  • --send-notifications provides explicit dry-run notification opt-in
  • config validation now enforces reboot_threshold > restart_threshold
  • apply_recovery() internals split into focused helper stages
  • reboot-intent cycles now keep trailing targets explicit as skipped entries
• Secret handling hardening:
  • command-check failure messages now redact credential/token patterns
• Corrupt-state handling notes:
  • quarantine suffix slots are bounded per timestamp (.99 max), with explicit logging when saturated

Breaking / Behavior Notes

• No intentional breaking config schema change in this beta target.
• Recovery remains staged (warn -> restart -> guarded reboot), with cooldown and guardrails.
• Reboot actions should remain disabled or tightly guarded until dry-run verification is complete on target hosts.

Beta Testing Guidance

Recommended first-run sequence:

1. validate-config --strict
2. doctor --json
3. run-once --dry-run --json
4. sample failure injection (scripts/failure_inject.py)
5. state/event inspection
6. issue report with support bundle

Useful command:

raspi-sentinel -c /etc/raspi-sentinel/config.toml doctor --json --support-bundle ./support-bundle.json

Please redact secrets before posting publicly (webhook URLs, tokens, private host details).

Known Limitations

• not a hardware watchdog replacement
• not a fleet monitoring system
• not validated on every Raspberry Pi OS release
• reboot enablement should follow environment-specific dry-run verification

Verification Plan (Release Gate)

• static checks (ruff, mypy)
• full test suite (pytest -q)
• dry-run + non-dry-run run-once --json on development and Pi Zero deployment targets
• confirm issue template/labels workflows are available for beta feedback routing

---

Full changelog details remain in CHANGELOG.md.