fix(ci): telemetry switch trivially satisfied without the row; coverage-lane test fixes

A custom profile that mounts no telemetry-otel row exports nothing, so
DSH_TELEMETRY_DISABLED must not fail its boot (CI exports the switch
globally, which broke the lifecycle-fixture profile). The web-app dist
resolution test accepts the fail-loud unbuilt outcome the CI coverage lane
sees before any build, and the headless spec covers the idle-anchor and
pre-start skip branches under the per-file gate.

apps/cli/tests/telemetry-switch.spec.ts

@@ -13,11 +13,10 @@ describe('resolveTelemetryPatch', () => {
     }
   })
 
-  it('fails loud when the switch is set but the row is absent', () => {
-    expect(() => resolveTelemetryPatch('1', false)).toThrow('DSH_TELEMETRY_DISABLED is set but row "telemetry-otel" is not in this composition')
-  })
-
-  it('ignores a missing row while the switch is unset', () => {
+  it('is trivially satisfied by a composition without the telemetry row', () => {
+    // A custom profile need not mount telemetry: nothing exports, so the
+    // privacy switch has nothing to disable and generates no patch.
+    expect(resolveTelemetryPatch('1', false)).toBeUndefined()
     expect(resolveTelemetryPatch(undefined, false)).toBeUndefined()
   })
 })