Krzysztof kuhy Rudnicki 5faed23977 security-hardening: recognise the guard-lib shutdown guard ... Test 10 only knew the retired shutdown-schedule-guard.path, so it reported a skip while guard-file@shutdown-schedule.path was actively protecting /etc/shutdown-schedule.conf. That understated the real protection in the same way tests 2, 3 and 5 did before the last commit. It now accepts the guard-lib unit and passes. The disabled-is-intentional branch stays for hosts running neither unit. Host: 19 passed / 0 failed / 5 skipped. Container: exit 0.		2026-07-19 20:09:24 +02:00
..
contracts	Run Arch-only shell tests in a container; harden worktree stubbing	2026-07-19 19:27:36 +02:00
evidence	security-hardening: recognise the guard-lib shutdown guard	2026-07-19 20:09:24 +02:00
memory	style(prettier): apply markdown/json formatting updates	2026-05-07 22:08:00 +02:00
plans	feat(phone-focus): add recovery workflow, automation scripts, and docs	2026-05-01 19:07:27 +02:00
sessions	chore(agent): add governance checks and artifact workflow scaffolding	2026-05-07 22:03:43 +02:00
specs	feat(phone-focus): add recovery workflow, automation scripts, and docs	2026-05-01 19:07:27 +02:00
workflows	chore(agent): add governance checks and artifact workflow scaffolding	2026-05-07 22:03:43 +02:00