The integrated benchmark previously exceeded its unchanged 300-second timeout. Reduce candidate-scoring and allocation work so the complete seven-scenario protocol finishes in 298.551 seconds locally, then restore benchmark success as a requirement for image publication and the aggregate CI check.
Evaluate objectives lazily in priority order, reuse calendar geometry and working-day prefixes, and share existing placements during assignments while detaching mutable metadata. Preserve search breadth, rule order, earned-entitlement chronology, outcomes, explanations and deterministic tie-breaks. Benchmark inputs, assertions, warm-ups, repetitions and resource limits remain unchanged.
Validation:
Required benchmark: exit 0 with all seven warm-ups and 14 measured runs; 2048 MiB heap, no coverage, 300-second timeout.
633 functional tests with coverage; application/spec type checks, lint, formatting, CI policy/image tests and production build pass.
Complete baseline comparisons match for all seven scenarios and 182 configuration cases; three permanent regression cases pin objective vectors and provenance.
Native-worker browser completion, input editing, heartbeats and keyboard cancellation checks pass. Independent Standards and Spec reviews found no findings.
Evidence and reproduction: docs/benchmark/issue-78.md, including all 14 protocol rows. The local timeout margin is only 1.449 seconds; live CI and security scans are unverified. No physical-phone run was available, and calendar rendering can pause the main thread for about two seconds.
Refs #78. The related verification issue #77 / PR #273 remains open; this PR does not close either issue or change the #268 activation gate.
The integrated benchmark previously exceeded its unchanged 300-second timeout. Reduce candidate-scoring and allocation work so the complete seven-scenario protocol finishes in 298.551 seconds locally, then restore benchmark success as a requirement for image publication and the aggregate CI check.
Evaluate objectives lazily in priority order, reuse calendar geometry and working-day prefixes, and share existing placements during assignments while detaching mutable metadata. Preserve search breadth, rule order, earned-entitlement chronology, outcomes, explanations and deterministic tie-breaks. Benchmark inputs, assertions, warm-ups, repetitions and resource limits remain unchanged.
Validation:
- Required benchmark: exit 0 with all seven warm-ups and 14 measured runs; 2048 MiB heap, no coverage, 300-second timeout.
- 633 functional tests with coverage; application/spec type checks, lint, formatting, CI policy/image tests and production build pass.
- Complete baseline comparisons match for all seven scenarios and 182 configuration cases; three permanent regression cases pin objective vectors and provenance.
- Native-worker browser completion, input editing, heartbeats and keyboard cancellation checks pass. Independent Standards and Spec reviews found no findings.
Evidence and reproduction: [docs/benchmark/issue-78.md](https://gitea.nessar.fr/nessar/vac-optimizer/src/commit/859a5f11052a8e2d71321b1a685177b7f44588b3/docs/benchmark/issue-78.md), including all 14 protocol rows. The local timeout margin is only 1.449 seconds; live CI and security scans are unverified. No physical-phone run was available, and calendar rendering can pause the main thread for about two seconds.
Refs #78. The related verification issue #77 / PR #273 remains open; this PR does not close either issue or change the #268 activation gate.
Reduce objective evaluation and calendar allocation work while preserving planner outcomes and deterministic explanations. Restore required benchmark gating and record the unchanged protocol, differential checks, and browser evidence for #78.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The integrated benchmark previously exceeded its unchanged 300-second timeout. Reduce candidate-scoring and allocation work so the complete seven-scenario protocol finishes in 298.551 seconds locally, then restore benchmark success as a requirement for image publication and the aggregate CI check.
Evaluate objectives lazily in priority order, reuse calendar geometry and working-day prefixes, and share existing placements during assignments while detaching mutable metadata. Preserve search breadth, rule order, earned-entitlement chronology, outcomes, explanations and deterministic tie-breaks. Benchmark inputs, assertions, warm-ups, repetitions and resource limits remain unchanged.
Validation:
Evidence and reproduction: docs/benchmark/issue-78.md, including all 14 protocol rows. The local timeout margin is only 1.449 seconds; live CI and security scans are unverified. No physical-phone run was available, and calendar rendering can pause the main thread for about two seconds.
Refs #78. The related verification issue #77 / PR #273 remains open; this PR does not close either issue or change the #268 activation gate.
859a5f1105tocbde23f572View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.