Document scheduler phase 1 payload mapping#276
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 901ac6a4c2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | `assignments[].task_id` | `plan.blocks[].task_id` | Same task ID. | | ||
| | `assignments[].slot_index` | `plan.blocks[].slot_index` | Same slot index. | | ||
| | `assignments[].start_time` | `plan.blocks[].start` | External timeline blocks have concrete sequential start times. | | ||
| | `assignments[].duration_hours` | `plan.blocks[].duration_minutes` | Convert minutes to hours. | |
There was a problem hiding this comment.
The output mapping row for assignments[].duration_hours says to “Convert minutes to hours,” but this row maps from HumanCompiler’s hours field to Scheduler’s duration_minutes, so the conversion must be the opposite. If an implementer follows this note literally during integration, block durations will be scaled incorrectly (typically by 60x), which would corrupt exported/translated schedule results.
Useful? React with 👍 / 👎.
1 participant
Summary
Validation