docs(runbook): packing recipe matches design §4 E (maintenance window, readlink current per removal) #127
No reviewers
Labels
No labels
severity/s2
severity/s3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
janpeter/scrum4me-docker!127
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/runbook-inpakrecept-4e"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #126 (T-136, scrum4me-server ST-037). Doc only.
The
s4m-codex-reviewerreview of #126 (REQUEST_CHANGES, merged before it was resolved) found that the packing recipe in runbook §9 lacks two conditions of the pinned design2026-09-28-compose-kopieen-structureel-design.md§4 E (scrum4me-server):readlink current(When2Watch) again, and stop if the path has meanwhile become a registered config file or a file undercurrent. The runbook only rechecked the sha256 anddocker compose ls --all. A release can becomecurrentafter step 2 without its sha256 or Compose registration changing, so step 5 could have removed an activecompose.yaml.The wording now follows §4 E. Nothing else changes.
🤖 Generated with Claude Code