docs: record colorimetric color specs as a non-goal #202

Merged

natsukium merged 1 commit from docs/colorimetric-non-goal-182 into main 2026-09-07 22:09:10 +09:00

Conversation 0 Commits 1 Files changed 7 +71 -53

natsukium commented 2026-09-07 21:49:47 +09:00

Owner

Copy link

Fixes #182.

Records the colorimetric-transform deferral as a decided non-goal instead of leaving 21 esctest cases unexplained. rgb: and #hex stay the committed color-spec subset for OSC 4 / 5 / 10-12; the X11 colorimetric spaces (CIELab, CIELuv, CIEXYZ, CIExyY, CIEuvY, TekHVC) and the rgbi: intensity form are refused, leaving the addressed slot unchanged with no reply, and OSC 13-19 remain accepted-and-ignored whatever the spec form.

Doc cascade:

• docs/explanation/non-goals.md — the non-goal entry, pointing at the owning argument.
• docs/explanation/protocols/vt-compliance.md — the rationale and its "Revisit if …" trigger under "Conscious omissions".
• docs/reference/protocols/vt-compliance.md — the normative color-spec subset and the refusal semantics.
• docs/reference/protocols/support-matrix.md — OSC 4 / 5 / 10-12 rows now name the accepted subset.
• docs/reference/esctest-compatibility.md — the 21 cases move from unexplained to non-goal.
• docs/README.md, crates/felis-grid/src/osc_color.rs — pointer and doc-comment mirrors.

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

• #201 test: pin the OSC 4/5 refusal and OSC 13-19 no-op behavior at the dispatch layer

Deferred

• A dispatch-level negative test for a refused colorimetric spec — crates/felis-grid/src/osc_color/tests.rs already asserts the rejection at the parser layer, and the plan explicitly calls for no new tests (raised by the implementer; filed as #201).

Fixes #182. Records the colorimetric-transform deferral as a decided non-goal instead of leaving 21 esctest cases unexplained. `rgb:` and `#hex` stay the committed color-spec subset for `OSC 4 / 5 / 10-12`; the X11 colorimetric spaces (`CIELab`, `CIELuv`, `CIEXYZ`, `CIExyY`, `CIEuvY`, `TekHVC`) and the `rgbi:` intensity form are refused, leaving the addressed slot unchanged with no reply, and `OSC 13-19` remain accepted-and-ignored whatever the spec form. Doc cascade: - `docs/explanation/non-goals.md` — the non-goal entry, pointing at the owning argument. - `docs/explanation/protocols/vt-compliance.md` — the rationale and its "Revisit if …" trigger under "Conscious omissions". - `docs/reference/protocols/vt-compliance.md` — the normative color-spec subset and the refusal semantics. - `docs/reference/protocols/support-matrix.md` — `OSC 4 / 5 / 10-12` rows now name the accepted subset. - `docs/reference/esctest-compatibility.md` — the 21 cases move from unexplained to non-goal. - `docs/README.md`, `crates/felis-grid/src/osc_color.rs` — pointer and doc-comment mirrors. 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 - #201 test: pin the OSC 4/5 refusal and OSC 13-19 no-op behavior at the dispatch layer ## Deferred - A dispatch-level negative test for a refused colorimetric spec — `crates/felis-grid/src/osc_color/tests.rs` already asserts the rejection at the parser layer, and the plan explicitly calls for no new tests (raised by the implementer; filed as #201).

natsukium added 1 commit 2026-09-07 21:49:47 +09:00

docs: record colorimetric color specs as a non-goal ... 5623ae2429

The 21 esctest failures over CIE / RGBI / TekHVC color specs were
labeled "deferred" with only a module path, leaving consumers unable to
tell whether the spaces are coming. They are not: `rgb:` and `#hex` are
the committed subset for the codes felis acts on (OSC 4 / 5 / 10-12;
13-19 are accepted and ignored whatever the spec form), kitty implements
none of the xterm-spelled CIE or TekHVC forms either, and no producer
felis targets emits them, so the cases are xterm's coverage of an xterm
extension rather than a compatibility gap.

Refs #182

natsukium merged commit 7ade5395e2 into main 2026-09-07 22:09:10 +09:00

natsukium deleted branch docs/colorimetric-non-goal-182 2026-09-07 22:09:10 +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!202

No description provided.