nessar/vac-optimizer

0 Fork 0

feat(planning): follow the indicative wait in calculation progress #304

Open

nessar wants to merge 3 commits from feature/calculation-progress into develop

pull from: feature/calculation-progress

Author	SHA1	Message	Date
nessarandClaude Opus 5.5	f128af68af	feat(planning): warn of an overrun only past the displayed range CI / policy (push) Successful in 8s Details CI / validate (push) Successful in 34s Details CI / build (push) Successful in 38s Details CI / policy (pull_request) Successful in 8s Details CI / benchmark (push) Successful in 1m7s Details CI / validate (pull_request) Successful in 36s Details CI / build (pull_request) Successful in 38s Details CI / test (push) Failing after 2m0s Details CI / benchmark (pull_request) Successful in 58s Details CI / test (pull_request) Failing after 1m50s Details CI / security (push) Successful in 56s Details CI / images (push) Skipped Details CI / required (push) Failing after 1s Details CI / security (pull_request) Successful in 1m41s Details CI / images (pull_request) Skipped Details CI / required (pull_request) Failing after 5s Details The expected wait sits near the middle of recent waits, so about half of all runs pass it. Between the expected wait and the top of the range shown before Calculate, the percentage now holds at 95% with no remaining-time line; "Taking longer than expected" appears and is announced only past that top. Refs #300 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-19 01:12:35 +02:00
nessarandClaude Opus 5.5	c2745ecbd6	feat(planning): follow the indicative wait in calculation progress CI / policy (push) Successful in 22s Details CI / validate (push) Successful in 35s Details CI / build (push) Successful in 21s Details CI / policy (pull_request) Successful in 8s Details CI / validate (pull_request) Successful in 24s Details CI / benchmark (push) Successful in 1m28s Details CI / security (push) Successful in 1m4s Details CI / build (pull_request) Successful in 24s Details CI / test (push) Failing after 2m8s Details CI / images (push) Skipped Details CI / required (push) Failing after 1s Details CI / security (pull_request) Successful in 56s Details CI / benchmark (pull_request) Successful in 1m32s Details CI / test (pull_request) Failing after 1m50s Details CI / images (pull_request) Skipped Details CI / required (pull_request) Failing after 2s Details The overlay percentage now rises linearly to 95% at the expected wait captured at Calculate, holds there, and shows 100% only when the planner completes. Beneath the status, one line names the current planning stage (with the rule name for rule stages) and another shows the approximate remaining time, or "Taking longer than expected" once the wait is exceeded, announced once through the live status. Cancel freezes the percentage and hides both lines. PlanningCalculationService reports the stage and submitted request instead of fixed per-stage percentages; PlanningDurationService owns the wait progress on a 250 ms tick. Closes #300 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-19 01:04:47 +02:00
nessarandClaude Opus 5.5	cfa4328ddb	docs(context): define planning stage and indicative wait Both terms are user-visible in the calculation overlay that #300 revises: the stage line names the planning stage, and the remaining time comes from the indicative wait. Refs #300. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-19 00:26:31 +02:00