Improve dry-run wait-line output readability #50

New issue

Closed

opened 2026-05-12 00:50:53 -04:00 by JackFrostbyte · 0 comments

JackFrostbyte commented

2026-05-12 00:50:53 -04:00

Owner

Context

Dry-run mode is useful for previewing scheduler behavior, but the wait-line output can be noisy/repetitive.

A review suggested collapsing or improving the dry-run wait output so the preview remains readable while still showing timing behavior clearly.

Scope

Review current dry-run output.
Reduce repetitive wait-line noise.
Keep enough timing information to understand scheduler behavior.
Do not change actual runtime scheduling behavior.

Acceptance criteria

Dry-run output is easier to read.
Scheduler event order remains visible.
Wait/delay behavior remains understandable.
Runtime behavior outside dry-run is unchanged.
ruff format passes.
ruff check passes.
Tests pass where applicable.

Branch workflow

Base branch:

develop

Suggested work branch:

fix/issue-50-dry-run-output-readability

Pull request target:

develop

Do not merge directly into main. main should only receive tested release-ready changes from develop.

## Context Dry-run mode is useful for previewing scheduler behavior, but the wait-line output can be noisy/repetitive. A review suggested collapsing or improving the dry-run wait output so the preview remains readable while still showing timing behavior clearly. ## Scope - Review current dry-run output. - Reduce repetitive wait-line noise. - Keep enough timing information to understand scheduler behavior. - Do not change actual runtime scheduling behavior. ## Acceptance criteria - Dry-run output is easier to read. - Scheduler event order remains visible. - Wait/delay behavior remains understandable. - Runtime behavior outside dry-run is unchanged. - `ruff format` passes. - `ruff check` passes. - Tests pass where applicable. ## Branch workflow Base branch: `develop` Suggested work branch: `fix/issue-50-dry-run-output-readability` Pull request target: `develop` Do not merge directly into `main`. `main` should only receive tested release-ready changes from `develop`.

JackFrostbyte added this to the v1.0.1 - Maintenance and startup reliability milestone

2026-05-12 01:01:53 -04:00