Skip to content

feat(processor): optimize coordination and adopt Blue Language rc16#11

Merged
piotr-blue merged 2 commits into
nextfrom
feature/language-rc16-coordination-adoption
Jul 21, 2026
Merged

feat(processor): optimize coordination and adopt Blue Language rc16#11
piotr-blue merged 2 commits into
nextfrom
feature/language-rc16-coordination-adoption

Conversation

@piotr-blue

Copy link
Copy Markdown
Contributor

Summary

  • optimize sequential workflow and Compute execution with bounded plan caches, immutable execution state, and frozen patch handoff
  • adopt blue.language:blue-language-java:3.1.0-rc.16 from Maven Central
  • remove local Language dependency overrides and unrelated external-consumer wiring
  • add deterministic metrics, differential, fixture, memory, binary-compatibility, and Java 8 bytecode verification
  • harden the build for Gradle 10 and reproducible source/publication artifacts

Verification

All project-local checks pass:

  • main suite: 368 tests, 0 failures
  • workflow-plan differential suite: 124 tests, 0 failures
  • complex-fixture integration suite: 55 tests, 0 failures
  • memory integration suite: 17 tests, 0 failures
  • metrics artifact suite: 1 test, 0 failures
  • binary compatibility: 26/26 public API classes
  • Java 8 bytecode: 84 classes, maximum major version 52
  • Maven staging and JMH compilation passed
  • metrics, POM, and source archive are reproducible byte-for-byte
  • published POM contains Blue Language 3.1.0-rc.16 with compile scope

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.
@cursor

cursor Bot commented Jul 21, 2026

Copy link
Copy Markdown

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.

@piotr-blue
piotr-blue merged commit 2fbf9ec into next Jul 21, 2026
1 check failed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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());

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Comment thread README.md

dependencies {
implementation "blue.coordination:blue-coordination-java:1.0.0"
implementation "blue.coordination:blue-coordination-java:2.0.0-rc.4"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

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