Going back to the inline-in-reactor shape: hardening directives land in ckn-bw's systemd_units reactor as shared Python dicts (HARDENING_COMMON + HARDENING_SERVER + HARDENING_WEB), spread into each unit's Service block. Educational reference units in deploy/files/.../*.service stay and get per-directive comments. Operator discipline hand-syncs the reference to the reactor; no CI drift test. The broader responsibility reshape — hardening drop-ins living in left4me with ckn-bw as a thin file-shipper — is worth pursuing as a separate dedicated session, not bundled into this refactor. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| plans | ||
| specs | ||