site: cut the template's own labels out of the pages

Point 7 of the page-wording review. The pages no longer show their data
structure as headings, and they no longer explain their own conventions.

- Level 1 is one screen: claim, status badge, three figures, the technology
  row, and one sentence carrying one link. Measured in headless Chrome at
  1440x900: 1404-1845 px tall before, exactly 900 px (no scroll) after, on
  all six area pages.
- DocPage: no kicker line, no visible level label, no "Evidence for this
  page" heading or instruction note, no "Drill-downs" list, no
  "Status <word> - sentence" footer. The artefact table starts at level 2,
  under the heading "Artefacts"; the history timeline is level 2 only.
- Landing page: "Start here" link text gone, "How to read this site" panel
  gone, the footer's status-label explainer gone.
- Content, presentation only, no claim softened: the leading H1 that
  duplicated the page title removed from all 41 documents; level 1 bodies
  reduced to the constraint as ordinary prose plus the way in;
  "**Status: ...**" prefixes removed from the artefact stubs; "## Drill-downs"
  and "## Period and confidence" removed from the level 2 pages, with the
  cross-area links moved into the prose.
- The six level 1 claims are now sentences with a subject, and use commas
  instead of middots. Same facts, no new ones.

Not in this commit: the 35 level 2 and 3 claims still use the compact CV
style. That is a voice decision for Sam, not a wording tidy-up.

make validate: 41 documents, 0 violations. go test ./...: pass.

(cherry picked from commit 03009f80fc7815ad7719412e125df9297a6e653f)

content/platform/l3/platform-backups.md

@@ -14,9 +14,7 @@ last_verified: 2026-10-26
 tags: [platform, backups, restore, artefact]
 ---
 
-# Artefact — Backups and restore runbook
-
-**Status: stub.** Redacted job definitions and the restore runbook land in Phase 7. Passphrase locations and remote paths are removed before publication.
+Redacted job definitions and the restore runbook land in Phase 7. Passphrase locations and remote paths are removed before publication.
 
 ## What the artefact is
 

content/platform/l3/platform-containers.md

@@ -14,9 +14,7 @@ last_verified: 2026-10-26
 tags: [platform, docker, artefact]
 ---
 
-# Artefact — Container inventory
-
-**Status: stub.** A digest of the inventory — grouped by purpose, with addresses removed — lands in Phase 7.
+A digest of the inventory — grouped by purpose, with addresses removed — lands in Phase 7.
 
 ## What the artefact is
 

content/platform/l3/platform-network.md

@@ -14,9 +14,7 @@ last_verified: 2026-10-26
 tags: [platform, networking, security, artefact]
 ---
 
-# Artefact — Network layout and remote access
-
-**Status: stub.** The topology diagram lands in Phase 7 with addresses and hostnames redacted.
+The topology diagram lands in Phase 7 with addresses and hostnames redacted.
 
 ## What the artefact is
 

content/platform/l3/platform-nixos.md

@@ -14,9 +14,7 @@ last_verified: 2026-10-26
 tags: [platform, nixos, artefact]
 ---
 
-# Artefact — Declarative multi-host configuration
-
-**Status: stub.** A redacted excerpt of the configuration tree lands in Phase 7. No hostnames, addresses or keys are published.
+A redacted excerpt of the configuration tree lands in Phase 7. No hostnames, addresses or keys are published.
 
 ## What the artefact is
 

content/platform/l3/platform-signage.md

@@ -14,9 +14,7 @@ last_verified: 2026-10-26
 tags: [platform, signage, hdmi-cec, artefact]
 ---
 
-# Artefact — Signage infrastructure · screens as a managed fleet
-
-**Status: stub.** The CEC command set and a layout diagram land in Phase 7.
+The CEC command set and a layout diagram land in Phase 7.
 
 ## What the artefact is
 

content/platform/l3/platform-tuios-package.md

@@ -14,9 +14,7 @@ last_verified: 2026-10-26
 tags: [platform, nix, packaging, artefact]
 ---
 
-# Artefact — A hand-written Nix package with an exit plan
-
-**Status: stub.** The whole file is short enough to publish verbatim; it lands in Phase 7.
+The whole file is short enough to publish verbatim; it lands in Phase 7.
 
 ## What the artefact is
 

content/platform/platform-estate.md

@@ -14,8 +14,6 @@ last_verified: 2026-10-26
 tags: [platform, devops, nixos, docker, backups, networking]
 ---
 
-# A small estate run to a documented standard
-
 **Capability statement.** Four hosts, fifty or more containers, configuration in version control instead of in a shell history, and one place where traffic enters. The estate is deliberately small because it is run rather than demonstrated.
 
 ## What is actually run
@@ -51,16 +49,3 @@ tags: [platform, devops, nixos, docker, backups, networking]
 - **Self-hosting is a choice with a cost.** Monitoring, backups, ingress and the AI gateway are all operated here, which means the failure modes are also operated here. The mitigation is documentation and measurement, not optimism.
 - **Rejected on purpose.** A long list of tools was evaluated and refused — Airflow for RAM, self-hosted Langfuse for six containers it could not afford, LiteLLM because it would duplicate the existing gateway, and a pile of documentation platforms. "Alternatives considered" is kept because the reasoning is the senior artifact.
 - **Not everything is automated.** Some operations are still a documented command run by a person. The runbook exists precisely because the automations do not cover everything.
-
-## Drill-downs
-
-- [Declarative multi-host configuration](l3/platform-nixos.md) — level 3
-- [A hand-written Nix package with an exit plan](l3/platform-tuios-package.md) — level 3
-- [Container inventory](l3/platform-containers.md) — level 3
-- [Backups and restore runbook](l3/platform-backups.md) — level 3
-- [Network layout and remote access](l3/platform-network.md) — level 3
-- [Signage infrastructure — screens as a managed fleet](l3/platform-signage.md) — level 3
-
-## Period and confidence
-
-`period: 2020–`, anchored on the homelab year in the evidence notes. Confidence is `running`: this is the current estate, verified 2026-10-26.

content/platform/platform-overview.md

@@ -3,7 +3,7 @@ id: platform-overview
 area: platform
 level: 1
 title: "Platform & Infrastructure"
-claim: "Runs a multi-machine NixOS and Proxmox estate — fifty-plus containers · declarative configuration · encrypted backups with a written restore runbook · and public ingress — sized to the hardware rather than the budget."
+claim: "Sam runs a multi-machine NixOS and Proxmox estate sized to the hardware rather than the budget: fifty-plus containers, declarative configuration, encrypted backups with a written restore runbook, and public ingress."
 confidence: running
 period: "2020–"
 tech: [NixOS, Proxmox, Docker, Caddy, Tailscale, Borg, Kopia, AWS S3]
@@ -13,13 +13,4 @@ public: true
 last_verified: 2026-10-26
 tags: [platform, devops, nixos, docker, backups]
 ---
-
-# Platform & Infrastructure
-
-**Claim.** Fifty or more containers on a four-host estate, configuration declared rather than hand-applied, encrypted backups on three machines with a restore runbook beside them, and one public listener at the edge.
-
-**Status.** Running. Figures trace to the approved metric set and the infrastructure reference; verified 2026-10-26.
-
-**The constraint that shaped it.** The runtime host is memory-bound rather than CPU-bound. Every service in this estate carries a memory cap and is bound to loopback, which is why the platform reads as engineering under constraint instead of hardware shopping.
-
-**Start here.** [The capability page](platform-estate.md) covers what runs, where, and what was rejected.
+The runtime host is memory-bound rather than CPU-bound, so every service carries a memory cap and is bound to loopback. What runs, where, and what was rejected is on the [estate page](platform-estate.md).