oxidecomputer / oxidecomputer/prettier-plugin-asciidoc

A reflow join flips the reading of a trailing title or indented line (render-equal, parse-side divergence)

Open
#65 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

conformance mechanism:reflow-join obligation:model-fidelity reflow-hazard
Dominant language
TypeScript
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Found by the #58 reading-invariant design prototype: 6 depth-5 sweep shapes (3x a trailing .T flips from title to text, 3x a trailing indented line flips from literal-paragraph start to paragraph text) where joining two paragraph lines changes our own classifier's reading of the LINE AFTER the join, while the emitted bytes of that line are identical and the oracle renders both sides the same. Example: '* a\n[role]\npara\npara\n[[anc]]\n lit\n' formats to '* a\n[role]\npara para\n[[anc]]\n lit\n'. Render-equality implies our parse of one side diverges from the oracle, so each shape is simultaneously a latent reflow hazard and parse-side divergence evidence; the fix likely rides the #55/#57-family parse work. Mechanism M2 in the reading-invariant ledger (#58).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the #58 reading-invariant design prototype and the #55/#57-family parse work referenced here; inspect the six depth-5 sweep shapes and Mechanism M2 in #58. Reproduce the supplied example and verify that joining lines no longer changes the classifier's reading of the following identical-rendering line.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.