chore: super-productivity runner scaffolding + asserting-journey boot RED found

Added executeAngularSuperProductivityWitnessRun + SUPER_PRODUCTIVITY_
MUTATION_SEAM (dialog-create-project, verified unique in dist-25's
main.389e30ec). Migrated dist-25 binding re-verified (62 files,
inventorySha256 2bfa70b9). THE FINDING: the asserting witness journey
RED-fails at boot — pins taskLists=2 but the live DOM renders exactly
1 task-list throughout on BOTH lanes (the done-tasks list only exists
with completed tasks, which the journey never creates). The 'five legs
green' claims came from the CALIBRATION driver, not the asserting
journey — so the JOURNEY pins need validation against a real asserting
run. taskLists→1 correction + full asserting re-drive is the next unit
before publish. tsc/lint/tests green.

Author: thejackshelton

packages/cli/src/witness/real-app-run.ts

@@ -6584,6 +6584,39 @@ export async function executeAngularFactoriolabWitnessRun(options: {
 	});
 }
 
+/**
+ * The byte mutation seam for the Super Productivity migrated lane.
+ *
+ * It is the Ivy component selector of the create-project dialog — the very
+ * control leg (d) drives — emitted exactly once across the served bundle, in the
+ * one module that carries the compiled component definition. The journey opens
+ * that dialog and asserts a single `dialog-create-project` host element renders;
+ * overwriting the selector in place renames the host tag, so the assertion
+ * observes zero and the run is red with a message that names the seam, and the
+ * uniqueness demanded by the corpus discipline means no second copy elsewhere in
+ * the bundle can absorb the overwrite.
+ */
+export const SUPER_PRODUCTIVITY_MUTATION_SEAM = 'dialog-create-project' as const;
+
+/**
+ * Super Productivity ships and registers a real ngsw in both lanes, so the run
+ * uses the default (canonical) service-worker policy: the browser context allows
+ * the registration the application's own root module makes, and the journey
+ * measures the worker that succeeds at its three checkpoints rather than an
+ * absence.
+ */
+export async function executeAngularSuperProductivityWitnessRun(options: {
+	lane: Lane;
+	pass: 1 | 2;
+	laneRoot: string;
+	receiptRoot: string;
+}): Promise<WitnessRealAppRun> {
+	const app = apps.find((candidate) => candidate.app === ANGULAR_SUPER_PRODUCTIVITY_APP);
+	if (app === undefined)
+		throw new Error('Super Productivity Witness specification is absent');
+	return await executeRun(app, options.lane, options.pass, options);
+}
+
 /**
  * The jira-clone Witness specification, reachable so its declared inventories,
  * probes and seams can be checked against the receipt schema that enforces them