release: the Plasma classroom becomes stable 0.2.0

0.1.50 was taken to the church and the things a container cannot answer
were answered on the hardware: boot, autologin, the panel after a reboot,
panel and browser scaling, Wonder Ink, Parent Call opening in the corner
and reaching the sanctuary with a typed name, readable and silent
notifications, HDMI audio and the volume keys.

The promotion is a fast-forward. The experiment was cut from the
published stable source and never diverged from it, so master reaches
this work without a merge and there is one history.

One thing changed for the release. The channel rules turn around:
classroom-v2 and hyprland are the obsolete channels now and a room on
either comes home to stable, while canary — where the next development
release goes — and any channel somebody named by hand stay where they
were put. A fresh installation has always defaulted to stable.

Nothing else moved. This is the 0.1.50 that was verified, with a version
number and a channel rule.

Co-Authored-By: Claude Opus 5 <[email protected]>

docs/classroom-v2-experiment.md

@@ -1293,6 +1293,32 @@ survive that — and `lab reboot` is in every scenario. It re-fences now
 and refuses to continue if either church network answers. The four
 retained topics are the user's to clear; the commands are in the report.
 
+## Stable: 0.2.0
+
+The experiment is over. 0.1.50 was taken to the church and everything a
+container could not answer was answered on the hardware: Plasma and KWin
+boot, autologin works, the panel comes back after a reboot, the panel and
+Chrome are the right size, Wonder Ink runs, Parent Call opens in the
+corner, accepts a typed name and reaches the sanctuary, notifications are
+readable and silent, HDMI audio and the volume keys work, and the room
+looks the way it was meant to.
+
+So the Plasma classroom is the stable line, and this branch's work is on
+master. The promotion was a fast-forward: the experiment was cut from the
+published stable source and never diverged from it, so there is one
+history and no merge.
+
+One thing changed for the promotion and nothing else did. The channel
+rules turned around: `classroom-v2` and `hyprland` are the obsolete
+channels now and a room on either comes home to `stable`, while `canary`
+— the next development release's channel — and any channel named by hand
+are left exactly where somebody put them. A fresh installation has always
+defaulted to `stable` and still does.
+
+Publishing followed the existing path: the package goes up through a
+channel publish, and `update_stable.sh` moves the manifest afterwards,
+manifest last.
+
 ## Unresolved risks
 
 In the order I would worry about them.
@@ -1362,13 +1388,14 @@ In the order I would worry about them.
     machine's key, and the control computer cannot reach it either — so
     every result above is the lab's. The package is built and the deploy
     commands are written down; the room itself is unverified.
-16. **The v2 channel still has no manifest.** `update_classroom_v2.sh`
-    exists now and has not been run. Until it is, a v2 room takes no
-    updates at all, and `classroom-migrate` moves every upgraded machine
-    onto that channel — deliberately, because stable and canary would
-    both hand a Plasma room the sway build back.
-17. **Nobody has typed into the anchored Parent Call card.** Layer shell
-    gives it the keyboard — the entry takes focus and shows a caret — but
+16. **The experiment's channel is now the obsolete one.** It carried the
+    rooms while this was an experiment and 0.2.0 brings them home to
+    stable. It is kept, pointed at 0.2.0 so that a machine still on it
+    takes the release that moves it, and the 0.1.50 package stays hosted
+    as the rollback.
+17. **Typing into the anchored Parent Call card was verified at the
+    church, not here.** Layer shell gives it the keyboard — the entry
+    takes focus and shows a caret — but
     keyboard injection has never worked in this lab, so the first thing
     to do on the bench is type a name into it. If it cannot be typed
     into, removing gtk-layer-shell from the package restores the centred