Remove the automation-launch section from the user docs; phase 4b app half done

The -phyphoxUrl / adb launch instructions were aimed at test automation,
not at the teachers the transferring-experiments page is written for -
removed at the maintainer's request (the seam remains documented in the
app source and the local test plan).

Roadmap and corpus README updated: both app suites now run the corpus on
every commit with T0 CI, so 4b's app half is done; the editor wiring
stays deferred. Verified on hardware today: contract test fully green,
39 probes against Pixel 9 Pro and iPhone, including the ten /set probes
and the repaired /meta.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: Staacks

CLAUDE.md

@@ -396,6 +396,8 @@ file-format page — the mechanism was there, the markers were never placed by h
 This repo was phase 1 of a larger plan recorded in `../CLAUDE.md`. Phase 2 (the OpenAPI description
 of the REST API) and phase 3 (the format spec, and the reference pages generated from it) are done.
 Phase 4a (the generated validators — RELAX NG and Schematron, published with the site and
-proven against the corpus on every build) is done. What is left is phase 4b — the conformance
-corpus run by the implementations' own test suites — and phase 5, making the Blockly editor
-consume the spec instead of encoding the format a fifth time.
+proven against the corpus on every build) is done, and so is phase 4b's app half (2026-08-24):
+both apps run the corpus in their own test suites with T0 CI, kept in step by `test-matrix.yml`
+and its checker. What is left of 4b is wiring the corpus into the editor test suite (deferred
+until the editor is picked up again), and phase 5, making the Blockly editor consume the spec
+instead of encoding the format a fifth time.

corpus/README.md

@@ -2,9 +2,10 @@
 
 Real and generated `.phyphox` files that, together with the shipped experiment
 collection, exercise **every element and attribute the format specification
-models** (`spec/*.yml`). This is the seed of the phase 4 conformance corpus:
-files the app and editor test suites can parse to catch regressions in the
-format surface that the shipped experiments alone never touch.
+models** (`spec/*.yml`). Both app test suites run this corpus on every commit
+(see "The app test suites" below) to catch regressions in the format surface
+that the shipped experiments alone never touch; wiring it into the editor
+test suite as well is planned.
 
 - `valid/` — files collected from real use: test files built during feature
   development, collaboration and support-request experiments, and student

docs/transferring-experiments.md

@@ -45,18 +45,6 @@ phyphox://asset=bluetooth%2Fphyphox_m_bmp581.phyphox
 
 This is meant for links in worksheets, documentation and classroom materials that should land the user directly in the right bundled experiment, and it is what automated testing uses to drive the app. It is deliberately limited to the bundled collection: experiment titles are not unique, and files elsewhere on the device keep going through the regular file-opening routes. An unknown path shows the app's normal "could not load" message.
 
-#### Launching from automation
-
-Scripted testing needs to open such a URL without anyone tapping a dialog, and the two platforms get there differently — deliberately, so do not look for the missing half:
-
-- **Android needs no special mechanism.** `adb shell am start -a android.intent.action.VIEW -d "phyphox://asset=accelerometer.phyphox"` delivers the URL to the app without any confirmation dialog.
-- **iOS confirms opening a URL from `simctl openurl` with a system dialog that cannot be suppressed**, so the app instead accepts the URL as a launch argument: `-phyphoxUrl <url>` behaves exactly as if the URL had been opened from outside the app, and goes through the same handler, so the semantics cannot drift (AppDelegate.swift).
-
-```
-xcrun simctl launch <udid> de.rwth-aachen.physics.phyphox -phyphoxUrl "phyphox://asset=accelerometer.phyphox"
-xcrun devicectl device process launch --device <udid> de.rwth-aachen.physics.phyphox -phyphoxUrl "phyphox://asset=accelerometer.phyphox"
-```
-
 ### Online QR-Codes (recommended)
 
 If your audience has internet access, this is the recommended method and the QR code can be created directly from our editor. This method is very similar to the phyphox:// URL, but the URL is encoded into a QR code, which can simply be scanned from the phyphox main menu. If you want to or need to create the QR code yourself, simply create a QR-Code that contains a link starting with phyphox://, <http://> or <https://> and phyphox should simply download the experiment after scanning the QR code.