Skip to content

Roadmap: unify NodeBridge + OptimizedNodeBridge under shared core #126

@bbopen

Description

@bbopen

Goal

Converge NodeBridge and OptimizedNodeBridge into a single shared implementation with consistent protocol guardrails, error classification, and lifecycle behavior. NodeBridge should remain the correctness-first default while performance features are opt-in.

Design / ADR

  • docs/adr/0001-unified-bridge-core.md

Why

  • Avoid duplicated JSONL parsing/timeout logic and inconsistent edge-case handling.
  • Make OptimizedNodeBridge a strict superset (pooling/caching optional) rather than a divergent path.

Acceptance criteria

  • Extract a shared transport core (JSONL framing, protocol validation, error mapping, buffer limits, timeout handling).
  • Preserve NodeBridge semantics as the baseline (minProcesses=1, caching off).
  • Make performance features opt-in and documented.
  • Add parity tests that run both modes against the same fixtures.
  • Close the linked issues (see below).

Linked issues to close

Metadata

Metadata

Assignees

Labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions