Restore initialization's issue 003 — the status flip was based on a wrong premise

Init's 003 was already resolved with its own consolidated attribution
(03-DESIGN/01-to-be/08-connectivity.md); the re-homing overwrote it with the
session's ADR-0045 firewall attribution. Init is canonical and the firewall
decision is recorded in the ported ADR 0045 regardless, so 003 is restored
untouched. No initialization record is modified by this reconciliation.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

04-ISSUES/003-firewall-scope-is-read-by-no-code/00-report.md

@@ -1,9 +1,9 @@
 ---
-status: fixed
+status: resolved
 opened: 2026-08-22
-located-in: [mesh-control/internal/catalogue, mesh-catalog/modules/firewall]
-fixed-by: the manifest refuses unknown keys, `from` is the field that scopes a port and it is rendered to nftables, and the firewall module applies it
-amended-design: 0045-a-machine-firewall-is-the-sum-of-what-it-listens-on.md
+located-in: [mesh-control]
+fixed-by: mesh-control — a machine's filtering is computed from what it was assigned
+amended-design: 03-DESIGN/01-to-be/08-connectivity.md
 ---
 
 # 003 — A firewall rule's `scope:` is read by no code