#220: protocol of the isolated deployment run #290
No reviewers
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#290
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue-220-isolated-run"
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?
Closes the verification work for #220 (chained on #289 — merge that first, fast-forward-only).
Adds
docs/vs-nfd/97-isolationslauf-protokoll.md: the assessor-facing protocol of the isolated deployment run — full stack ininternal: truenetworks, complete checklist (setup, login, live collaboration, search, upload, all export formats, backup and restore), tcpdump full capture with zero packets leaving the isolated subnets, and the explicit SMTP-without-egress behaviour (outbox-contained failure after 5 retries, instance stays fully functional). The restore finding from the run is #288, fixed in the chained PR and re-verified in the same stack.Also ticks plan checkbox P1-3 and the I-28 open question in
20-massnahmenplan.md, and updates the operations handbook airgap section (#229 feedback loop).Issue #220 will be closed manually after green CI + merge, with the protocol as evidence.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AUtYMxwTCMHG9mVHnwbFg8