Skip to content

test(m3): verify canonical Synexia bootstrap via actual OpenRewrite Java21 SDK - #11

Merged
hsoliwal merged 1 commit into
masterfrom
work/canonical-bootstrap-source-sealed-sdk-20261018
Oct 18, 2026
Merged

hsoliwal merged 1 commit into
masterfrom
work/canonical-bootstrap-source-sealed-sdk-20261018

Conversation

@hsoliwal

Copy link
Copy Markdown
Owner

Shared canonical Synexia bootstrap — read-only public-fork application

Two already-present M3 Maven/OpenRewrite classes are byte-identical to the canonical first-party recipes in hsoliwal/com.synexia#12184:

  • M3BootstrapInventoryRecipe.java: Git blob 8f1018a1bcfa203420253d59a8473ef5a18e19b6
  • M3BootstrapTaskRecipe.java: Git blob cfb9fb8befe2c5ccde5035e96ae7c99b89b5f490

Executable receiving proof

This branch adds a focused Java21 JUnit test that calls actual OpenRewrite Recipe.run on a synthetic Java source including a misleading code-like string literal, and asserts a second complete source fixed point with zero changes. It also executes the real task-crate SHA-256 admission and drift-refusal cases.

The dedicated GitHub Actions workflow compiles/runs this test using the existing .m3/openrewrite-recipes/pom.xml, asserts both original Git blobs, and rejects any changed path outside the test, documentation, and workflow itself.

There are no public product/API/JNI/widget/runtime source modifications. This is an intentionally read-only recipe application and qualification, not a claim that every source-changing recipe is applicable to this fork. The existing target adapter stays in place while reusable recipe semantics remain canonical in Synexia; original upstream licenses and attribution are preserved.

Status at creation: original shared Git blobs verified; exact-head Maven/OpenRewrite SDK CI NOT_YET_PROVEN. Keep DRAFT pending check completion; do not mistake this for an all-fork source-transform proof.

@hsoliwal
hsoliwal marked this pull request as ready for review October 18, 2026 13:11
@hsoliwal
hsoliwal merged commit 82ae111 into master Oct 18, 2026
4 of 6 checks passed
hsoliwal pushed a commit that referenced this pull request Nov 16, 2026
The emulator assumed every character occupies one cell, so Hangul, Han
and Kana text, fullwidth forms and emoji were placed one column short
per character and the screen fell apart as soon as a program laid text
out for a real terminal (line editors, curses UIs, Ink based CLIs).

Add CharWidth, a UAX #11 East Asian Width lookup: Wide and Fullwidth
count as two columns, combining marks and controls as zero, Ambiguous as
one, as UAX #11 recommends outside an East Asian legacy context.

The emulator advances the cursor by that width and stores a NUL filler
in the second cell of a wide character, never splits one across the
right margin and erases the margin cell it leaves unused. Overwriting,
erasing, inserting or deleting either half of a wide character blanks
the whole character, and a count of zero edits nothing. Insert mode
makes room in cells, run by run, on the line the text is written to. A
character beyond the BMP takes two cells and leaves no filler in a
one-column terminal.

The renderer skips the fillers so a fixed width font draws a wide glyph
over both cells, falls back to placing each character at its own cell
when the font does not advance exactly one cell per column, draws a
character beyond the BMP whole and draws the block cursor over both
cells. A partial repaint that starts on the second cell of a wide
character is widened to its first, and copying drops the fillers. A
selection that starts or ends on half of a wide character covers the
whole character, both when copied and when highlighted, and the filler
takes the word boundary status of its character when selecting the word
under the mouse.

Tests cover the width table, placement, the margin, overwriting and
erasing halves, insert and delete, zero counts, the cursor, selection
and word selection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant