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]>

tests/test-deployment-support.sh

@@ -215,8 +215,10 @@ check("Trixie validation runs before any upload", validation < first_rsync)
 # upgraded room ends on the v2 channel with every setting this release
 # has, exactly once, and the command a technician runs is safe to run on
 # a machine that is already converged.
-check("the gate checks the upgraded channel",
-      "'^CHANNEL=classroom-v2$'" in validation_script)
+check("the gate checks a deliberate channel survives",
+      "'^CHANNEL=canary$'" in validation_script)
+check("and that the experiment's channel comes home",
+      "'^CHANNEL=stable$'" in validation_script)
 check("and that every new setting arrived exactly once",
       "for setting in LIVE_ENABLED AUDIO_OUTPUT UI_SCALE" in validation_script)
 check("and that running the migration by hand is safe",