Retire the old build spec, and point every reference at the architecture (M0.1)

Development Plan M0.1. Every section reference in code, tests, specs/,
the example config, the tuning guide, and the CLAUDE.md and README files
now cites docs/Architecture.md (P, L, D, O, X, Q) instead of the old
spec's A-H, and docs/Architecture-Build-Spec.md is deleted (git keeps
it). The plan's old-to-new table goes with it.

Mostly mechanical, with a per-site choice where one old section split:
A4 became L2 where it meant stop/abandon/the loop and L3 where it meant
approvals; A10 became L6 in the context-budget code and L7 elsewhere; B2
became D4 for outbound Gitea and publishing and D5 for review intake;
'A3 step N' became the matching step of L8's boot sequence. Comments
describing behaviour the architecture drops (planning always escalating,
thresholds tuned at an old build step) now describe the current code and
point at the Development Plan.

docs/Architecture.md gains one line the rewrite missed: intake outages
delay but never fail work (old B2), now in L5, where the poller and
Matrix code cite it.

Comments and docs only; no behaviour change.

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

nisse-dev/src/nisse_dev/tools.py

@@ -1,11 +1,11 @@
-"""Executor tools (spec A15: reduced schema, flat arguments).
+"""Executor tools (architecture L9: reduced schema, flat arguments).
 
-Deliberately unsandboxed. The VM is the trust boundary (B3) and tool use is
-auto-approved inside an approved unit of work (A4), so per-command
+Deliberately unsandboxed. The VM is the trust boundary (D7) and tool use is
+auto-approved inside an approved unit of work (L3), so per-command
 confinement would add failure modes without adding safety. The workspace is
 where work happens — the default for relative paths and the command cwd — not
 a wall. Protecting agent state from the agent is a mount-layout concern
-(A2/B3), not this module's job.
+(L8/D7), not this module's job.
 
 What *is* enforced here is operational: commands cannot hang the loop, cannot
 consume the context window with megabytes of build log, and do not inherit
@@ -153,7 +153,7 @@ class Workspace:
 
     def write_file(self, path: str, content: str) -> ToolOutcome:
         target = self._resolve(path)
-        # Not a sandbox — the VM is the trust boundary (B3). This is about the
+        # Not a sandbox — the VM is the trust boundary (D7). This is about the
         # work existing at all: a file written outside the repo is invisible
         # to git, so the milestone would publish an empty PR while the model
         # truthfully reports success. Models do guess plausible absolute paths