Propose the Development Plan, and mark the architecture agreed

docs/Development-Plan.md: where the code stands against each section of
docs/Architecture.md, the environment today, how we work (plan-first per
milestone, tests, the Quint model, a bring-up run on this box ending
each phase), and seven phases of milestones from housekeeping to
nisse-ops, each marked pre-approved or needs discussion. Every open
issue is mapped to a milestone or marked superseded; an old-to-new
section table serves the reference update in M0.1.

docs/Architecture.md: status now agreed; D7 regains the browser tool
for the internal test network, left out of the rewrite by mistake.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE

docs/Architecture.md

@@ -1,11 +1,10 @@
 # Nisse — Architecture
 
-**Status: draft for review.** This document is to replace the architecture parts of
-`docs/Architecture-Build-Spec.md`. How and in what order it gets built will go in a
-separate document, `docs/Development-Plan.md`, written once this one is agreed.
-Until then the old spec stays in place, and code comments still cite its section
+**Status: agreed (PR #83).** How and in what order it gets built is in
+`docs/Development-Plan.md`. Until that plan's first milestone retires
+`docs/Architecture-Build-Spec.md`, code comments still cite the old spec's section
 numbers (A1–A18, B, C, F). This document uses different letters (P, L, D, O, X, Q)
-so the two can't be confused while the references are updated.
+so the two can't be confused meanwhile.
 
 This document says what Nisse is, how its parts fit together, and why. It records
 decisions and the reasons for them. It doesn't record status or sequencing.
@@ -788,6 +787,8 @@ milestone's marking.
   opening access later is a firewall change.
 - **Test containers on an internal Docker network with no route out.**
 - **Build storage on a separate mount** from the state volume.
+- **A browser** (a shared Playwright tool, headless) **reaches only the internal
+  test network,** to exercise web apps the agent built and reproduce bugs. No SSO.
 
 ---