Write SCOPE.md, and record that pr-hall-of-helix now exists

SCOPE.md was the register-generated stub. It now names the planes and the
packages behind them, the wire contract as the boundary, and what the
framework deliberately does not own -- the interfaces, the campaigns,
backend authority, and Phase D.

Adds three boundary tests, because most "does this belong in fluid-core?"
arguments reduce to one of them: could the control plane be killed right
now with no runtime effect; does this require the target API to change or
link anything; and would this be here if the Hall of Helix did not exist.

FLUID-WP-0009 T02 moves to progress. pr-hall-of-helix was created and
registered early, because the provisioning work needed a home for the
presence spec. The campaign itself has not moved, which is the part the
"after FT-WP-0001 T12" sequencing was protecting.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1361245@bnt-lap001
Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a

workplans/FLUID-WP-0009-campaign-repos-and-example-separation.md

@@ -67,7 +67,7 @@ consumes one or more `fluid-*` interfaces and owns none of them.
 
 ```task
 id: FLUID-WP-0009-T02
-status: todo
+status: progress
 priority: medium
 state_hub_task_id: "7d40da89-9a4d-5358-ae2b-7a1a1339efff"
 ```
@@ -76,6 +76,20 @@ Create the repository and move the campaign into it, per `FT-WP-0001` T13. The
 split is already written there; this task is the execution and the registration
 with the State Hub under the `infotech` domain.
 
+**Partly done, ahead of the sequencing above (2026-09-04).** The repository
+exists, is registered (domain `infotech`, topic `helix-forge`, prefix
+`PRHOH-WP-`), and carries a grounded `INTENT.md` and `SCOPE.md` plus the declared
+Telegram presence at `presence/telegram.yaml`.
+
+It was created early because provisioning needed somewhere to put the presence
+spec — a bot's name and a channel's title are editorial, and putting them in the
+delivery interface would have cut the seam in the wrong place immediately.
+
+What remains is the part the sequencing was actually protecting: **the campaign
+itself has not moved.** Composition and the review queue still live in
+`fluid-telegram` under `FT-WP-0001` T06/T07, and should stay there until the loop
+has closed once (T12), as `FT-WP-0001` T13 says.
+
 The campaign becomes a consumer of `fluid-telegram` in cohort
 `hall-publishing-jobs`, and runs its own FLUID loop over its own artifacts —
 which composition variant travels — using the per-variant engagement the