docs: record stances for the three not-yet protocol rows #197

Merged

natsukium merged 1 commit from docs/protocol-not-yet-trio-181 into main 2026-09-07 21:07:17 +09:00

Conversation 0 Commits 1 Files changed 3 +65 -36

natsukium commented 2026-09-07 20:56:51 +09:00

Owner

Copy link

Fixes #181.

The support matrix carried three ❌ not yet rows with no recorded stance and no
tracking issue. This records a verdict for each before the publish freeze:

• DECCARA / DECRARA — adopt; the rectangle bounds model already serves five
  sequences. Tracked by #188.
• In-band resize notify (?2048) — adopt; the notify carries the size in band
  on the PTY stream, ordered against the input around it. Tracked by #189.
• XTSMGRAPHICS — refuse, for the reason Sixel is refused: it sizes Sixel/ReGIS
  surfaces and color registers felis does not keep, and Kitty graphics needs no
  numeric substitute.

Doc cascade: docs/reference/protocols/support-matrix.md (the rows now cite their
issue or the non-goal), docs/explanation/protocols/landscape.md (the rationale and
the "Revisit if …" triggers), docs/explanation/non-goals.md (the XTSMGRAPHICS
refusal beside Sixel).

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

Follow-ups

• #188 [v0.1/Protocol] Implement DECCARA / DECRARA rectangular attribute ops
• #189 [v0.1/Protocol] Implement in-band resize notify (?2048)

Deferred

• No automated guard for the tracked-issue-per-not-yet-row convention — the issue's
  own Tests section scopes verification to just prose-check and the docs-tree
  guards; a new documentation test asserting every not-yet row links an issue is
  hardening beyond the acceptance criteria, not a defect in this diff.

Fixes #181. The support matrix carried three `❌ not yet` rows with no recorded stance and no tracking issue. This records a verdict for each before the publish freeze: - **DECCARA / DECRARA** — adopt; the rectangle bounds model already serves five sequences. Tracked by #188. - **In-band resize notify (`?2048`)** — adopt; the notify carries the size in band on the PTY stream, ordered against the input around it. Tracked by #189. - **XTSMGRAPHICS** — refuse, for the reason Sixel is refused: it sizes Sixel/ReGIS surfaces and color registers felis does not keep, and Kitty graphics needs no numeric substitute. Doc cascade: `docs/reference/protocols/support-matrix.md` (the rows now cite their issue or the non-goal), `docs/explanation/protocols/landscape.md` (the rationale and the "Revisit if …" triggers), `docs/explanation/non-goals.md` (the XTSMGRAPHICS refusal beside Sixel). 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 ## Follow-ups - #188 [v0.1/Protocol] Implement DECCARA / DECRARA rectangular attribute ops - #189 [v0.1/Protocol] Implement in-band resize notify (?2048) ## Deferred - No automated guard for the tracked-issue-per-not-yet-row convention — the issue's own Tests section scopes verification to `just prose-check` and the docs-tree guards; a new documentation test asserting every not-yet row links an issue is hardening beyond the acceptance criteria, not a defect in this diff.

natsukium added 1 commit 2026-09-07 20:56:51 +09:00

docs: record stances for the three not-yet protocol rows ... 3ef617c845

The support matrix carried three `❌ not yet` rows with no stance anywhere
and no tracking issue, so nothing said whether they were coming or refused.
Before the publish freeze each needs a verdict.

Rectangular attribute ops and `?2048` are adopted: the rectangle bounds
model already serves five sequences, and the resize notify carries the size
in band on the PTY stream, ordered against the input around it, where the
`SIGWINCH` the daemon's resize already raises costs a handler racing that
input and a `TIOCGWINSZ` round-trip. Window-size reporting stays out because
a query any program can pull answers with host pixel extents, where the
notify mode reports the PTY geometry its subscriber already owns and stubs
the pixel axes as `CSI 14 t` does.

XTSMGRAPHICS is refused for the reason Sixel is: it sizes the Sixel and
ReGIS surfaces and color registers felis does not keep. Kitty graphics
offers no numeric substitute, because `a=q` is a capability probe, and it
needs none.

Refs #181

natsukium merged commit c5937a45a4 into main 2026-09-07 21:07:17 +09:00

natsukium deleted branch docs/protocol-not-yet-trio-181 2026-09-07 21:07:17 +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!197

No description provided.