Skip to content

chore: adopt Planner CandidatePostASAPDAGs API - #812

Open
zzylol wants to merge 1 commit into
fix/placement-pricing-evidencefrom
refactor/candidate-post-asap-api
Open

zzylol wants to merge 1 commit into
fix/placement-pricing-evidencefrom
refactor/candidate-post-asap-api

Conversation

@zzylol

@zzylol zzylol commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #809. Uses ProjectASAP/ASAPPlanner#508.

Why

The Planner candidate collection is now named CandidatePostASAPDAGs, matching the architecture terminology.

What

Pin Planner revision ea12b31680be777b1866d3ea5fc82fd4a9a3e57e and update backend comments and documentation. Only Planner revision entries change in Cargo.lock; every dependency version and sketchlib revision is preserved. Backend call sites already infer the collection's type, so no execution code change is needed.

Before this PR

The backend pins the old PlanSpace API.

After this PR

The backend compiles against CandidatePostASAPDAGs with the same search, selection, and runtime behavior.

Validation

Formatting, whitespace checks, workspace all-target Clippy with warnings denied, and the complete control-plane test suite passed against the exact renamed API revision. Planner workspace tests also passed; its Rust diff is naming and formatting only.

🤖 Generated with Claude Code

Pin the public candidate-collection rename and update terminology. Preserve dependency versions and sketchlib revisions; backend calls already infer the renamed return type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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