fix: report line-only coverage honestly and tighten Bun test helpers

The generated HTML and Cobertura reports no longer show unmeasured
branch and function coverage as 100%. Poll and waitFor deadlines use
performance.now so frozen dates cannot make them loop forever, the
malformed-configuration test covers undefined again next to the empty
array, compose health checks honor PORT, and the migration spec lists
only what is still open.

Refs #291, #292, #293

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/bun-adoption.md

@@ -41,10 +41,6 @@ start); it is not a result from the live Gitea workflow.
   the live runner. The `images` job still has Alpine's `nodejs` on `PATH` for the
   checkout action, which the project command does not use. These and the Gitea
   activation steps remain unverified until a live pull-request run.
-- **Intermittent spec.** `real planning worker cancellation > preserves balances
-and provenance after a valid checkpoint` failed in one of three full coverage
-  runs on the development laptop (it cancels from a stage's progress callback and
-  asserts that the stage did not complete); the cause is not yet investigated.
 - **ADR 0009** stays `proposed` until the final gate.
 
 ## Problem Statement
@@ -276,23 +272,18 @@ remains proposed; the Status section lists what is implemented.
 The glossary receives no new terms because the choices concern general tooling,
 rather than new leave-planning concepts.
 
-Remaining verification and unresolved requirements:
+Remaining verification (everything else is recorded as verified under Status):
 
-- Angular compilation, test-resource loading, serializers, mocking, isolation,
-  and the existing worker harnesses must work under the native Bun runner.
-- Standalone TypeScript 7 diagnostics must be checked alongside Angular's
-  TypeScript 6 diagnostics; their coexistence is agreed, but project-specific
-  differences have not been measured.
-- Current Istanbul reports include text, HTML, and Cobertura. Native coverage
-  equivalence and report-format support have not been established; accepting a
-  reduced capability or different downstream format has not been agreed.
-- Third-party Gitea checkout and artifact actions may impose their own Node
-  requirement. Identify the actual platform constraint; no exception allowing
-  project commands to fall back to Node has been agreed, and CI infrastructure
-  changes beyond the migration require a separate decision.
-- The exact Bun release and container compatibility remain to be verified.
-  The local installation currently lacks the documented native lint, format,
-  and standalone type-check commands.
+- Native lint and format wait for a stable Bun release that ships `bun lint` and
+  `bun fmt` (#290).
+- Live Gitea validation (#293): the custom job `shell` template, the Bun download
+  in each job, the `images` job with publisher credentials, and the benchmark's
+  timing margin on the runners.
+- The `images` job keeps Alpine's `nodejs` on `PATH` because the checkout action
+  needs it (a runner requirement); project commands do not use it and no Node
+  fallback for them is agreed.
+- `src/test-setup.ts` imports Analog's internal `jitTransform` by path; replace it
+  when Angular or Analog exports a JIT transform.
 
 Research checked on 2026-10-17:
 
@@ -305,8 +296,8 @@ Research checked on 2026-10-17:
 - [Angular build guidance](https://angular.dev/ecosystem/custom-build-pipeline)
   recommends retaining its standard CLI pipeline.
 - [Angular's web request engine](https://angular.dev/api/ssr/AngularAppEngine) and
-  [Bun's HTTP server](https://bun.sh/docs/runtime/http/server) provide the intended
-  server integration contracts; their compatibility here remains untested.
+  [Bun's HTTP server](https://bun.sh/docs/runtime/http/server) describe the original
+  server integration plan, replaced by the `Bun.serve` static server above.
 - [Angular version compatibility](https://angular.dev/reference/versions) and
   [compiler roadmap](https://angular.dev/roadmap) establish the current Angular
   compiler boundary. [Microsoft's coexistence guidance](https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/#typescript-and-embedded-languages)