docs: fold the esctest baseline how-to into its reference page #483

Merged

natsukium merged 1 commit from docs/esctest-baseline-to-reference into main 2026-09-26 12:19:39 +09:00

Conversation 0 Commits 1 Files changed 4 +7 -43

natsukium commented 2026-09-26 11:03:52 +09:00

Owner

Copy link

docs/how-to/ is the user task list; raising PASS_BASELINE is a contributor chore. The reference page already carried the invocation, ESCTEST_INCLUDE and the same-commit rule, so the how-to is deleted and the one missing rule (the raising commit names the behaviors and the newly passing cases) moves to reference/esctest-compatibility.md "Invariant and baseline". The add-escape-sequence skill and docs/README.md follow.

`docs/how-to/` is the user task list; raising `PASS_BASELINE` is a contributor chore. The reference page already carried the invocation, `ESCTEST_INCLUDE` and the same-commit rule, so the how-to is deleted and the one missing rule (the raising commit names the behaviors and the newly passing cases) moves to `reference/esctest-compatibility.md` "Invariant and baseline". The `add-escape-sequence` skill and `docs/README.md` follow.

natsukium added 1 commit 2026-09-26 11:03:52 +09:00

docs: fold the esctest baseline how-to into its reference page ... 90b8fea251

docs/how-to/ is the user's task list, and raising PASS_BASELINE is a
contributor chore, so the page sat among install and tmux guides where
no user needs it. Nearly all of it already lived in
reference/esctest-compatibility.md (the invocation, ESCTEST_INCLUDE,
the same-commit rule); the one thing the reference lacked, what the
raising commit records, moves there, and the add-escape-sequence skill
points at that section.

Assisted-by: Claude Code

natsukium merged commit 1cdec1557e into main 2026-09-26 12:19:39 +09:00

natsukium deleted branch docs/esctest-baseline-to-reference 2026-09-26 12:19:39 +09:00

natsukium referenced this pull request from a commit 2026-09-26 12:19:40 +09:00

docs: fold the esctest baseline how-to into its reference page (#483)

Commenting is not possible because the repository is archived.

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

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!483

No description provided.