Skip to content

docs: refresh README for v3.4 orchestration + v3.3 cluster runtime#61

Merged
ZhiXiao-Lin merged 1 commit into
mainfrom
docs/readme-v3.4-v3.3
May 30, 2026
Merged

docs: refresh README for v3.4 orchestration + v3.3 cluster runtime#61
ZhiXiao-Lin merged 1 commit into
mainfrom
docs/readme-v3.4-v3.3

Conversation

@ZhiXiao-Lin
Copy link
Copy Markdown
Contributor

What

Refreshes README.md to match the shipped v3.4.0 (programmable orchestration) and v3.3.0 (cluster-grade runtime) releases, and fixes three factual defects in the existing SDK examples.

Changes

  • What's new — replace the stale What's new in 3.2 / 3.0 block with What's new in 3.4 / 3.3:
    • 3.4: the programmable, deterministic orchestration grammar — AgentStepSpec/StepOutcome contracts over the AgentExecutor seam, execute_steps_parallel / execute_pipeline / execute_steps_parallel_resumable + WorkflowCheckpoint, schema-forced output, and the session.parallel/pipeline/parallelResumable SDK grammar.
    • 3.3: cluster-grade runtime — lifecycle (close/is_closed/list_sessions), identity labels, BudgetGuard, loop checkpoints + resume_run, SessionRetentionLimits, MCP idle disconnect.
    • Older highlights + migration detail deferred to CHANGELOG.

Factual fixes

  • SessionRetentionLimits — both SDKs support it today; replaced the false 'Rust-only / SDK shape lands later' comments with the real shapes (Python retention_limits dict, Node retentionLimits object).
  • Node setBudgetGuard — corrected from the wrong two-positional-arg form to the real single-ctx-object callbacks (camelCase usage keys, optional timeoutMs, fail-closed + must-not-throw notes). The Python example was already correct and is unchanged.

Docs-only; no code changes. Accompanying apps/docs chapters (en + cn) updated separately in the monorepo.

- Replace the stale 'What's new in 3.2/3.0' block with 'What's new in
  3.4/3.3' (programmable orchestration grammar + cluster-grade runtime),
  deferring older notes to CHANGELOG.
- Fix SessionRetentionLimits SDK examples: both SDKs support it today
  (Python retention_limits dict, Node retentionLimits object) — drop the
  false 'Rust-only / SDK shape lands later' claims.
- Fix the Node setBudgetGuard example to the real single-ctx-object
  callback signature (camelCase usage keys, optional timeoutMs, the
  fail-closed + must-not-throw napi notes).
@ZhiXiao-Lin ZhiXiao-Lin merged commit 1d8ba47 into main May 30, 2026
1 check passed
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.

2 participants