CLI/MCP: serialize TemporalPlan schedules (start, duration, end, makespan)#123
Merged
Conversation
plan_dict now detects a TemporalPlan and emits per-step start, duration and end plus a top-level makespan (cost kept for compatibility). Covers both the CLI and the MCP solve tool, which share serialize.py. Documented in the README CLI section and the object-model temporal section. Fixes #119 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Renders
TemporalPlanschedules in the JSON emitted bypddlpy solve --planner temporaland the MCPsolvetool: per-stepstart/duration/endplus a top-levelmakespan.Why
Found in the v1.2.0 post-release check (#119): the temporal planner computes a full schedule, but the generic
plan_dictrendering dropped it — steps showed only{action, args}and the makespan hid in the genericcostfield.Changes
pddlpy/serialize.py:plan_dictdetects aTemporalPlanand emits{action, args, start, duration, end}per step and a top-levelmakespan(costkept for compatibility). Covers CLI and MCP for free since both go throughserialize.py.tests/test_cli.pyandtests/test_mcpserver.py(100% coverage held, 234 tests).temporalamong the accepted planners);docs/object-model.mdtemporal section notes the JSON rendering.Fixes #119
🤖 Generated with Claude Code