# GitLab #55: Garantir l’invariance et la réactivité sous charge

Original: `nessar/vac-optimizer`; GitLab Issue ID 326. Target: [#55](https://gitea.nessar.fr/nessar/vac-optimizer/issues/55).

Author: nessar (GitLab user 8). Created: 2026-08-30T18:20:18.861Z. Last source update: 2026-10-03T14:23:31.543Z.

Source state: closed; discussion locked: False.

This linked record preserves source attribution, timestamps, discussion grouping, review positions and historical diffs. Current Gitea activity is separate from the original source dates. Old CI jobs and their reports are omitted by owner decision.

## Discussions and activity

### Discussion c4ce8b1d9fce7afc1128344d22f13d29c1a62b68

#### Source note 1747 — nessar (GitLab user 8) — 2026-10-02T12:54:24.959343Z

````text
Completion audit — 2026-10-02

Not complete: docs/benchmark/README.md records up to 5,950.9 ms extra main-thread timer delay during loaded trace-artifact delivery. This directly fails the responsive-UI criterion here. Earlier owner exceptions closed #43/#45/#11, not this ticket. Outcome/artifact separation and deterministic benchmarks exist, but slow-consumer deadline invariance, full trace retention beyond ten seconds and failure isolation still need the specified verification.

Evidence: reviewed issue requirements/discussions and f1f0835 (published application source; live main 57a39c81 only adds Renovate configuration). Tested an isolated checkout of the published source: 20 test files, 157/157 tests passed, including the five benchmark scenarios. Local commit 51978f7 and uncommitted edits were inspected separately and are not evidence of published completion.
````

### Discussion 247d24c38af8fb9f0c28c48a2dd59952e2c56ef1

#### Source note 1833 — nessar (GitLab user 8) — 2026-10-02T12:54:51.557037Z

system activity.

````text
mentioned in issue #10
````

### Discussion 4d9c2c87fb7482d13792b160d690bc731f6b6255

#### Source note 1876 — nessar (GitLab user 8) — 2026-10-03T14:23:31.127737Z

````text
Implemented with $luna-verified-implement and independently verified.

Planning work is isolated from trace capture, materialization, and transfer. The outcome and stable explanation are delivered before the complete trace. Worker delivery now keeps at most 16 packets of 64 operations in flight and waits for receiver acknowledgements. Receiver batches yield, release consumed packets, and retain every evaluation. Pending duplicate snapshots coalesce without dropping distinct candidates; failures and stale calculations remain isolated. Benchmark helpers release prior calculation references between runs.

Validation: 201/201 tests across 23 files; application/specification type checks, ESLint, and production build pass. All five scenarios match pre-change outcomes in traced/untraced core comparisons. Three loaded browser repetitions each return the same 144-placement plan and a ready trace containing all 868,919 candidate records. Planning work is 5.81–6.18 seconds, within ten seconds; the full trace arrives 24.09–25.10 seconds after the usable outcome. Maximum extra 50 ms heartbeat delay is 946.8 ms, down from 4.65–5.49 seconds before acknowledged delivery. No browser errors or renderer crashes occurred in the final run.

A separate twelve-balance rendered-calendar run completes full trace navigation and counterfactual comparison without errors (maximum extra heartbeat delay 540.3 ms). Keyboard/focus restoration and responsive widths 375/768/1440 pass. Exact results and limits are recorded in docs/benchmark/README.md (2026-10-03).

These are Chromium desktop measurements with a mobile viewport and 4× CPU throttling, not physical-phone evidence. Complete loaded traces still require substantial memory; production build has two warning-budget notices and stays within hard budgets.

Implementation is in the local working tree based on 0ce33cc9d6fe7381965a9162571abe205d0b7350; no commit or push was requested.
````

### Discussion 34e4c86c56f30bbdde039dbbfdda5a0c8cb01bd9

#### Source note 1886 — nessar (GitLab user 8) — 2026-10-03T14:23:33.275378Z

system activity.

````text
mentioned in issue #46
````

## State event records

- {"close_after_error_tracking_resolve": false, "close_auto_resolve_prometheus_alert": false, "created_at": "2026-10-03T14:23:31.604478+00:00", "epic_id": null, "id": 627, "imported_from": 0, "issue_id": 326, "merge_request_id": null, "namespace_id": 38, "source_commit": null, "source_merge_request_id": null, "state": 2, "user_id": 8}