docs: freeze the consumed-without-effect set #207

Merged

natsukium merged 2 commits from docs/freeze-consumed-without-effect-183 into main 2026-09-07 23:37:44 +09:00

Conversation 0 Commits 2 Files changed 8 +192 -69

natsukium commented 2026-09-07 23:20:53 +09:00

Owner

Copy link

Fixes #183.

Freezes the set of compatibility shims that consume producer bytes without effect. vt-compliance.md gains a normative "Consumed without effect" table stating, per row, the exact input and the exact reply or no-op — so the stub answers producers branch on (0;0, Ps=0, 0$r) become a published contract rather than an implementation detail. landscape.md gains the admission rule: a new tolerate-row is accepted only beside the supported form it stands next to, with a Revisit trigger.

Doc cascade: docs/reference/protocols/vt-compliance.md (the normative table), docs/reference/protocols/support-matrix.md (rows point at the frozen table), docs/reference/esctest-compatibility.md (rejected cases aligned), docs/explanation/protocols/landscape.md (admission rule + rationale).

Tests: the tolerated inputs that had no pinning test now have one — mouse mode ?9, the tolerated OSC families, and SCS charset selection — so a shim that starts doing something fails a test.

Verified: just check green (fmt, clippy, nextest, deny, proto-compat); reviewed by pi luna + pi sol; docs proofread by Gemini gemini-3.8-flash-high

Deferred

• The XTWINOPS CSI 1-9 t row cites no test ("Pinned by: —") — a bare fall-through with nothing observable to assert beyond "no reply"; the adjacent report-arm test already covers the reply-emitting window ops.
• test: XTWINOPS CSI 1t-9t row is shipped with no pinning test at all — already on the implementer's own deferred list, reasoned as above; a minor test-completeness wish, not a required criterion.

Fixes #183. Freezes the set of compatibility shims that consume producer bytes without effect. `vt-compliance.md` gains a normative "Consumed without effect" table stating, per row, the exact input and the exact reply or no-op — so the stub answers producers branch on (`0;0`, `Ps=0`, `0$r`) become a published contract rather than an implementation detail. `landscape.md` gains the admission rule: a new tolerate-row is accepted only beside the supported form it stands next to, with a Revisit trigger. Doc cascade: `docs/reference/protocols/vt-compliance.md` (the normative table), `docs/reference/protocols/support-matrix.md` (rows point at the frozen table), `docs/reference/esctest-compatibility.md` (rejected cases aligned), `docs/explanation/protocols/landscape.md` (admission rule + rationale). Tests: the tolerated inputs that had no pinning test now have one — mouse mode `?9`, the tolerated OSC families, and SCS charset selection — so a shim that starts doing something fails a test. Verified: just check green (fmt, clippy, nextest, deny, proto-compat); reviewed by pi luna + pi sol; docs proofread by Gemini gemini-3.8-flash-high ## Deferred - The XTWINOPS `CSI 1-9 t` row cites no test ("Pinned by: —") — a bare fall-through with nothing observable to assert beyond "no reply"; the adjacent report-arm test already covers the reply-emitting window ops. - test: XTWINOPS CSI 1t-9t row is shipped with no pinning test at all — already on the implementer's own deferred list, reasoned as above; a minor test-completeness wish, not a required criterion.

natsukium added 2 commits 2026-09-07 23:20:53 +09:00

docs: freeze the consumed-without-effect set ... 8217157c2c

The compatibility shims that swallow producer bytes were reasonable one
at a time but were never a recorded set, so "just ignore it" was the
default an addition could take without a decision. Publish freezes the
stub replies producers branch on, so enumerate them normatively while
removing one is still free, and give the landscape an admission rule so
a future tolerate-row has to name the supported form it stands beside.

Refs #183

grid: pin the tolerated inputs that had no test ... 23e50f22e2

The consumed-without-effect set is normative once published, so every
row needs a test that fails if the shim starts doing something. The
mouse `?9` mode, the tolerated OSC families, and SCS charset selection
had none.

Refs #183

natsukium merged commit 23e50f22e2 into main 2026-09-07 23:37:44 +09:00

natsukium deleted branch docs/freeze-consumed-without-effect-183 2026-09-07 23:37:44 +09:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

priority/P0

Must be resolved before the v0.1.0 tag

  

priority/P1

Must be settled before the first public contract freezes

  

priority/P2

Explicitly deferred until after v0.1.0

  

release/v0.1.0

Work tracked for the first tagged release

  

status/blocked

Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  

status/planned

Triaged with a source-grounded plan and a passed pi review; ready to implement

  

type/bug

Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  

type/design

An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  

type/test-gap

Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  

type/tracker

Parent issue that tracks child work

No labels

priority/P0

priority/P1

priority/P2

release/v0.1.0

status/blocked

status/planned

type/bug

type/design

type/test-gap

type/tracker

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

natsukium/felis!207

No description provided.