feat(processor): optimize coordination and adopt Blue Language rc16#11
Conversation
Introduce `AllTimelinesChannelProcessor` for handling shared operations across timelines and `ChatWorkflowOperationProcessor` for streamlined chat workflows. Include comprehensive tests for validating processor functionality and update README with relevant details.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce888965e2
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| // Compatibility-only boundary for callers that compiled the | ||
| // workflow graph in resolved construction mode. Preserve the | ||
| // exact visible authored shape and pay this conversion once. | ||
| value = FrozenNode.fromNode(value.toNode()); |
There was a problem hiding this comment.
Preserve authored overlays for resolved static patches
When a static Update Document step is inherited/resolved, properties.get("val") can be a non-strict resolved FrozenNode whose toNode() includes fields or metadata inherited from the patch-entry/value type. The previous frozen changeset path minimized non-strict items before building the patch, but this new static-plan path freezes value.toNode() directly, so inherited static patches can write resolved-only content or fail canonicalization instead of applying the authored overlay. Reuse the merge-reversal/minimization step before caching the template.
Useful? React with 👍 / 👎.
|
|
||
| dependencies { | ||
| implementation "blue.coordination:blue-coordination-java:1.0.0" | ||
| implementation "blue.coordination:blue-coordination-java:2.0.0-rc.4" |
There was a problem hiding this comment.
Advertise the rc5 artifact in install instructions
For users copying the Gradle snippet after this change, this coordinate still points at 2.0.0-rc.4 even though the project metadata in .cz.toml is 2.0.0-rc.5 and the rest of this commit documents the new rc16-based artifact. That makes the README install instructions pull the previous release rather than the artifact containing these fixes and dependency upgrades.
Useful? React with 👍 / 👎.
Summary
blue.language:blue-language-java:3.1.0-rc.16from Maven CentralVerification
All project-local checks pass:
3.1.0-rc.16with compile scope