Event streaming, telemetry lineage and app log context - v4.12.0 milestone - #90
Merged
Merged
Conversation
…stone The wrapper half of the progressive-rendering program: the multi-shot reply contract and envelope-mode SSE dialect (producer EventStreamWriter + streaming /api/event host + PostOffice.stream/streamTo consumer), the engines' reply_to mechanism on the primitive bus, business correlation-id continuity, full span lineage with the engines' distributed-trace dataset on stdout logs, and the app-log-context feature with the packaged default template. Version aligned with the engine lock-step line at 4.12.0 (npm lineage jumps the legacy 4.3.x). Co-Authored-By: Claude Code <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
The Node.js language pack's half of the progressive-rendering program,
released as v4.12.0 - the version aligns with the Mercury Composable engine
lock-step line, and the npm lineage jumps from the legacy pre-composable 4.3.x
directly to 4.12.0.
with
EventStreamWriter, the streaming/api/eventhost speaking thehybrid envelope-mode SSE dialect with the pinned 406/503/408 degradations,
PostOffice.stream()(async iterator with conformance guards) andstreamTo()(the relay composition), on the primitive bus's new reply_tomechanism.
span as parent; outbound stamps, RPC-tag suppression, segment spans and
sender attribution per the engines' rules; the engines' distributed-trace
dataset emitted on the
distributed.tracingstdout stream.my_cidtag outbound, themy_correlation_idview injected at delivery,runWithTrace()(nowexported) carrying it for edge callers.
default-log-context.yaml,resources/app-log-context.yamloverride,app.log.contextflag, and theupdateContext()developer API - structured log lines join the trace onspanId.echoes.
Why
Same milestone as the Python twin: progressive rendering with the complete
observability story, live-verified against both engines and the Python pack
in the interop report - the foundation for AI SDLC adapters in this runtime.
Verification
tsc clean, node --test 76/76, mkdocs strict clean; live cross-runtime drives
recorded in
docs/test-reports/progressive-rendering-interop.md.🤖 Generated with Claude Code
Co-Authored-By: Claude Code noreply@anthropic.com