Skip to content

Event streaming, telemetry lineage and app log context - v4.12.0 milestone - #90

Merged
acn-ericlaw merged 1 commit into
mainfrom
feature/progressive-rendering-v4.12.0
Aug 30, 2026
Merged

Event streaming, telemetry lineage and app log context - v4.12.0 milestone#90
acn-ericlaw merged 1 commit into
mainfrom
feature/progressive-rendering-v4.12.0

Conversation

@acn-ericlaw

Copy link
Copy Markdown
Contributor

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.

  • Event streaming (the engines' exact contract): interceptor functions
    with EventStreamWriter, the streaming /api/event host speaking the
    hybrid envelope-mode SSE dialect with the pinned 406/503/408 degradations,
    PostOffice.stream() (async iterator with conformance guards) and
    streamTo() (the relay composition), on the primitive bus's new reply_to
    mechanism.
  • Telemetry lineage: spans minted per traced execution with the caller's
    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.tracing stdout stream.
  • Business correlation-id continuity: the my_cid tag outbound, the
    my_correlation_id view injected at delivery, runWithTrace() (now
    exported) carrying it for edge callers.
  • Application log context: the packaged default-log-context.yaml,
    resources/app-log-context.yaml override, app.log.context flag, and the
    updateContext() developer API - structured log lines join the trace on
    spanId.
  • The interop test report and the demo app's self-documenting continuity
    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

…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>
@acn-ericlaw
acn-ericlaw merged commit 40a9f8f into main Aug 30, 2026
5 checks passed
@acn-ericlaw
acn-ericlaw deleted the feature/progressive-rendering-v4.12.0 branch August 30, 2026 05:10
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