v6.7.0: Browser/Edge Read Path

[flyingrobots]

Outcome

Browser and edge read paths are designed and proven enough to know which runtime boundaries are real, which adapters are missing, and what compatibility contract git-cas can honestly claim.

Scope

• Inventory Node-specific read-path assumptions.
• Design browser/edge adapter boundaries.
• Prove at least one focused runtime portability slice before expanding scope.

Required Proof

• Design cycle before implementation.
• Runtime or adapter tests that exercise the actual portability surface.

[flyingrobots]

Roadmap update: this goalpost moves from v6.5.0 to v6.6.0 so the existing roadmap order remains explicit after the emergency scoped-staging-workspace release takes v6.4.0. The implementation scope is unchanged.

[flyingrobots]

This goalpost moves from v6.6.0 to v6.7.0 solely to preserve the established roadmap order after the emergency semver-minor lazy-reference release takes v6.5.0 and the unfinished TUI/agent parity work moves intact to v6.6.0. Scope and acceptance criteria are unchanged.