Location
docs/differences.md, section C: "Known gaps, not deliberate, recorded until corrected"
Problem
Section C currently says that no accidental compatibility gap is known. That statement becomes incorrect once the confirmed v0.4.3 conformance defects are accepted and tracked.
The section should identify only measured mismatches that have no decision record and are expected to disappear. It must not classify unresolved policy questions such as disconnect(true), payload serialization, package entry points, or the observable Adapter surface as accidental defects before those decisions are made.
Suggested wording
Replace the empty-state paragraph with a concise list of the accepted correction issues:
Each entry should link to its issue and describe only the user-observable mismatch. When a correction lands, remove its entry in the same pull request and link the resulting dual-run case from docs/conformance.md where appropriate.
Keep decision-dependent findings out of section C until the project decides whether each one is a correction, an intentional divergence, or deferred surface. Do not include internal planning dates or review notes.
Location
docs/differences.md, section C: "Known gaps, not deliberate, recorded until corrected"Problem
Section C currently says that no accidental compatibility gap is known. That statement becomes incorrect once the confirmed
v0.4.3conformance defects are accepted and tracked.The section should identify only measured mismatches that have no decision record and are expected to disappear. It must not classify unresolved policy questions such as
disconnect(true), payload serialization, package entry points, or the observable Adapter surface as accidental defects before those decisions are made.Suggested wording
Replace the empty-state paragraph with a concise list of the accepted correction issues:
use,connect, anddisconnect.Each entry should link to its issue and describe only the user-observable mismatch. When a correction lands, remove its entry in the same pull request and link the resulting dual-run case from
docs/conformance.mdwhere appropriate.Keep decision-dependent findings out of section C until the project decides whether each one is a correction, an intentional divergence, or deferred surface. Do not include internal planning dates or review notes.