mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
c9d8e85567
The role README claimed the backup machinery "operates transparently against the mount paths" and demoted the source-of-truth rule to advice in a prose box - both written before 2efc73d3b made that rule the code's behaviour. It now states what is enforced: this role skips export-backed volumes, svc-bkp-nfs-2-local is their single capture, and manager-pinned roles, roles forcing another compose_mode_force and nfs: false opt-outs stay covered here. It also names the limit the code actually has - the exclusion checks that some host is in the svc-bkp-nfs-2-local inventory group, not that the role ever ran successfully - because a README promising more than the code delivers is worse than one promising less. Its Schema section carried the role's timer flow; it now carries the mechanism the change set is about: meta/volumes.yml -> swarm_nfs_backed() as the single predicate -> its two consumers (the compose rewrite and the backup exclusion) -> the inventory-group gate -> the export host's single capture -> the restore path with its mountpoint probe -> the drill's [3b] guard against over-exclusion. The two swarm READMEs drew the drill with eight steps and pre-773a25ab6 semantics. Both now draw the nine that exist, including what makes the proof a proof: the pulled tree is wiped before the device recover, so the device holds the only copy left; the live export is wiped with the marker proven gone before it is restored; and [9] deletes the marker server-side before restoring the volume through its bound backing store. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Script Collection
This directory contains automation scripts used across the project.
-
system/ contains host and system-facing helpers.
-
container/ contains helpers that run inside the local container.
-
github/ contains GitHub workflow helper scripts.
-
For the canonical Make target index, see make.md.
-
🛠️ Organize operational helpers for development, CI, release, and maintenance
-
🧭 Separate responsibilities into focused subdirectories with clear scope
-
📚 Keep script-based workflows discoverable and easier to navigate
The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.