Skip to content

Expose bounded lanes for step diameter leaders (#2211) - #2224

Merged
pzfreo merged 5 commits into
fix/2211-od-lanefrom
fix/2211-step-diameter-lane
Oct 7, 2026
Merged

pzfreo merged 5 commits into
fix/2211-od-lanefrom
fix/2211-step-diameter-lane

Conversation

@pzfreo

@pzfreo pzfreo commented Oct 7, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Expose exact step.diameter lane controls for X/Z profile and Y end-on step leaders, with no change to no-override placements.
  • Submit only the requested witness-relative rank to the shared measured leader solve; preserve stable names, measurement provenance, and Y-axis diameter coverage.
  • Report an infeasible requested rank as placement_unsatisfiable with measurement evidence instead of silently choosing another lane.

Local checks

  • Focused X/Y/Z lane, mixed-diameter, and explicit drop-evidence cases pass.
  • Existing diameter and lane regression slice passed (39 tests) before the final Y coverage-marker addition; the targeted Y coverage case passed after it.
  • Ruff and full mypy pass; MkDocs strict build passes.
  • A redundant broad local slice was stopped after 37 passes and no failures at 3.5 minutes to avoid waiting on its slow tail; required CI remains the merge gate.

Stacked on #2223. Resolves the step-diameter lane slice of #2211; the issue stays open for remaining callout-side controls and stack verification.

@pzfreo
pzfreo force-pushed the fix/2211-step-diameter-lane branch from beefd97 to 300a81a Compare October 7, 2026 03:51
@pzfreo
pzfreo added this pull request to stack #2229 October 7, 2026 03:52
@pzfreo
pzfreo merged commit 82f97e5 into main Oct 7, 2026
38 of 48 checks passed
@pzfreo
pzfreo deleted the fix/2211-step-diameter-lane branch October 7, 2026 05:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant