CI/CD: compare the runtime figure against the run's own chart count

CI-CD.md

@@ -136,7 +136,7 @@ Not on a schedule: it would spend compute every day on a question that changes r
 | **One cluster per chart** | no reuse. Reuse saves time and changes what the test proves: leftovers of the previous install, a warm image cache, fixtures already applied. "Came up from nothing" is the statement. |
 | **Excluded charts** | dropped through the one parser, `ci/run-install-test.sh --list-excluded`, and listed in the summary **with their justification**, as in the PR pipeline. |
 | **The record** | per chart: outcome, date, runner label, `K3S_IMAGE`, `kubectl` version. Plus a final job with the verdict over the whole matrix. A green run nobody notes is unknown again next time. |
-| **Expected runtime** | **20 charts in 12m41s** (Gitea PR #48, one job, all legs concurrent on one Docker daemon), against 23 charts in the matrix today. Written down so a later deviation is visible as one. The timeout is 30 minutes per leg, in `install-test.yml`, hence identical for both callers. |
+| **Expected runtime** | **20 charts in 12m41s** (Gitea PR #48, one job, all legs concurrent on one Docker daemon). Written down so a later deviation is visible as one; compare it against the chart count the run prints in its own summary — 24 at the time of writing, and one more with every new chart. The timeout is 30 minutes per leg, in `install-test.yml`, hence identical for both callers. |
 
 ## `ci/helm-dependencies.sh` — the step they all share