# Distribution decision record

## Published dev.12 (11 October 2026)

[npm `0.1.0-dev.12`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.12), both anonymous registry tags (`latest` and `preview`), and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.12) select frozen source `c17f968c4bc484599e9f50c1becceb4a6d23e1d1`. The annotated tag object is `45c40d3fb019c00184e8f5dafaf7b68e76201fc0`. The retained final archive, anonymous registry download and downloaded GitHub asset agree byte for byte: 421,523 bytes, 52 files, SHA-256 `990e5a067bbe7c270a60cf70e5892bab31d00b8182782ca601da8e75947972ea`, integrity `sha512-DEuorTTicWapv8oNV942huiPB8HMPTehrgsUA0+Cdgy7bUvOKfk7YfNr8pc7G75ezkE4S9C6NzNksNAYRIXXOg==`. Every payload file matches the frozen source/tag. The downloaded GitHub checksum asset also agrees, with SHA-256 `674e3e7c30cde5627d843f70c70e1c24f9c183143a9e9cb4f6b530464d22a2dd`. Initial anonymous version reads return 404 during processing; the upload is not repeated.

This release adds parser/compiler-backed built-in-class and closed-capture-reference completion, a complete selected-rule preview and reproducible Markdown workshop snapshots. Compiler semantics, public API/declarations and runtime dependencies are unchanged. The exact retained final archive passes complete installed JavaScript/strict TypeScript/API/CLI consumers on Node 25.9.0 and Node 22.23.3 without replacement or repacking. The local gate sequence and its targeted screenshot-metadata correction are recorded in [testing](TESTING.md#dev12-candidate-verification-11-october-2026); the separate prototype is not published.

Owner Pages commit `625f696d05cba4c04665577f67445ffd7b411e29` changes 49 files, all inside the existing `Regex-For-Humans/` folder. [Deployment 38176385100](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38176385100) succeeds; all 87 public release files return HTTP 200 and match the validated build byte for byte. Live Chrome desktop/mobile, Firefox desktop and WebKit mobile pass raw draft recovery, nonmutating group previews, applied native spans/captures, closed-capture completion, actual Markdown download/fixture roundtrip and French dark 320px layouts without page errors or document overflow. All four hosted screenshots are visually inspected.

All ten README guides retain 20 identical canonical code blocks and synchronized dev.12 links and real screenshots. Actual GitHub Arabic/Urdu rendering passes in six desktop/mobile views, including intact LTR version labels at 320px; all six captures are visually inspected. The Downloads Reddit draft describes dev.12 and remains unposted. Its original 19-rule example still produces the exact supplied regex and passes two positive/four negative cases against a fresh public npm installation. Subsequent publication receipts are documentation on this frozen runtime and do not replace its archive or tag. Older archives/tags remain immutable, source Actions stays disabled, and independent human reviews and the wider autonomous mission remain open.

## Historical dev.12 candidate (11 October 2026)

The local candidate combines parser/compiler-backed class and closed-capture-reference completion, the full selected-rule preview and reproducible Markdown reports from source milestones `e347aa0`, `3114933` and `9c9beab`. Package/lock metadata selects `0.1.0-dev.12`; public npm tags, the GitHub prerelease and owner Pages remain frozen dev.11. README/homepage source links, feature guides, release notes and refreshed screenshots now target dev.12 for the final archive. These edits prepare delivery; registry/GitHub/Pages verification remains pending.

Local gate sequence is complete after correcting screenshot metadata: Node 25/22 (424 cases each, 420 passes and four existing skips), 726 Chromium, 484 Firefox/WebKit, 64 homepage checks, seven required native profiles (8,782 span/capture comparisons), quality/link checks and zero moderate-level audit findings. The first complete command failed two stale screenshot-reference/dimension checks after its preceding stages passed; the Pages builder now derives PNG metadata and the complete homepage rerun passes. A retained 420,613-byte prototype passes exact-byte clean consumers on both Node editions. It predates final copy/screenshots and must not be published. Final README copy is synchronized; actual GitHub AR/UR rendering passes in six desktop/mobile views, including a complete LTR preview version at 320px. Required next evidence: exact final retained-archive consumers on Node 25/22, source/tag agreement, registry/GitHub byte checks and owner Pages/live verification. No new publication is claimed before those steps. Older archives/tags remain immutable, source Actions stays disabled and independent human reviews remain open.

## Published dev.11 (11 October 2026)

[npm `0.1.0-dev.11`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.11), both registry tags (`latest` and `preview`), and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.11) select frozen source `feff37d69957da31992b46663410522dfab9bd69`. The annotated tag object is `057b6b5dc19bdf94b8d8de700b3bdb7c9e67a5d6`. The retained final archive, anonymous registry download and downloaded GitHub asset agree byte for byte: 408,988 bytes, 50 files, SHA-256 `cfd56bd51ce7d199cba2d6578205eb55c11ef1afbadcecd0ded854a39f635788`, integrity `sha512-JO4zMrrGwWUP0RYe81LxdP1F3LG9s5qisjjAP7uuI1/4SJVrJ74eMUAcAYP5gPSlPdWvspfE2JN/1pocFBenWg==`. Every payload file matches the frozen source/tag. The GitHub checksum asset also agrees, with SHA-256 `74188592b08a99ef24e1b0a6a6b09a6fd1e13f4dd1988b34a9862f1d8c4bcec0`. Initial anonymous registry reads return 404 during processing; the upload is not repeated.

This release adds optional browser draft recovery and validated before/after group-edit comparisons. Compiler semantics, public API/declarations and runtime dependencies are unchanged. The final archive passes complete installed JavaScript/strict TypeScript/API/CLI consumers on Node 25.9.0 and Node 22.23.3. Fresh-cache public default installation on Node 25 and preview installation on Node 22 pass the same checks and enforce installed version dev.11. All seven required foreign profiles pass 8,782 comparisons, including PHP 8.5.11 / PCRE2 10.44. Scoped flags retain their compatible-native-runtime requirement and explicit foreign-profile rejection. See [the testing record](TESTING.md#dev11-candidate-verification-11-october-2026) for the full runtime gate and the separate final-copy checks; the earlier prototype archive remains separate.

Owner Pages commit `f15b89dd94e3aee5d11243aa78d63487456e4486` changes 50 files, all inside the existing `Regex-For-Humans/` folder. [Deployment 38164762629](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38164762629) succeeds; all 83 public release files return HTTP 200 and match the validated build byte for byte. Live Chrome desktop/mobile, Firefox desktop and WebKit mobile verify unfinished draft recovery, unchanged source/regex/saved draft during preview, applied native spans/captures, French dark-theme labels and 320px layouts without page errors or document overflow.

All ten README guides retain 20 identical canonical code blocks and synchronized dev.11 links and real screenshots. Actual GitHub Arabic/Urdu renders at 1,280 and 390 px retain 19 RTL headings, seven RTL tables, 20 LTR blocks and all native-first paragraphs; all four captures are visually inspected. The Downloads Reddit draft describes dev.11 and remains unposted. Its original 19-rule example still produces the exact supplied regex and passes two positive/four negative cases against a fresh public npm installation. Subsequent publication receipts are documentation on this frozen runtime and do not replace its archive or tag. Source Actions remains disabled; independent human language, usability, explanation and screen-reader reviews and the wider autonomous mission remain open.

## Historical dev.11 preparation snapshot (11 October 2026)

The dev.11 candidate combines optional browser draft recovery and validated group-edit previews from source commits `3748f4c` and `4be8b4f`. Package metadata, the ten README guides and homepage version links select dev.11 in the local candidate. Runtime/compiler/public declarations are unchanged. The complete verification stage and separate Node 22 suite pass; all seven required native profiles pass 8,782 comparisons after restoring the retained PHP runtime to the command's PATH. See [the testing receipt](TESTING.md#dev11-candidate-verification-11-october-2026). The prototype archive predates two version-guide edits and the refreshed screenshots/receipts; preserve it separately. Final copy/build/package checks, retained-final-archive consumers, immutable source/tag freeze, npm/GitHub publication and owner Pages/live verification still need their own receipts. Public registry tags and hosted runtime remain dev.10 until those steps succeed; preparing this copy is not publication proof. Older archives stay immutable and source Actions remains disabled.

**Unreleased group previews on main:** the [group comparison workflow](GROUP_PREVIEWS.md) joins draft recovery after dev.10. These workshop-only source changes require their own complete distribution gate before a new npm/site release; dev.10's immutable archive, tag and hosted runtime remain unchanged.

**Unreleased draft recovery on main:** the optional workshop draft workflow described in [the draft contract](TEST_FIXTURES.md#draft-recovery-on-unreleased-main) follows frozen dev.10. All ten source guides distinguish this addition from the published package and site. Its component checks do not replace a complete new distribution gate; preserve dev.10's immutable archive/tag and hosted runtime until the next verified preview.

## Published dev.10 (11 October 2026)

[npm `0.1.0-dev.10`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.10), both registry tags (`latest` and `preview`), and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.10) select frozen source `433e438a92643c313e325421515fb495a1d153e9`. The annotated tag object is `6277c078bb7d0d6b8f4616b3b3a7d5a38b65cc60`. Retained, anonymous registry-downloaded and GitHub-downloaded archives agree byte for byte: 397,286 bytes, 49 files, SHA-256 `8efc5bcc3e202d0969f9f3cc8591a406d728cdcfec66821e2d637a0a05332cca`, integrity `sha512-8Hk3wfTG37BoURkhrb+6oW5pZcGmBPyOcWbdOT15pBeIcWBUdc4K7ewedSD3+zqcQkDU5PAETQI9dHZ6uoUsAg==`. Every payload file matches the tag. The GitHub archive digest agrees; its checksum asset has SHA-256 `38c15cc27df32a5bab96d810ab842f51f7ef2bf13af71b73deeb3ea236991c3e`. Exact-archive consumers pass on Node 25 and Node 22; fresh public default and preview installations pass the complete JavaScript/strict TypeScript/API/CLI consumer checks.

This release adds native scoped i/m/s groups, cached-source runtime protection and the 64-level group-wrapper correction. Scoped groups require a compatible native runtime: tested Node 22 lacks syntax and tested Node 25/26 have measured native behavioral defects, so the feature is refused there. Ordinary supported rules and CLI workflows retain Node 22+ support. Foreign exports reject scoped groups until their semantics are verified.

Owner Pages commit `7245eceae2fddba2ff64cb9a5c3fb1c6808d581c` changes 45 files, all inside the existing `Regex-For-Humans/` folder. [Deployment 38156405794](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38156405794) succeeds; all 81 public files return HTTP 200 and match the validated release build byte for byte. Live Chrome desktop/mobile, Firefox desktop and WebKit mobile checks pass scoped matching, captures, reverse import and cached construction, with no document overflow or page errors. The full candidate command passes; see [the testing record](TESTING.md) for exact counts and runtime boundaries.

All ten guides pin dev.10 and retain 20 identical canonical code blocks. Actual GitHub Arabic/Urdu renders pass desktop/mobile direction checks and visual inspection; an Urdu paragraph was corrected to start with Urdu prose so GitHub's automatic paragraph direction stays RTL. The local Reddit draft now describes dev.10 and remains unposted. Its original 19-rule example still generates the exact supplied regex and passes two positive/four negative cases. Subsequent publication receipts are documentation on this frozen runtime and do not replace its archive or tag. Source Actions remains disabled; independent native-speaker, usability, explanation and screen-reader gates and the wider autonomous mission remain open.

## Historical dev.10 preparation snapshot (11 October 2026)

The isolated candidate starts from source `b321e83`, including native scoped i/m/s groups, the cached-source runtime guard and the 64-level group-wrapper correction. Package metadata, security policy, homepage, language/compatibility guides and all ten READMEs select `0.1.0-dev.10`. All guides retain the canonical code examples; Arabic/Urdu use RTL prose and isolated LTR syntax. Scoped matching remains unavailable on the tested Node 22/25/26 editions and requires a compatible native runtime.

The underlying source passes 401 Node cases on each tested edition (397 passes and four explicit native-scope skips), 16 focused Chrome desktop/mobile and Firefox/WebKit checks, and clean installed JavaScript/strict TypeScript/API/CLI consumers on Node 25 and Node 22. The complete candidate distribution gate, frozen archive, npm upload, GitHub prerelease and hosted Pages verification are still pending. These component receipts are not publication proof.

At preparation, npm authentication is valid and both registry tags select dev.9. The immutable dev.9 archive and hosted runtime remain unchanged. Source Actions stays disabled; independent human review gates and the wider autonomous mission remain open.

## Published dev.9 (11 October 2026)

[npm `0.1.0-dev.9`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.9), both registry tags (`latest` and `preview`), and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.9) select frozen source `7254cf3487e464f227eae540a82437fb47329ae6`. The annotated tag object is `0e55fb2378479600721a727bd96ddf053fa6e75c`. The exact retained archive, public registry download and public GitHub asset agree: 382,895 bytes, 48 files, SHA-256 `564311df082f15cc104ec9b10896e38c7d6bef21887c4ac49257ba4fccf5602c`. Every payload file matches the tagged source; the downloaded checksum asset also matches. Both exact-archive consumers pass on Node 25.9.0 and Node 22.23.3. A fresh public installation reproduces the original 19-rule manifest regex and passes two positive/four negative cases. Initial registry reads returned 404 during propagation; publication was not repeated.

The release contains precise quoted/property/class diagnostic ranges, conservative absolute input-edge failure explanations and complete workshop snapshot sharing. All ten guides retain their 20 equivalent code blocks and current screenshots; actual GitHub Arabic and Urdu previews preserve RTL prose and LTR technical code. The updated English Reddit draft in Downloads describes dev.9, preserves the supplied manifest rules and exact regex, and remains unposted.

Owner Pages commit `670eff8fc94968b03973b432b2b9d76e997e0d68` changes 50 files, all within the existing `Regex-For-Humans/` folder. [Deployment 38142923197](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38142923197) succeeds; all 80 public files return HTTP 200 and match the validated build byte for byte. Publication receipts are subsequent documentation on this frozen runtime and do not replace its archive or tag. See [the testing record](TESTING.md) for complete component results and the unreproduced WebKit failure. Source-repository Actions remains disabled. Independent native-speaker, usability and screen-reader reviews and the wider autonomous mission remain open.

## Historical dev.9 preparation snapshot (11 October 2026)

The isolated dev.9 candidate starts from verified source `14b4e5c`. It adds the subsequent quoted/property/class diagnostic ranges, absolute input-edge failure explanations and complete workshop snapshot links to the distribution. All ten guides describe these workflows and pin dev.9; their 20 canonical code blocks remain identical, with Arabic/Urdu prose RTL and technical code LTR. Initial guide/interface contracts pass all 13 checks, and lint/types/source links pass. Complete release verification, exact retained-archive consumers, source promotion, npm publication, matching tag/Release and Pages synchronization are still pending at this preparation snapshot.

At this preparation snapshot, npm authentication is valid for `othmaneblial` and registry versions end at dev.8. The published runtime and retained dev.8 archive below remain unchanged. Credentials are checked without exposing tokens or requesting verification codes in chat. The complete autonomous mission and independent human review gates remain open.

**Published dev.8 (11 October 2026):** [npm `0.1.0-dev.8`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.8) and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.8) use source `9cc141674ef3f9bd622188153a4b361284d28261`, annotated tag object `83b0af03843c6e186a0cbf4408bca27387217c28`. npm `latest` and `preview` both point to dev.8. The retained, registry-downloaded and GitHub-downloaded archives are identical: 367,873 bytes, 48 files, SHA-256 `26037077091d064ae484c7120c8bdd6fc5240175976a1b309cfe2789e2eac922`, SHA-1 `2a496d23f48ac60633b73427afd0fbd07196756a`, integrity `sha512-uxm0zo/IQcK8N7N8S0rKZPG/gDFGQ94rYq/s08FezvB4Bb5py1thnIjFjyseKD0R/wBw/oaIwiJLDlCD8ZV8ZQ==`. Every payload file matches that source commit, and the GitHub checksum asset matches the retained file. Clean JavaScript/strict TypeScript/API/CLI consumers pass on Node 25.9.0 and Node 22.23.3 using the registry-downloaded archive. Fresh-cache public `@preview` installation and npx report dev.8; the installed compiler reproduces the supplied manifest regex exactly, accepts two valid rows and rejects four malformed variants.

**Hosted dev.8:** owner Pages commit `7912032852c283c36bac03aab76047e345d934d9` changes 48 files, all inside `Regex-For-Humans/`. [Deployment 38130254570](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38130254570) succeeds. All 80 files return HTTP 200 and match the release build byte for byte. That build's tracked source files match `9cc1416`; later publication receipts are a documentation follow-up on the same release runtime. Installed Chrome displays dev.8, selects the complete invalid `-12` token through error navigation, and compiles a comment plus a named capture/backreference with a successful native `nightly/nightly` match. All ten README guides pin dev.8 and retain 20 identical canonical code blocks; Arabic and Urdu retain RTL prose and LTR code. The Downloads Reddit draft describes the published release, preserves its original complex example and remains unposted.

**dev.8 source boundary:** quoted-escape and semantic-property/class/item ranges added after frozen source `9cc1416` were then unreleased extensions, documented separately in [the testing receipt](TESTING.md). They remain absent from the immutable dev.8 archive and are now shipped in dev.9. Older retained archives remain unchanged. Source-repository Actions stays disabled; independent native-speaker, usability and screen-reader reviews remain open. The wider autonomous mission continues.

**Published dev.7 (11 October 2026):** [npm `0.1.0-dev.7`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.7) and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.7) use source tag `09490f54202ca92d96f194af2815d9b7d47ea860` (annotated tag object `654e4beb31fe945f8d5f665b0f3e411308692db2`). Both registry `preview` and `latest` point to dev.7. The retained, registry-downloaded and GitHub-downloaded archives agree: 354,910 bytes, 48 files, SHA-256 `dbd62055087b4428014e792bbf2f099c96443aec0b3d2d2c84fbdae8fd31c771`, SHA-1 `ddc853002663c81d18b7354672f64261783652da`, integrity `sha512-ZRx8BTlesjdDFqToBQZwFRG5QYQpJvq+rV6AntymXzDyen+szb6Q5U3zObZMZk1XJ6C6A33Q/bvIiJlum4VO9Q==`. The GitHub checksum asset also matches. Exact retained-archive JavaScript/strict TypeScript/API/CLI consumers pass on Node 25.9.0 and Node 22.23.3. A fresh-cache public preview installation reports dev.7 through its CLI and reproduces the original complex manifest regex exactly, accepting one valid row and rejecting four malformed variants. Whole-line comments retain identical generated output.

**Hosted dev.7:** owner Pages commit `84768ace9052bf0221d662fc4b0f0a221b8176fb` changes 56 files only inside `Regex-For-Humans/`. [Deployment 38118498328](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38118498328) succeeds; all 79 files of that release build return HTTP 200 and match the local build byte for byte. Installed Chrome shows dev.7, filters the 31 recipes by category and difficulty, compiles comments plus a named capture/backreference, renames the capture and reference together, and displays expert metadata. Manual fixture save/restore retains the work; exact native spans, captures and replacement results agree. Beginner/expert selection preserves the compiled pattern. The dark desktop explanation panel was visually inspected. The measured mobile CSS viewport is exactly 320px with no document overflow; this geometry check is distinct from the desktop visual inspection. No page errors were logged. Source-repository Actions remains disabled.

**Guides and draft:** actual GitHub Arabic/Urdu guides show dev.7, each with 19 section headings, 20 LTR-wrapped code blocks and inline version labels inside RTL prose. The Arabic installation section and the narrow Urdu section were visually inspected. The English Reddit update in Downloads introduces the already-shared project, explains groups and the new dev.7 workshop features, pins the published package and preserves the supplied manifest rules and exact regex. It remains a local draft. The complete autonomous mission, PHP runtime parity and independent language/usability/screen-reader reviews remain open. The frozen dev.5/dev.6 artifacts and tags are unchanged.

**Dev.7 candidate (11 October 2026):** an isolated checkout based on source `06a39c2e6c259a8346c28eed8b4addd33fc6359c` aligns package/lock, changelog, the ten README guides, language/compatibility/security contracts and homepage with `0.1.0-dev.7`. The compiler includes whole-line comments and idempotent single-block alternative imports. The workshop adds syntax colors, rule templates, exact expectations, regression fixtures, 31 searchable recipes, failure explanations and three explanation levels. Arabic/Urdu keep RTL prose, isolated LTR technical text and inline version labels. All 365 candidate Node checks pass on Node 25.9.0 and Node 22.23.3; 64 candidate homepage checks pass. The same underlying compiler passes 7,388 generated-code span/capture comparisons across Python, Rust, Go, Java, C# and Ruby; PHP runtime parity remains unverified. All 576 Chromium checks pass at the source checkpoint; its complete Firefox/WebKit gate is still running at preparation time. Publication follows that gate and exact retained-package verification. At this snapshot, public npm and Pages remain dev.6. Subsequent publication evidence belongs to the [current distribution record on GitHub](https://github.com/OthmaneBlial/Regex-For-Humans/blob/main/docs/DISTRIBUTION.md).

**Published dev.6 (11 October 2026):** [npm `0.1.0-dev.6`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.6) and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.6) use the annotated tag at source `79589b135a81ce63e954a2e892ddc89fd2ea7acb` (tag object `0a65d0ffa8e6b1331eace7f141ce0f74519f64d4`). Both npm `preview` and `latest` point to dev.6. The retained, registry-downloaded and GitHub-downloaded archives are identical: 311,220 bytes, 43 files, SHA-256 `2006a788e8b23fb9235b48a628710fc43b6484ea1aa4073f275b642d6fd9cccb`, SHA-1 `f679a8a77a77f708e93d138408eda3da60692e9f`, integrity `sha512-/uapTW0iKydcbaaR5zu62aFUlcSOd7KJ00Dh1t4Q8EkbQU12NnLFaT0Ba0jR0ugiazMRnEfTNUx3zD8eWORGsg==`. The downloaded GitHub `SHA256SUMS` matches the retained checksum file. Exact-archive clean JavaScript/strict TypeScript/API/CLI consumers pass on Node 25.9.0 and Node 22.23.3 before upload and again using the registry download. Fresh-cache public `@preview` installation and npx return dev.6. The package contains the new `editGroup`, `toSVG`, `analyze` and `exportRegex` APIs and CLI `--target`; browser themes and interface translations belong to the hosted workshop.

**Hosted dev.6:** Pages owner commit `c7d45e53dff06a0bad0250a368fa2c1897741c46` changes only 42 files inside `Regex-For-Humans/`. [Deployment 38099174848](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38099174848) completed successfully. All 66 public files return HTTP 200 and match the built site byte for byte. Installed Chrome displays dev.6 and its npm link, matches a native named capture/backreference, renames the capture and its reference, highlights its actual input range, opens the structural SVG and risk notes, and generates Python code. Four interface languages and both explicit themes retain rules and generated regex; the dark preference survives reload. The 320px workshop has no document overflow or page errors. Its dark capture was visually inspected. Source-repository Actions remains disabled.

**Public README and draft proof:** actual GitHub Arabic/Urdu guides pass installed Chrome at 1280/390/320px after font loading, each with 19 RTL section headings, 20 LTR code blocks and no document overflow. Both 320px introduction captures were visually inspected. This does not replace independent native-speaker, usability or screen-reader review. The updated Reddit draft remains a local Markdown file in Downloads; its exact manifest regex, optional-directory example and three negative variants pass against the publicly installed dev.6 package. No Reddit post was submitted. The frozen dev.5 archive and tag remain unchanged. The wider highlighting/builder/debugger/example mission continues.

**Dev.6 preparation (11 October 2026):** the group editor, structural SVG diagrams, heuristic risk review and nine source-export formats are implemented and pushed through source `3c6a90f`. The workshop adds four interface languages and persistent system/light/dark themes. All ten README guides retain the same 19 complete sections and 20 canonical executable blocks; Arabic and Urdu isolate code in LTR markup inside RTL prose. The full local gate passes 1,138 tests (334 Node, 478 Chromium desktop/mobile, 262 Firefox/WebKit and 64 homepage), builds, clean package consumers and an audit with zero vulnerabilities. A separate clean consumer passes on Node 22.23.3. This entry records preparation; registry, GitHub asset and Pages publication require the receipts added below after upload. PHP runtime parity and independent human reviews remain open. Historical dev.5 archives and tags remain unchanged.

**Published dev.5 (10 October 2026):** [npm `0.1.0-dev.5`](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.5) and the [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.5) resolve to the annotated tag at source `0f1b19b69eb01d604b80ce22ea6e1ae62001009e`. Both npm `preview` and `latest` point to dev.5. The retained, registry-downloaded and GitHub-downloaded tarballs match byte for byte: 248,223 bytes, 38 files, SHA-256 `18ffb8b47bc45a537a34b8b5c0b50b8faaeea5dee3defed45ff6ff00fbda1366`, SHA-1 `0c6db8fa6421a9a514e96de3808e86b17a25749d`, integrity `sha512-GNFG0TEJGFkscBZQufh5pOdlpNNoFbmpu83Io46sc/m91DWBkL7Rb6MwpTgvjuPYxPuyBmjrTfPZ3dMsiZIiXA==`. GitHub's downloaded `SHA256SUMS` also matches. Exact-archive clean JavaScript/TypeScript/API/CLI consumers pass on Node 25.9.0 and Node 22.23.3 before upload and again from the registry download. Fresh-cache public `@preview` installation and npx return dev.5; the installed CLI generates a native v intersection.

**Hosted dev.5:** Pages owner commit `ccd5826c027e154052d99a472aedb2d0f7aa66d5` changes only 36 files inside `Regex-For-Humans/`. [Deployment 38070341053](https://github.com/OthmaneBlial/OthmaneBlial.github.io/actions/runs/38070341053) completed successfully. The public homepage, CSS/JS, workshop, rendered guide and library module return HTTP 200 with exact tested bytes; all 12 workshop JavaScript modules match too. Connected Chrome shows dev.5 and its npm link. Native v intersection with a named capture and d indices passes four public examples, shows `value = "A"` at `0–1`, and has no console errors. Source-repository Actions remains disabled.

**dev.5 guides and checks:** 301 Node tests, ten README/localization contracts, lint/types/links, builds, 64 homepage checks and eight changed-guide checks pass. Runtime source is unchanged from the complete 891-test native-core gate. Actual GitHub Arabic/Urdu guides at `0f1b19b` pass measured 1280/390/320px widths after fonts load: 16 RTL headings, seven RTL tables, 20 LTR blocks, 236 isolated LTR inline fragments and no overflow. All 20 rendered code blocks match English; the three native-set commands remain single LTR lines. Narrow Urdu table and Arabic introduction captures are visually inspected, and the viewport override is reset. The Downloads Reddit draft now describes published dev.5, retains the exact 19-rule manifest and stays unposted. Stable support and human review gates remain open.

**Earlier dev.5 preparation (10 October 2026):** package/lock version, changelog, ten README guides, security policy and product documentation were aligned with the native set/string/flag/class/property/boundary/assertion/lazy additions. The first local candidate passed 301 Node tests, lint/types/docs, both builds and a clean JavaScript/TypeScript/API/CLI consumer. Runtime source was unchanged from the complete 891-test gate at `612dc18`. Archive and publication gates were pending at that preparation snapshot; the current verified publication is recorded above. Historical dev.4 hashes and dated source milestones below retain their original snapshots. Human reviews remain open.

**Published native-set guide proof (10 October 2026):** source `612dc18` is pushed directly to `main`. Both actual GitHub RTL guides pass measured 1280/390/320px widths after font loading, with 16 RTL headings, seven RTL tables, 20 LTR blocks, 234 LTR inline fragments, three single-line set headers and no overflow. Their rendered code exactly matches the English guide at that commit. Two targeted 320px passage captures are visually inspected; closing-brace fragments retain LTR isolation and the viewport override is reset. This publishes source/documentation, while npm and Pages remain dev.4. The Reddit draft stays unposted and human review gates remain open.

**Nested native v-set source candidate (10 October 2026):** native union/intersection/subtraction blocks, recursive typed members and exact spans, structural string-complement validation and v-mode empty/universal sets are implemented through the shared parser/compiler, reverse reader, explanations, CLI and isolated workshop. The final complete local gate passes 891 tests (301 Node, 378 Chromium desktop/mobile, 148 Firefox/WebKit, 64 homepage), clean installed-package checks, builds, lint/types/docs and a zero-vulnerability audit. Node 22 passes 55 selected checks and a separate clean consumer. All ten source guides document the feature and retain the same 20 canonical code blocks; Arabic/Urdu have 234 explicitly LTR inline fragments and three separate LTR set commands. Public rendering is a separate check. The Downloads Reddit draft includes the new source-only operations and remains unposted. npm/Pages are still dev.4; the next distribution milestone is a verified dev.5 preview and synchronized site. Human review gates stay open.

**Published native-string documentation proof (10 October 2026):** core source `ca34862` and the narrow-screen version-line correction `fdddc09` are pushed directly to `main`. At `fdddc09`, both actual GitHub RTL guides pass measured 1280/390/320px checks after font loading: 16 RTL headings, seven RTL tables, 20 canonical LTR blocks, 226 LTR inline fragments, three native-string commands and a standalone version line on single LTR lines, and no overflow. Their rendered code exactly matches the English GitHub guide at the same commit. Six targeted passage captures are visually inspected; [TESTING.md](TESTING.md) records the zoom-adjusted capture method and the discarded blank screenshots. npm and Pages remain dev.4, the Reddit draft remains unposted and human review gates remain open.

**Native v-string source candidate (10 October 2026):** finite string sets, all seven standard Unicode properties of strings and explicit code-point sequences are implemented through the shared parser/compiler, reverse translator, explanations, typed member traces, CLI and workshop. Native v matching preserves longer-first preference, shorter-member backtracking, empty members, capture indices and cursor behavior; structural validation rejects invalid complements without replacing native string semantics. The full local gate passes 817 tests (295 Node, 344 Chromium desktop/mobile, 114 Firefox/WebKit, 64 homepage), clean package checks, builds, lint/types/docs and a zero-vulnerability audit. All 49 selected Node 22 tests and a separate clean Node 22 consumer pass. All ten source README guides document the feature; Arabic/Urdu retain 20 canonical code blocks and now 226 LTR inline fragments. The Downloads Reddit draft describes the new source-only strings and remains unposted. npm and the hosted site remain at dev.4; the temporary pack candidates are verification artifacts, not registry releases. Nested v sets/intersection/subtraction are next, followed by a verified dev.5 npm/Pages milestone. Human review gates stay open.

## Local verification

**Eight-flag source candidate (10 October 2026):** full verification passes with 288 Node tests, 324 Chromium desktop/mobile checks, 94 Firefox/WebKit checks and 64 homepage checks, builds, lint/types/docs, a clean JavaScript/TypeScript consumer and zero audit vulnerabilities. A subsequent CLI alias-order fix passes all 47 focused CLI/flag tests and clean consumers on Node 25.9.0 and Node 22.23.3; final checks and documentation builds pass afterward. Both installed consumers cover every native flag combination and both orders of `--flags` plus i/s aliases. [TESTING.md](TESTING.md) records the 184,320 native cursor/capture comparisons, 20,480 absolute-anchor browser comparisons and the guarded WebKit edge case. The new API/CLI/workshop flags and native u/v class modes are unreleased; the exact published dev.4 archive and hosted playground remain unchanged. Nested v sets/string properties and human review gates remain open.

**Published eight-flag documentation proof (10 October 2026):** source `5696fc3` is pushed directly to `main`. Actual Arabic/Urdu GitHub guides pass connected-Chrome DOM/layout checks at measured 1280/390/320px CSS widths after font loading: 16 RTL headings, seven RTL tables, 20 canonical LTR blocks and 221 explicitly LTR inline fragments. Both new flag commands stay on one LTR line, the earlier commands retain their checked layout, and neither document overflows. Rendered code blocks exactly match the English GitHub guide at the same commit. [TESTING.md](TESTING.md) distinguishes these checks from earlier screenshot reviews and the initial HTTP 503 requests. The Downloads Reddit draft includes source-only flags and remains unposted. npm dev.4 and the hosted playground remain unchanged; human review gates remain open.

**Published class-note documentation proof (10 October 2026):** class source `647ba6b` and RTL layout correction `d18cd00` are pushed directly to `main`. Actual Arabic/Urdu GitHub guides pass installed Chrome at 1280/390/320px: 16 RTL headings, seven RTL tables, 20 canonical LTR blocks and 202 explicitly LTR inline fragments. All three new class/range commands remain on one LTR line after removing list indentation; all six final screenshots were visually inspected without document overflow. Ten README/localization checks and final lint/types/docs/build checks pass after that correction. The Downloads Reddit draft now includes source-only classes/ranges and remains unposted. This source/documentation publication does not change npm `0.1.0-dev.4` or the hosted playground; human review gates remain open.

**Composable-character-class source candidate (10 October 2026):** the final full `CI=1 npm run verify` command passes uninterrupted: 281 Node tests, 316 bundled Chromium desktop/mobile checks, 86 Firefox/WebKit checks, 64 homepage checks, lint/types/docs, builds, a clean JavaScript/TypeScript package consumer and zero audit vulnerabilities. All 50 selected checks and a separate clean consumer also pass on Node 22.23.3. Installed CLI checks preserve class members, inclusive Unicode ranges, native complement polarity and lazy preference in both directions; TypeScript narrows `CharacterClassSegment` and `CharacterClassMember`. The corpus compares 19,800 native match/capture/indices results in Node and per browser engine/viewport, plus 7,040 seeded Node comparisons. [TESTING.md](TESTING.md) records the obsolete word-class fixture and collapsed UUID-panel corrections preceding this final successful run. Final documentation records are checked and rebuilt afterward. This verifies source additions; it does not replace the exact published npm `0.1.0-dev.4` archive or deploy Pages. Classes, properties, boundaries, lazy repetition and lookaround remain unreleased beyond dev.4. Native v sets/string properties, broader flags and human review gates remain open.

**Unicode-property source candidate (10 October 2026):** the full `CI=1 npm run verify` gate passes in one uninterrupted command: 274 Node tests, 312 bundled Chromium desktop/mobile checks, 82 Firefox/WebKit checks, 64 homepage checks, lint/types/docs, builds, a clean JavaScript/TypeScript package consumer and zero audit vulnerabilities. All 43 selected checks and a separate clean consumer also pass on Node 22.23.3. Installed CLI checks preserve standalone property aliases, polarity, lazy preference and native complement/case-folding behavior in both directions; TypeScript narrows `UnicodePropertySegment`. Final documentation records are checked and rebuilt afterward. This verifies the source addition and does not change the exact published npm `0.1.0-dev.4` archive or deploy a new Pages build. Unicode properties, boundaries, lazy repetition and lookaround remain unreleased beyond dev.4. Character-class combinations, v sets/string properties, broader flags and human review gates remain open.

**Word-boundary source candidate (10 October 2026):** the full `CI=1 npm run verify` gate passes in one uninterrupted command: 268 Node tests, 308 bundled Chromium desktop/mobile checks, 78 Firefox/WebKit checks, 64 homepage checks, lint/types/docs, builds, a clean JavaScript/TypeScript package consumer and zero audit vulnerabilities. All 43 focused checks and a separate clean consumer also pass on Node 22.23.3. Installed CLI checks cover both boundary directions and TypeScript consumers narrow the new `BoundarySegment` variant. Final documentation records are rebuilt and checked afterward. This verifies the current source addition; it does not change the exact published npm `0.1.0-dev.4` archive or deploy a new Pages build. Boundary, lazy and lookaround support remain unreleased beyond dev.4. Human review gates stay open.

**Ordered alternatives and 0.1.0-dev.4 candidate (10 October 2026):** all verification components pass on Node 25.9.0/npm 11.12.1: 251 Node tests, 296 bundled Chromium desktop/mobile workshop checks, 66 Firefox/WebKit checks, 64 homepage checks, lint/types/docs, builds, a clean installed-package JavaScript/TypeScript consumer and zero audit vulnerabilities. All 26 focused group/reference/alternative/localization checks also pass on Node 22.23.3. Installed Chrome at 1280/390px and Firefox/WebKit at 1280px verify the release version, native date capture values/spans, alternatives, reverse capture participation, keyboard source navigation and 320px layout, with no page errors. The first command found two obsolete alternative-error fixtures, replaced with equivalent unsupported lookaheads without weakening selection/scrolling/recovery assertions. The subsequent full command passed the compiler/workshop/compatibility stages and found the homepage screenshot URL/dimensions still referencing the old image. After updating those attributes, the complete 64-check site suite and audit passed separately. This records successful component gates rather than one uninterrupted command. The worker deadline remains 1,200 ms. Human, screen-reader and independent native-language reviews remain open.

**Capture explorer and RTL documentation verification (10 October 2026):** source `4f7495d` passes all verification components: lint/types/docs, 244 Node tests, 292 bundled Chromium desktop/mobile workshop checks, 62 Firefox/WebKit checks, 64 homepage checks, builds, clean package installation and zero audit vulnerabilities. All 30 focused group/reference/runner/localization checks pass on Node 22.23.3. The full command stopped at a language-link test selector; after its correction, the complete homepage suite and audit passed separately. This is component evidence, rather than one uninterrupted full-command pass. Native capture values/spans, absent/empty participation, Unicode advancement, bounded search enumeration and nested reply validation are covered. npm remains `0.1.0-dev.3`; the new source features have not been released there.

**Compiler and multilingual documentation verification (10 October 2026):** the full `npm run verify` gate passed for the capture/reference/reverse compiler milestone at `42a147b`: 238 Node tests, 282 Chrome desktop/mobile workshop checks, 52 Firefox/WebKit checks, 62 homepage checks, clean package installation, builds and zero audit vulnerabilities. The subsequent README/site milestone at `34b2b9b` passed all 241 Node tests, all 64 Chrome desktop/mobile homepage checks, lint/types/docs, builds and clean package installation. Its 10 localization/link checks passed on Node 22.23.3. These are separate verified snapshots; npm remains `0.1.0-dev.3`, and independent translation review remains open.

**Latest full release verification (2 October 2026):** `npm run verify` passed on `cae0204` with Node 25.9.0/npm 11.12.1 on macOS arm64: 222 Node tests, 276 desktop/mobile Chromium checks, 46 Firefox/WebKit checks, 62 homepage checks, clean-consumer installation of the 110,701-byte, 26-file package, and zero audit vulnerabilities. This is local verification; GitHub Actions remains disabled. The human usability and screen-reader reviews remain open.

**Earlier full release verification (2 October 2026):** The complete `npm run verify` gate passed at release-candidate commit `e19b576` with Node 25.9.0/npm 11.12.1: 222 Node tests, 274 desktop/mobile Chromium checks, 44 Firefox/WebKit checks, 62 homepage checks, a 109,481-byte 26-file clean consumer tarball and zero audit vulnerabilities. Coverage includes reverse translation of `[^]`, ordinary-dot preservation under synthesized `s`, CLI/library parity and line-break matching. The final tagged commit `ad638fe` adds the build-generated homepage module URL; `npm run check` and all 62 site checks passed again at that commit. The exact tagged tarball was regenerated and clean-consumer-tested at the same size. Publication evidence is recorded below; human usability and screen reader reviews remain open.

**Earlier full release verification (2 October 2026):** Full release verification passed on 2 October 2026 at tagged source commit `c1bae7c` (`v0.1.0-dev.1`) with Node 25.9.0/npm 11.12.1: 220 Node tests, 272 desktop/mobile Chromium workshop checks, 42 Firefox/WebKit checks, 62 homepage checks, a clean consumer install of the retained 106,631-byte, 26-file tarball and an audit with zero vulnerabilities. The UUID recipe uses five fixed hexadecimal groups and thirteen examples; every hex position, separator and group boundary agrees in forward/reverse matching under all four option combinations. Its shared browser flow checks eleven explanation fragments, option changes, copy requests, reverse translation, automated accessibility and 320px layout. Two initial gate attempts stopped at obsolete CLI version and README source-command assumptions; both checks were corrected before the complete successful run. The exact retained archive then passed clean consumer installs on Node 25.9.0 and Node 22.23.3 with npm 11.12.1: eighteen recipes, 176 inputs, 704 option variants per runtime, 36 CLI recipe-direction checks, the README example and strict TypeScript declarations. All 22 selected UUID, runner and documentation checks passed on Node 22. These are local automated checks, separate from publication and human reviews.

**Earlier full local verification (2 October 2026):** Full local verification passed on 2 October 2026 at source commit `a958797` with Node 25.9.0/npm 11.12.1: 219 Node tests, 268 desktop/mobile Chromium workshop tests, 40 Firefox/WebKit checks, 62 homepage tests, a clean consumer install (105,170-byte tarball) and an audit with zero vulnerabilities. The Node regression and both Chrome UI cases failed before the fix: an injected contradictory result incorrectly reported all four examples as expected. Success replies now require the complete sent case count and IDs, with pass consistent with actual versus the original expected value; caller edits after posting cannot change the snapshot, and reordered valid replies remain accepted. All 14 runner checks also passed on Node 22.23.3. Additional local Chrome at 1280/390px and Firefox/WebKit at 1280px passed 12 shared flows, including 45 malformed replies per controller flow and both string/contradictory UI failure and recovery states. There were zero automated accessibility violations in those UI states, no page errors or overflow when narrowed to 320px after recovery; eight failure panels were inspected. Only the controller changes executable behavior: 19 static resources are identical and 13 others change only versioned URLs. Regex matching stays in the worker. Injected events do not establish naturally occurring worker corruption; this checkout tarball, the unchanged published npm preview and human validation remain separate evidence.

**Latest security-policy verification (2 October 2026):** Security-policy verification passed on 2 October 2026 at source commit `39b82f8`: formatting/types/documentation checks, all 218 Node tests, Pages/share-card builds, 62 homepage checks and an audit with zero vulnerabilities on Node 25.9.0/npm 11.12.1. The new documentation contract failed before the fix; it now keeps the policy aligned with the README’s versioned experimental npm preview, distinguishes stable support and identifies fixes on main. Clean-consumer installs passed on Node 25.9.0 (104,214-byte tarball) and Node 22.23.3 (104,354-byte tarball), both using npm 11.12.1; all seven documentation contracts also passed on Node 22. Private vulnerability reporting is enabled, repository Actions remains disabled and the public preview version/integrity is unchanged. All 33 non-Markdown website resources match the prior deployment byte for byte. This documentation/component run is separate from the full workshop snapshot and human validation.

**Earlier full local verification (2 October 2026):** Full local verification passed on 2 October 2026 at source commit `1dc5f32` with Node 25.9.0/npm 11.12.1: 217 Node tests, 266 desktop/mobile Chromium workshop tests, 38 Firefox/WebKit checks, 62 homepage tests, a clean consumer install (103,458-byte tarball) and an audit with zero vulnerabilities. Both Chrome cases and the final check with a settled caret against the previous hosted build failed before the fix. Native focus now skips caret scrolling, then nearest scrolling reveals the surviving control without moving its reading position. Shared checks at normal width and 320px retain its complete view, value and caret, verify focus/visibility and matching, and report zero automated accessibility violations, page errors or overflow. Intermediate focus restores still failed Firefox; the final setup separates settled caret placement from manual scrolling. Only the workshop app changes executable behavior; 20 static resources are identical and 12 others change only versioned URLs. No new Node 22 run or npm release is claimed; human validation remains separate.

**Earlier full local verification (2 October 2026):** Full local verification passed on 2 October 2026 at source commit `838d5ea` with Node 25.9.0/npm 11.12.1: 217 Node tests, 266 desktop/mobile Chromium workshop tests, 38 Firefox/WebKit checks, 62 homepage tests, a clean consumer install (102,537-byte tarball) and an audit with zero vulnerabilities. Both Chrome regression cases failed before the fix. Surviving examples now retain selection offsets/direction, reading scroll and resize height through additions/removals; renumbering, focus, native replacement of the restored selection, matching and fresh rows/recipes passed. Additional local Chrome at 1280/390px and Firefox/WebKit at 1280px repeated the flow at normal width and 320px, with zero automated accessibility violations, no page errors or overflow; seven retained-view panels were inspected. Only the workshop app changes executable behavior; 20 static resources are identical and 12 others change only versioned URLs. Initial formatting failed, then was corrected before the full gate. No new Node 22 run or npm release is claimed; physical keyboard and screen-reader validation remain separate.

**Earlier full local verification (2 October 2026):** Full local verification passed on 2 October 2026 at source commit `c8b0554` with Node 25.9.0/npm 11.12.1: 217 Node tests, 264 desktop/mobile Chromium workshop tests, 36 Firefox/WebKit checks, 62 homepage tests, a clean consumer install (101,295-byte tarball) and an audit with zero vulnerabilities. Both new Node regressions failed before the fix. Forty malformed worker replies now fail immediately and retire the worker; valid empty/100-result batches, safe-integer boundary IDs, old request IDs, idle messages and replacement recovery remain covered. All 13 runner checks also passed on Node 22.23.3. Additional local Chrome at 1280/390px and Firefox/WebKit at 1280px passed the shared native-worker event and UI flows, with zero automated accessibility violations in failure/recovery states, no page errors or 320px overflow; four failure panels were inspected. The supplementary capture helper initially needed an explicit browser context for Axe; its corrected run passed. Only the controller changes executable behavior; 19 static resources are identical and 13 others change only versioned URLs. Injected events, this checkout tarball, the published npm preview and human validation remain separate evidence.

**Latest optional-flags type verification (2 October 2026):** Optional compiler flags type verification passed on 2 October 2026 at source commit `acba0c0`: checks, all 215 Node tests, Pages/share-card builds, 32 Firefox/WebKit checks, 62 homepage checks and an audit with zero vulnerabilities. The installed strict consumer failed at three valid uses before the fix; it now accepts readonly defaults, inline undefined and forwarded optional flags with `exactOptionalPropertyTypes`. Null compiler flags and undefined native metadata flags remain rejected. Clean installations passed on Node 25.9.0 (100,005-byte tarball) and Node 22.23.3 (100,158-byte tarball), both using npm 11.12.1. Local Chrome at 1280/390px and Firefox/WebKit at 1280px verified default matching, metadata reads and validation, with no page errors or 320px overflow. Both executable modules are unchanged; all changed static resources differ only in JSDoc or versioned URLs. This component run is separate from the latest full workshop snapshot, the published npm preview and human validation.

**Earlier full local verification (2 October 2026):** Full local verification passed on 2 October 2026 at source commit `ca42267` with Node 25.9.0/npm 11.12.1: 215 Node tests, 260 desktop/mobile Chromium workshop tests, 32 Firefox/WebKit compatibility checks, 62 homepage tests, a clean consumer package install (97,677-byte tarball), and `npm audit` with zero vulnerabilities. Both new word-class regressions failed before the change. All 24 range/underscore orders, three duplicate forms, negation, eight flag combinations and eight repetition forms retain complete native `exec()` results, flags and `lastIndex`; nearby incomplete or extended ranges remain rejected at their original columns. All 27 reverse/word checks also passed on Node 22.23.3. Additional local Chrome at 1280/390px and Firefox/WebKit at 1280px each verified 64 native variants and visible translation/options/matching/copy requests, error navigation and recovery. Both states had zero automated accessibility violations, no page errors or overflow at 320px; four reverse-panel crops were inspected. This checkout tarball and local automation remain separate from the unchanged published npm preview and human validation.

**Latest cached-metadata type verification (2 October 2026):** Cached metadata type verification passed on 2 October 2026 at source commit `77da041`: formatting/types/documentation checks, all 215 Node tests, Pages/share-card builds, 32 Firefox/WebKit compatibility checks, 62 homepage checks and an audit with zero vulnerabilities on Node 25.9.0/npm 11.12.1. Clean-consumer installs passed on Node 25.9.0 (98,775-byte tarball) and Node 22.23.3 (98,935-byte tarball), both with npm 11.12.1. The strict consumer failed before the fix because cached and inline pairs lacked segments; it now accepts readonly pairs and complete inline results while six expected-error cases reject missing/non-string fields and null/string inputs. Node and installed-package checks verify that unused segments are never read. Additional local Chrome at 1280/390px and Firefox/WebKit at 1280px verified frozen metadata, complete results, ignored segment getters, single source/flags reads, validation order and matching, with no page errors or overflow at 320px. An exact comparison confirmed index.js differs only in JSDoc; executable helper code is unchanged. This component run is separate from the full workshop snapshot at `ca42267`, the unchanged published npm preview and human validation.

**Earlier full local verification (2 October 2026):** `npm run verify` passed at source commit `2b86412` with Node 25.9.0/npm 11.12.1: 213 Node tests, 258 desktop/mobile Chromium workshop tests, 30 Firefox/WebKit compatibility checks, 62 homepage tests, a clean consumer package install (95,866-byte tarball), and `npm audit` with zero vulnerabilities. The new regressions failed before validation because malformed catalogue data blocked later manual compilation. Nineteen malformed payloads now retain manual editing, matching and copy requests; delayed failures preserve edits, valid reloads restore all 17 recipes, and 100 examples accept empty strings and CRLF normalized to the 2,048-code-unit field limit. Additional local Chrome checks at 1280/390px and Firefox/WebKit at 1280px passed the same flows with zero automated accessibility violations in failure/recovery states, no page errors or overflow at 320px; four sidebar crops were inspected. These automated checks and this checkout tarball are separate from human validation and the unchanged published npm preview.

The first full attempt stopped at an existing desktop native-resize check (257 workshop passes, one failure); it did not reach compatibility, homepage or audit checks. Commit `69e274d` waits for current example feedback before measuring native resize geometry, preserving the real drag and height/identity assertions. All ten repeated desktop/mobile resize checks passed, followed by the complete successful gate above.

**Earlier full local verification (2 October 2026):** `npm run verify` passed at source commit `260e004` on Node 25.9.0/npm 11.12.1, with Biome 2.5.15: 213 Node tests, 254 desktop/mobile Chromium workshop tests, 26 Firefox/WebKit compatibility checks, 62 homepage tests, a clean consumer package installation (94,880-byte tarball), and `npm audit` with zero vulnerabilities. Message-error handling passed a red/green Node regression, all 11 runner checks on Node 22.23.3, and additional local controller/workshop checks in Chrome at 1280/390px and Firefox/WebKit at 1280px. Pending and idle failures retire the worker; exact recovery and late-event isolation passed. Both visible states had zero automated accessibility violations, no page errors or overflow at 320px; four example-panel crops were inspected. These checks dispatch a native-worker event rather than inducing an internal browser decoding failure. The checkout tarball, hosted deployment, unchanged published npm preview and human validation are separate.

**Latest homepage recipe verification (2 October 2026):** source commit `2b65554` passed formatting/types/documentation checks, all 212 Node tests, the Pages build, a clean consumer installation (93,993-byte tarball), all 62 homepage checks and an audit with zero vulnerabilities on Node 25.9.0/npm 11.12.1. The loader validates and compiles all three demos before enabling any button; nine malformed-data cases retain the initial pattern, matching, copying and workshop link, then valid reloads recover. The shared check passed in local Chrome at 1280/390px and Firefox/WebKit at 1280px, with no page errors, 320px overflow or settled-state automated accessibility violations. Four demo crops were inspected. All 31 other non-Markdown website resources matched the previous deployed build; this homepage component run is separate from the full workshop/browser snapshot below and the unchanged published npm preview.

**Earlier full local verification (2 October 2026):** `npm run verify` passed at source commit `efe8c72` on Node 25.9.0/npm 11.12.1, with Biome 2.5.15: 212 Node tests, 252 desktop/mobile Chromium workshop tests, 24 Firefox/WebKit compatibility checks, 60 homepage tests, a clean consumer package installation (93,158-byte tarball), and `npm audit` with zero vulnerabilities. Nullish direct worker messages return the existing validation error instead of an uncaught exception, and the same worker still accepts the next valid request. Normal controller request IDs, matching, limits and the 1,200 ms product deadline are unchanged. Existing whole-batch validation, flags, partial-match feedback, reverse translation, complex recipes, keyboard/focus and clipboard checks remain covered. This checkout tarball and local macOS automation are separate from the unchanged published npm preview and human validation.

**Latest independent native-pattern verification (2 October 2026):** source commit `2094b72` passed formatting/types/documentation checks, all 212 Node tests, the Pages build, a clean consumer installation (92,621-byte tarball), all 60 homepage checks and an audit with zero vulnerabilities on Node 25.9.0/npm 11.12.1. Native forms, independent of compiler output, retain deterministic translation and complete `exec()` results for 4,096 flag variants across 31 selected strings. All 24 reverse/fuzz checks also passed on Node 22.23.3. All 33 non-Markdown website files matched the prior deployed build byte for byte. This testing/documentation run is separate from the full workshop/browser snapshot below and the unchanged published npm preview.

**Latest testing-guide verification (2 October 2026):** source commit `1a5f928` passed formatting/types/documentation checks, all 211 Node tests, the Pages build, a clean consumer installation (92,014-byte tarball), all 60 homepage checks and an audit with zero vulnerabilities on Node 25.9.0/npm 11.12.1. The guide puts setup first and its individual commands match the complete verification gate, including Pages, compatibility and share-card steps. Previous coverage/verification text is retained with reviewed reference corrections. All 13 README/setup and documentation-link checks also passed on Node 22.23.3. All 33 non-Markdown website files matched the prior deployed build byte for byte. This documentation run is separate from the full workshop/browser snapshot below and the unchanged published npm preview.

**Latest CLI UTF-8 verification (2 October 2026):** source commit `3e2fb04` passed formatting/types/documentation checks, all 208 Node tests, the Pages build, a clean consumer installation (88,620-byte tarball), all 60 homepage checks and an audit with zero vulnerabilities on Node 25.9.0/npm 11.12.1. Forty malformed-input failures cover both directions, file/stdin input and plain text/JSON; valid Unicode/BOM recovery, forward source columns and reverse matching passed. All 45 CLI/literal-reader checks also passed on Node 22.23.3. All 33 non-Markdown website files matched the prior deployed build byte for byte. This CLI/documentation run is separate from the full workshop/browser snapshot below and the unchanged published npm preview.

**Earlier full local verification (2 October 2026):** `npm run verify` passed at source commit `b5b3868` on Node 25.9.0/npm 11.12.1, with Biome 2.5.15: 210 Node tests, 250 desktop/mobile Chromium workshop tests, 22 Firefox/WebKit compatibility checks, 60 homepage tests, a clean consumer package installation (91,748-byte tarball), and `npm audit` with zero vulnerabilities. Full-mode feedback reports the zero-based UTF-16 position of rejected partial and empty matches. Shared checks cover Unicode offsets, line matches, controls, escaped data, expected-negative results and accessible descriptions in all three engines. Complete matching still backtracks past a shorter first search match; switching modes retains the generated regex. Existing API, literal budgets, native metadata, option flags, workers, CLI reverse, complex records, keyboard/focus, scroll and clipboard flows remain covered. The tested checkout tarball is separate from the unchanged published 80,466-byte npm preview. These runs verify local automation on macOS only; see [TESTING.md](TESTING.md) for earlier snapshots and compatibility evidence.

### Preview server

The earlier encoded-forward-slash fix passed its full gate at `957c21a` and all six HTTP tests on Node 22.23.3. Existing encoded file and directory URLs redirect to literal path separators before serving, retaining queries and Unicode/space escapes. Redirects stay on the same origin, literal percent data remains filename data, and missing/outside targets preserve `404` / `403` without redirects. Desktop/mobile Chrome and Firefox/WebKit verified relative module and stylesheet loading through actual browser navigation. This changes the local preview server; GitHub Pages serves the hosted site with its own server.

The earlier missing-path preview server fix passed its full local gate at `e111b9c`, and all five HTTP server tests passed separately on Node 22.23.3. URLs that try to enter a file as a directory return `404` for GET and HEAD, including encoded separators and query strings. Bodies stay empty with no redirect; malformed URL escapes retain `400`, and valid assets still load after errors. This is local server evidence rather than a change to the GitHub Pages server.

The earlier full run also covers case-insensitive content-type lookup in the local preview server. Its four HTTP regressions passed separately on Node 22.23.3; desktop/mobile Chrome fixtures verified that uppercase JavaScript modules and mixed-case stylesheets now load and affect the page. Unknown extensions retain their binary fallback, with exact GET content, empty HEAD bodies and `nosniff` preserved. This is local preview evidence rather than a change to the GitHub Pages server.

The earlier local preview server fix at `5a9772c` passed `npm run check`, all 164 Node tests, `npm run build:pages` and a clean-consumer package installation (61,441-byte tarball) on Node 25.9.0/npm 11.12.1. Its three HTTP server regressions also passed on Node 22.23.3. This focused tooling run verifies root-directory links and outside-target rejection; the complete browser snapshot remains the full run above.

## Hosted development preview

### Release 0.1.0-dev.4, alternatives and ten README languages

Tagged source `af7029176f0c28669cbb1352f2137d07d3a95ddf` was published into the existing project folder at Pages commit `1dfaf1cad277ce875e15a03e17ffd7bde54c1ebd`; the Pages build completed successfully. All 58 served files return HTTP 200 and match the local build by SHA-256. Public installed Chrome at 1280/390px and Firefox/WebKit at 1280px verify the dev.4 version and npm link, ten language links, native date capture values/spans, ordered choices, reverse capture participation and keyboard source navigation, with no page errors or document overflow at 320px. Four public capture-panel screenshots were visually inspected.

The ten README guides link dev.4 and mark groups, captures, references and alternatives as available. Desktop/mobile screenshots now show the current build and open native date captures. Actual GitHub views of Arabic and Urdu at 1280/390px retain 16 RTL headings, seven RTL tables, 20 LTR blocks and 171 explicitly LTR inline fragments per document. All 20 code blocks match the canonical README. Independent native-speaker and screen-reader reviews remain open.

The development site and workshop are live at [othmaneblial.github.io/Regex-For-Humans](https://othmaneblial.github.io/Regex-For-Humans/).

### Capture explorer and Arabic/Urdu README guides

Source `4f7495d` was published at Pages commit `95f66c3`, whose build succeeded on 10 October 2026. All 58 served files return HTTP 200 and match local SHA-256 values; all 33 changed files remain inside the existing project folder. Chrome at 1280/390px and Firefox/WebKit at 1280px verify ten language links, four requested copies, native year/month/day values and spans, absent versus empty capture values and Unicode empty-match positions 0/2/3, with no page errors or 320px overflow. Four public capture-panel screenshots were inspected. These checks use the unchanged 1,200 ms worker deadline; clipboard interception verifies requested text.

Both complete translated READMEs were also checked directly on their published GitHub pages at 1280/390px: 16 section headings and seven tables use RTL, all 20 code blocks use LTR and retain canonical code bytes, and 165 inline code fragments explicitly declare LTR. Eight published introduction/capture screenshots were inspected. Independent native-speaker and screen-reader reviews remain open, as does workshop UI localization. This website publication does not release the new compiler or explorer features to npm.

### Complete README translations and capture guides

Source `34b2b9b` was published inside the existing `Regex-For-Humans/` folder at Pages commit `22245c6`, whose build succeeded on 10 October 2026. All 56 served files match the local build by SHA-256; the canonical homepage and workshop return HTTP 200. Chrome at 1280/390px and Firefox/WebKit at 1280px verify eight README links, all four new copy requests, no 320px overflow, native capture/reference import and positive/negative matching in the isolated worker, with no page errors. Clipboard interception verifies requested copy text, rather than the operating-system clipboard. The homepage keeps its existing identity and adds capture fields, API/CLI examples and FAQs. The seven translated READMEs retain all 20 canonical code blocks and 18 recipes. Workshop UI translation and independent native-speaker review remain open; this publication does not release the new compiler features to npm.

### Release 0.1.0-dev.1 and UUID recipe

Hosted release verification passed after Pages commit `2bf90f0` built successfully on 2 October 2026 (Europe/Paris): all 46 served files matched local SHA-256 values, and all 19 changed files are inside the existing project folder. Chrome at 1280/390px and Firefox/WebKit at 1280px passed the UUID flow: eighteen recipes, thirteen preloaded examples, eleven explanation fragments, four option combinations, reverse translation and copy requests, with zero automated accessibility violations, page errors or overflow at 320px; four input panels were inspected. Twelve shared worker-reply flows passed, including 45 malformed replies per controller flow, original expectations despite caller edits, reordered valid results, stale/idle handling and replacement recovery. Both injected string and contradictory UI replies preserve rules, regex, input and focus through failure and recovery; eight failure panels were inspected, with zero automated accessibility violations and no page errors or 320px overflow. Worker reuse, whole-batch validation, 100-example/2,048-code-unit boundaries and three deliberate 150 ms interruptions per engine/viewport flow also passed; the product deadline remains 1,200 ms. Desktop/mobile checks passed all three complex records, 100 explanation fragments, 26 exact inputs, real clipboard, reverse translation, focus and retained/reset scroll, including the manifest's 32/33-emoji boundary; six regex crops were inspected. The site links the released `0.1.0-dev.1` package and CLI reverse instructions. These automated and injected-event checks are separate from the exact npm/GitHub archive checks below and the open human/stable-release gates.

### Replies checked against sent cases

Hosted sent-case reply verification passed after Pages commit `a37a130` built successfully on 2 October 2026 (Europe/Paris): all 46 served files matched local SHA-256 values. All 17 changed files are inside the existing project folder; only the controller changes executable behavior, with 19 resources identical and 13 changing only versioned URLs. Chrome at 1280/390px and Firefox/WebKit at 1280px passed 12 shared flows: 45 malformed replies per controller flow, original expectations despite caller edits, reordered valid results, safe boundaries, stale/idle handling and replacement recovery. Both string and contradictory UI failure/recovery states retained rules, regex, input and focus, with zero automated accessibility violations, no page errors or overflow at 320px after recovery; eight failure panels were inspected. Existing worker reuse, batch validation, 100-example/2,048-code-unit boundaries and three deliberate 150 ms interruptions per flow passed; the product deadline remains 1,200 ms. Desktop/mobile complex checks passed all three records, 100 explanation fragments and 26 exact inputs, real clipboard, reverse, focus and scroll behavior; six regex crops were inspected. These are injected-event and automated browser checks, separate from the unchanged npm preview and human validation.

### Published preview in the security policy

Source commit `c686343` was synchronized into the existing project folder at Pages commit `12b6373`.

Hosted security-policy verification passed after Pages commit `12b6373` built successfully on 2 October 2026 (Europe/Paris): all 46 served files matched local SHA-256 values. Only four Markdown files changed inside the existing project folder; all 33 non-Markdown resources are byte-identical to the prior deployment. The served policy links the README’s versioned experimental npm preview, distinguishes stable support and identifies fixes on main. This documentation update preserves the previously verified workshop behavior and unchanged npm preview; it is not a new package release or human usability result.

### Focus without caret scrolling

Source commit `cb9a200` was synchronized into the existing project folder at Pages commit `30d5f42`, whose build succeeded on 2 October 2026 (Europe/Paris). All 16 changed files are within `Regex-For-Humans/`; 20 non-Markdown resources stayed identical, and 12 of the other 13 differ only in versioned URLs. The remaining file is the tested workshop app.

Hosted verification of a caret outside the reading view passed after Pages commit `30d5f42` built successfully: all 46 served files matched local SHA-256 values. Chrome at 1280/390px and Firefox/WebKit at 1280px repeated the complete example-view flow at normal width and 320px. After removal, the collapsed end caret and 140px height remain unchanged at the manually chosen 62px reading position, with the field focused and in the viewport. There were zero automated accessibility violations, no page errors or overflow; seven caret-view panels were inspected. Existing worker reuse, batch validation, 100-example/2,048-code-unit boundaries and three deliberate 150 ms interruptions per flow passed; the product deadline remains 1,200 ms. Desktop/mobile complex checks passed all three records, 100 explanation fragments and 26 exact inputs, real clipboard, reverse, focus and scroll behavior; six regex crops were inspected.

### Surviving example views

Source commit `2759546` was synchronized into the existing project folder at Pages commit `7f9a962`, whose build succeeded on 2 October 2026 (Europe/Paris). All 16 changed files are within `Regex-For-Humans/`; 20 non-Markdown resources stayed identical, and 12 of the other 13 differ only in versioned URLs. The remaining file is the tested workshop app.

Hosted example-view verification passed after Pages commit `7f9a962` built successfully: all 46 served files matched local SHA-256 values. Chrome at 1280/390px and Firefox/WebKit at 1280px repeated add/remove/renumber, preserved selections/scroll/height, native text replacement, fresh rows and recipe resets at normal width and 320px. There were zero automated accessibility violations, no page errors or overflow; seven retained-view panels were inspected. Existing worker reuse, batch validation, 100-example/2,048-code-unit boundaries and three deliberate 150 ms interruptions per flow passed; the product deadline remains 1,200 ms. Desktop/mobile complex checks passed all three records, 100 explanation fragments and 26 exact inputs, real clipboard, reverse, focus and scroll behavior; six regex crops were inspected.

### Worker reply validation

Source commit `ad615f1` was synchronized into the existing project folder at Pages commit `ea6b7e9`, whose build succeeded on 2 October 2026 (Europe/Paris). All 18 changed files are within `Regex-For-Humans/`; 19 non-Markdown resources stayed identical, and 13 of the other 14 differ only in versioned URLs. The remaining file is the tested worker controller. Other folders and the published npm preview were preserved.

Hosted worker-reply verification passed after Pages commit `ea6b7e9` built successfully: all 46 served files matched local SHA-256 values. Chrome at 1280/390px and Firefox/WebKit at 1280px passed 40 injected malformed replies, immediate retirement, safe boundaries, stale/idle handling and fresh-worker recovery. UI failure/recovery states retained rules, regex, input and focus, with zero automated accessibility violations, no page errors or 320px overflow; four failure panels were inspected. Existing worker reuse, batch validation, 100-example/2,048-code-unit boundaries and three deliberate 150 ms interruptions per flow passed; the product deadline remains 1,200 ms. Desktop/mobile complex checks passed all three records, 100 explanation fragments and 26 exact inputs, real clipboard, reverse, focus and scroll behavior; six regex crops were inspected.

### Optional compiler flag defaults

Source commit `c372862` was synchronized into the existing project folder at Pages commit `ae7d52c`, whose build succeeded on 2 October 2026 (Europe/Paris). All 17 changed files are within `Regex-For-Humans/`; 20 non-Markdown resources stayed identical, and the other 13 differ only in JSDoc or versioned URLs. Executable behavior and the published npm preview are unchanged. The README labels strict optional-flags type support as unreleased on main.

Hosted optional-flags verification passed after Pages commit `ae7d52c` built successfully: all 46 served files matched local SHA-256 values. Chrome at 1280/390px and Firefox/WebKit at 1280px verified omitted, explicit undefined and readonly defaults, exact matching, metadata reads and validation, with no page errors or 320px overflow. Existing worker recovery, batch validation, boundaries and deliberate 150 ms interruptions passed; the product deadline remains 1,200 ms. Three complex records, 100 explanation fragments and 26 exact inputs passed desktop/mobile clipboard, reverse, focus and scroll checks; six regex crops were inspected.

### Cached compile metadata

Source commit `4a266d3` was synchronized into the existing project folder at Pages commit `c8e3daa`, whose build succeeded on 2 October 2026 (Europe/Paris). All forty-six served files returned HTTP 200 and matched local SHA-256 values, including all eighteen changed project files. Twenty non-Markdown resources were unchanged; comparison of the thirteen changed resources with the prior deployment confirmed only JSDoc or versioned URL differences. Executable helper code is unchanged. Other project folders and the published npm preview were preserved; its TypeScript declaration still requires the complete compile result.

Live Chrome at 1280/390px and Firefox/WebKit at 1280px verified frozen source/flags metadata and complete results, ignored throwing segment getters, single source/flags reads, source-before-flags validation and exact matching. There were no page errors or overflow at 320px. The served README marks the wider TypeScript input as an unreleased main change, matching the separately verified Node 25/22 clean consumers.

Existing worker reuse, invalid-rule recovery, four whole-batch validation errors, 100-example/2,048-code-unit boundaries and three expensive-request interruptions passed in all four browser flows. The deliberate interruptions use a 150 ms test budget; the product deadline remains 1,200 ms. Live Chrome at both widths also passed the three complex records, 100 explanation fragments and 26 exact preloaded cases, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected.

### Complete word-class translation

Source commit `52966c6` was synchronized into the existing project folder at Pages commit `f027aab`, whose build succeeded on 2 October 2026 (Europe/Paris). All forty-six served website files returned HTTP 200 and matched local SHA-256 values, including all seventeen changed project files. Twenty non-Markdown resources were unchanged; thirteen changed, including versioned references. Other project folders and the published npm preview were preserved.

Live Chrome at 1280/390px and Firefox/WebKit at 1280px each verified 64 native word-class variants plus four visible translations with reordered/duplicated parts, negation and preserved options. Matching and copy requests passed; three nearby unsupported classes retained the rules/output, selected their range error and recovered after a supported translation. Both states had zero automated accessibility violations, no page errors or overflow at 320px; four reverse-panel crops were inspected.

Existing worker reuse, invalid-rule recovery, four whole-batch validation errors, 100-example/2,048-code-unit boundaries and three expensive-request interruptions passed in all four browser flows. The deliberate interruptions use a 150 ms test budget; the product deadline remains 1,200 ms. Live Chrome at both widths also passed the three complex records, 100 explanation fragments and 26 exact preloaded cases, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected.

### Workshop recipe validation

Source commit `7e189c6` was synchronized into the existing project folder at Pages commit `13122c9` (sixteen changed project files). Its deployment was cancelled by a subsequent shared-repository update; successor `1910367` changed only `universe/` and built successfully on 2 October 2026 (Europe/Paris). All forty-six served website files returned HTTP 200 and matched local SHA-256 values. Twenty non-Markdown resources were unchanged; thirteen changed, including versioned references. Other project folders and the published npm preview were preserved.

Live Chrome at 1280/390px and Firefox/WebKit at 1280px passed the shared recipe checks: nineteen malformed payloads retain manual editing, matching and copy requests; late failures preserve edits; valid reloads restore seventeen recipes; a valid 100-example catalogue accepts empty strings and CRLF normalized to the field limit. Failure/recovery states had zero automated accessibility violations, no page errors or overflow at 320px. Four sidebar crops were inspected.

Existing worker reuse, invalid-rule recovery, four batch-validation errors, 100-example/2,048-code-unit boundaries and three expensive-request interruptions passed in all four browser flows. These deliberate interruptions use a 150 ms test budget; the product deadline remains 1,200 ms. Live Chrome at both widths also passed the three complex records, 100 explanation fragments and 26 exact preloaded cases, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected.

### Worker message errors

Source commit `3c36f31` was synchronized into the existing project folder at Pages commit `89ad0f1`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all seventeen changed project files. Nineteen non-Markdown website resources were unchanged. Other project folders and the published npm preview were preserved.

Live Chrome at 1280/390px and Firefox/WebKit at 1280px ran the shared native-worker event regression: pending testing rejected with the existing worker error, idle workers retired, late events were ignored and valid requests recovered with exact results. The workshop showed the failure notice and stopped rows, then recovered after editing; each tested controller used three workers. Both visible states had zero automated accessibility violations, no page errors or overflow at 320px. Four example-panel crops were inspected. These checks dispatch `messageerror`; they do not induce an internal browser decoding failure.

Existing worker reuse, invalid-rule recovery, four batch-validation errors and the boundary batch of 100 examples with 2,048-code-unit values also passed in all four browser flows. Each flow interrupted three valid expensive requests and recovered through the same controller, using a 150 ms test budget while the product deadline remains 1,200 ms.

Live Chrome at 1280/390px rechecked all three complex records, 100 explanation fragments and 26 exact preloaded cases, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected; there was no page error or overflow at 320px.

### Homepage recipe validation

Source commit `0d0c227` was synchronized into the existing project folder at Pages commit `fb96114`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all five changed project files. All thirty-one other non-Markdown website resources, including the workshop, matched the previous deployed build byte for byte. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px each ran the shared failure/reload check with nine malformed payloads. Missing or malformed data, including invalid rules in the last demo, keeps every recipe button disabled after the load-error notice; the initial pattern, positive/negative matching, copy action and workshop link remain usable. Reloading valid data restores all three demos. There were no page errors or overflow at 320px, and no automated accessibility violations after finite entrance animations settled.

Separate live Chrome checks at both widths verified all three normal demos, their exact regexes and positive/negative inputs. All twelve real clipboard comparisons matched the requested rules or regex. Four fallback/recovered demo crops were inspected after transient copy feedback cleared. Existing workshop interaction checks remain recorded below.

### Nullish worker messages

Source commit `cf98409` was synchronized into the existing project folder at Pages commit `26cf090`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all sixteen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px ran the shared direct-message regression against the served worker. Each flow received two validation errors for null/undefined data and three exact valid replies from the same worker, without an uncaught error. The normal workshop summary stayed correct; there was no page error or overflow at 320px.

Live worker checks also preserved reuse across settled edits, options and the manifest recipe, cancellation on invalid rules and fresh-worker recovery. Four malformed batches retained their stable errors before matching, and boundary batches of 100 examples with 2,048-code-unit values passed. Each browser flow interrupted three valid expensive requests and recovered through the same controller; these deliberate timeout checks use a 150 ms test budget while the product deadline remains 1,200 ms.

Live Chrome at 1280/390px rechecked all three complex records, 100 explanation fragments and 26 exact preloaded cases, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected. There was no page error or overflow at 320px.

### Independent native-pattern coverage

Source commit `d0642d4` was synchronized into the existing project folder at Pages commit `71bcce6`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including both changed documentation files. All thirty-three non-Markdown website files matched the previous deployed build byte for byte. Other project folders and the published npm preview were preserved.

The served testing guide describes the independent 512-form native-regex check, its 4,096 flag variants and 31 selected strings. Its setup remains on line 5, before coverage and verification records. This publication updates testing documentation; runtime resources are unchanged and earlier live workshop interaction checks are recorded below.

### Local testing guide

Source commit `8fe307b` was synchronized into the existing project folder at Pages commit `424b442`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including both changed documentation files. All thirty-three non-Markdown website files matched the previous deployed build byte for byte. Other project folders and the published npm preview were preserved.

The served testing guide puts setup on line 5, before detailed coverage and verification records. Its individual-check block matches the complete `package.json` gate in order, including `build:pages`, `test:compat` and `build:share-card`, followed by the package dry run. Existing coverage and dated verification paragraphs are retained with reviewed reference corrections. This publication updates documentation; earlier live workshop interaction checks are recorded below.

### Partial-match positions

Source commit `63689a2` was synchronized into the existing project folder at Pages commit `73394a7`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all seventeen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px ran the shared match-feedback check. Rejected Full-mode matches report the first match's zero-based UTF-16 position after emoji, combining accents, newlines, direction controls and ordinary prefixes. Expected-negative results, accessible descriptions, line anchors, escaped matched text, empty/no-match feedback and complete-match backtracking passed. Switching Full/Search modes retained the generated regex. Four result-row/help crops were inspected; there was no overflow at 320px or page error.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the manifest's 32/33-emoji boundary. Six regex crops were inspected. Worker reuse, complete-batch validation, four stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### Bounded rule counting and error navigation

Source commit `01b38cd` was synchronized into the existing project folder at Pages commit `feed927`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all eighteen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px ran the shared source-limit regression. Four excessive inputs retained their complete text and i/s flags, showed “Over limit”, disabled copying and selected the first excess position, including an empty newline row and the second UTF-16 unit of an emoji. Instrumented splitting received only 16,384 units for the diagnostic and 16,385 for navigation. Exactly 16,384 units compiled; restoring short rules recovered with the retained flags and expected results. There was no overflow at 320px in either the error or recovered state, and no page error. Four footer/diagnostic crops were inspected. These bounds apply to application splitting; native field insertion/rendering is separate.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the manifest's 32/33-emoji boundary. Six regex crops were inspected. Worker reuse, complete-batch validation, four stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### Worker flag compatibility

Source commit `f79de8f` was synchronized into the existing project folder at Pages commit `7dc64a1`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including both changed documentation files. All thirty-three non-Markdown website files matched the previous deployed build byte for byte. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px ran the same shared worker-flag check. Each run verified 160 case/line/dot-all/astral outcomes across eight canonical flag combinations and Full/Search modes. Twenty-six malformed flag values, including a 1,048,576-unit string, retained `WORKER_ERROR` with `Invalid regex test request.`; matching recovered after every rejection. Valid requests reused one worker, while recovery after errors started fresh workers. The product deadline remains 1,200 ms. There was no overflow at 320px or page error. This documentation/test update keeps the existing site runtime; earlier complex-record and interactive validation is recorded below.

### Validated compile-result metadata

Source commit `3b7bc99` was synchronized into the existing project folder at Pages commit `3f6897f`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all seventeen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px verified the served `toRegExp` helper with changing source/flags getters. Each field was read once; the first values retained Unicode, case-insensitive and dot-all matching. An invalid source skipped the flags getter and retained the exact TypeError. There was no overflow at 320px or page error.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the manifest's 32/33-emoji boundary. Six regex crops were inspected. Worker reuse, complete-batch validation, four stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### CLI UTF-8 input guidance

Source commit `4bf00cf` was synchronized into the existing project folder at Pages commit `f3ca5b1`, whose build completed on 2 October 2026 (Europe/Paris). All forty-six website files returned HTTP 200 and matched local SHA-256 values, including all four changed documentation files. The served README explains saving the input as UTF-8 in either CLI mode and retains the explicit unreleased status of checkout-only `--reverse`. All thirty-three non-Markdown website files matched the previous deployment byte for byte. Other project folders and the published npm preview were preserved. This publication updates documentation; local CLI validation is recorded above, and the earlier live workshop interaction checks remain recorded below.

### Exact literal-limit errors

Source commit `fa5a2f9` was synchronized into the existing project folder at Pages commit `af3bf6b`, whose build completed on 2 October 2026 (Europe/Paris). Twenty-eight resources returned HTTP 200 and matched local SHA-256 values, including all sixteen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px each verified the exact error naming the 16,392-unit UTF-16 budget, including delimiters, flags and outer whitespace. Three excessive inputs retained their pasted text, rules, i/s flags, copied regex and matching examples. An emoji literal padded to exactly the limit translated successfully, cleared the error, reset the flags and focused the rules. Four reverse-panel screenshots were inspected; the message wrapped cleanly, with no overflow at 320px or page error.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected. Worker reuse, complete-batch validation, stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### Complete regex-literal input budget

Source commit `070a78f` was synchronized into the existing project folder at Pages commit `8ede10f`, whose build completed on 2 October 2026 (Europe/Paris). Twenty-eight resources returned HTTP 200 and matched local SHA-256 values, including all nineteen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px each rejected three over-budget inputs, including leading spaces, trailing non-breaking spaces and whitespace-only input. The pasted text, rules, i/s flags, copied regex and example matching remained intact. An emoji literal with padding totaling exactly 16,392 UTF-16 code units translated successfully, cleared the error, reset the flags and focused the rules. The visible limit text and four reverse-panel screenshots were inspected; there was no overflow at 320px or page error.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected. Worker reuse, complete-batch validation, stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### Exact compiler option flags

Source commit `9374163` was synchronized into the existing project folder at Pages commit `3689293`, whose build completed on 1 October 2026. Twenty-eight resources returned HTTP 200 and matched local SHA-256 values, including all eighteen changed project files and the corrected language reference. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px compiled all five allowed option strings, verified canonical flags and case/dot-all matching, and rejected duplicates, trailing line breaks and 1,048,576-code-unit flags with the same positioned error. Native-metadata translation also passed with serialization disabled, including frozen iframe regexes, matching equivalence, unchanged `lastIndex`, lookalike rejection and flag/Unicode/source diagnostic priority. No page errors were recorded.

Live desktop/mobile Chrome rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected, with no overflow at 320px. Worker reuse, complete-batch validation, stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### Native metadata without regex serialization

Source commit `70191d7` was synchronized into the existing project folder at Pages commit `9507789`, whose build completed on 1 October 2026. Twenty-seven resources returned HTTP 200 and matched local SHA-256 values, including all eighteen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px disabled `structuredClone` during reverse translation. Genuine iframe regexes, frozen metadata overrides, matching equivalence and unchanged `lastIndex` passed. Oversized inputs retained the flag/Unicode/source error priority and exact positions without serialization; lookalike objects were rejected. No page errors were recorded.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected, with no overflow at 320px. Existing worker reuse, complete-batch validation, stable errors, recovery, 100-example/2,048-code-unit boundaries and interruption of valid expensive batches passed again in Chrome, Firefox and WebKit. The deliberate timeout checks use a 150 ms test budget; the product deadline remains 1,200 ms.

### Complete example batch validation

Source commit `fb20fcc` was synchronized into the existing project folder at Pages commit `72d8157`. Its individual build reported an error; the subsequent Pages commit `3a14895` built successfully on 1 October 2026. GitHub's comparison confirms that the successful commit includes our update and only adds changes outside this project. Twenty-seven resources returned HTTP 200 and matched local SHA-256 values, including all seventeen changed project files. Other project folders and the published npm preview were preserved.

Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px each rejected four malformed Full/Search batches before an earlier pathological or compiler-generated example could time out. Null entries, duplicate IDs, oversized values and sparse entries retained the stable error; the same controller recovered and accepted 100 examples with 2,048-code-unit values and the expected IDs. Completed-worker reuse and recovery after three valid adversarial requests also passed. Those deliberate timeout checks use a 150 ms test budget; malformed-batch checks use the unchanged 1,200 ms product deadline.

Live desktop/mobile Chrome also rechecked the three complex records, 100 fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus, scroll reset/retention and the 32/33-emoji boundary. Six regex crops were inspected, with no page errors or overflow at 320px.

### Shared reverse reader and CLI instructions

Source commit `c3245c7` was synchronized into the existing project folder at Pages commit `1a19276`, whose build completed on 1 October 2026. The workshop now loads the shared regex-literal reader, and its served README includes the source-checkout CLI reverse instructions with their explicit unreleased status. Twenty-seven resources returned HTTP 200 and matched local SHA-256 values, including all nineteen changed Pages files. Other project folders were preserved; the published npm preview is unchanged.

Live desktop/mobile Chrome rechecked all three complex records, 100 explanation fragments, 26 exact inputs, source selection, real clipboard, reverse translation, focus and scroll reset, retained reading positions, optional values, case folding and the 32/33-emoji boundary. Six regex crops were inspected; there was no overflow at 320px or page error. Live worker checks also passed in Chrome at 1280/390px and Firefox/WebKit at 1280px: settled checks reused one worker, invalid rules discarded it, and recovery started fresh. Each flow recovered after three adversarial requests timed out in already loaded workers, with all workers terminated by timeout or final cleanup. Those adversarial checks use a 150 ms test budget; the product's 1,200 ms deadline is unchanged.

### Completed example workers

Source commit `6e2d969` was synchronized into the existing project folder at Pages commit `8b4fdda`, whose build completed on 1 October 2026. Live Chrome checks at 1280/390px and Firefox/WebKit checks at 1280px each required one worker across settled example edits, i/s option changes and the complete manifest recipe. Invalid rules terminated it, and valid rules recovered with a fresh worker. In each browser flow, three pathological/compiler-generated requests ran in already loaded workers, timed out and recovered through the same controller; all four workers were terminated by timeout or final cleanup. These adversarial checks use a 150 ms test budget; the product's 1,200 ms deadline is unchanged.

Live desktop/mobile Chrome also rechecked the npm link, all three complex record recipes, 100 explanation fragments, 26 exact inputs and outcomes, source selection, real clipboard, reverse translation, scroll/focus reset and retained reading positions, optional values, case folding and the 32/33-emoji boundary. Twenty-six files returned HTTP 200 and matched local SHA-256 values, including all eighteen changed Pages files. Six regex crops were inspected; there was no overflow at 320px or page error. Other project folders were preserved. This updates the workshop; the published npm tarball remains the immutable preview recorded below.

### npm preview and regex beginning

The npm installation link and generated-regex view fix were synchronized from source commit `d96fe11` into the existing project folder at Pages commit `47b7953`, whose build completed on 1 October 2026. Live desktop/mobile Chrome checks verified the published npm version link and install command, all three complex record cards, 100 explanation fragments and 26 exact preloaded inputs. Recipe reloads and successful reverse translation reset the rules, explanation list and regex left edge, preserving matching and the expected button/editor focus. Valid rule edits, i/s changes and unsupported captures retained the reading positions; supported translation recovered. Source-line selection, real clipboard contents, access-log case folding, telemetry optional values/lane rejection and the manifest's 32/33-emoji boundary passed. Twenty-three served files returned HTTP 200 and matched local SHA-256 values, including all nineteen changed Pages files. Six regex crops and two homepage hero captures were inspected across both viewports. At 320px there was no page overflow, and the browser recorded no page errors.

### First-rule explanations

The explanation-view fix was synchronized into the existing project folder at Pages commit `3953154`, whose build completed on 1 October 2026. Live desktop/mobile Chrome checks followed all three complex record cards and verified 100 fragments, 26 exact preloaded inputs and outcomes, notes, source-line selection and actual clipboard contents. Starting from a scrolled explanation list, successful reverse translation and keyboard recipe reloading returned both the rules and explanations to the first rule, preserving matching and the expected editor/button focus. Valid rule edits and i/s option changes retained the explanation reading position. Unsupported captures retained the current rules, regex and explanation position; a supported retry recovered. Access-log case folding, telemetry optional-value combinations/lane rejection and the manifest's 32/33-emoji boundary still worked. Six explanation screenshots were captured and inspected across both viewports. There was no page overflow at 320px or page error. Twenty-one served files returned HTTP 200 and matched local SHA-256 values, covering all fifteen changed Pages files and six unchanged reference files.

### Complex record recipes

The access-log and telemetry recipes were synchronized into the existing project folder at Pages commit `f4c3f14`, whose build completed on 1 October 2026. Live desktop/mobile Chrome checks followed all three complex record homepage cards and verified 100 explanation fragments, 26 exact preloaded inputs and their outcomes, recipe notes, source-line selection and actual clipboard contents. Reverse translation retained matching; keyboard reloading restored the original rules/cases, focused the recipe button and left the rule editor's caret/scroll at the beginning. Checks verified access-log case folding, all four telemetry optional-value combinations and lane rejection, plus the manifest's 32/33-emoji boundary. Unsupported captures preserved the rules, and a supported retry recovered. Access-log and telemetry screenshots were captured and inspected on both viewports. There was no overflow at 320px or page error. Thirteen served files returned HTTP 200 and matched local SHA-256 values.

### Translation confirmation

The feedback fix was synchronized into the existing project folder at Pages commit `bccee28`, whose build completed on 1 October 2026. Live desktop/mobile Chrome checks verified confirmation clearing after rule edits, both i/s option changes and switching recipes. Editing examples, changing match mode and copying the regex retained the confirmation. An unsupported capture kept its error, accessible description and exact source selection after invalid rule edits, option changes and recipe reloading; a supported retry recovered. The manifest retained its 19 explanation fragments and nine passing outcomes, working clipboard, source-line selection and first-rule caret/scroll. Screenshots were captured and inspected, with no overflow at 320px or page errors. Thirteen served files returned HTTP 200 and matched local SHA-256 values.

### First-rule editor view

The editor view fix was synchronized into the existing project folder at Pages commit `3c751c6`, whose build completed on 1 October 2026. Live desktop/mobile Chrome checks verified that initial loading, reverse translation and keyboard recipe reloading leave the caret and scroll at the beginning of the rules. Translation focuses the editor; recipe reloading retains button focus. The manifest still showed all 19 explanation fragments and nine passing outcomes, with working clipboard copying, source-line selection and the 32/33-emoji boundary. Screenshots were captured and inspected. There was no overflow at 320px or page error. Thirteen served files returned HTTP 200 and matched local SHA-256 values.

### Complete artifact-manifest recipe

The manifest recipe was synchronized into the existing project folder at Pages commit `e793735`, whose build completed on 1 October 2026. Live desktop/mobile checks followed its homepage card and verified the exact 19 rules, all explanation fragments and all nine preloaded inputs and outcomes. The path explanation selected its source line, the actual clipboard contained the generated regex, and Ctrl + Enter translated it back with correct focus and matching. A project name of 32 emoji matched; 33 did not. Reselecting the recipe restored the original rules and cases. There was no overflow at 320px or page error. Thirteen served website, workshop, fixture and documentation files returned HTTP 200 and matched local SHA-256 values.

### Explicit word-character names

The explicit word-character names and readable identifier examples were synchronized into the existing project folder at Pages commit `ef3c9d5`, whose build completed on 1 October 2026. Live desktop/mobile checks imported the served API and compared eight repetition forms across all eight supported flag combinations. All 1,152 native match-array/index comparisons per viewport agreed, including Unicode case-folding equivalents, emoji and lone surrogates. The username recipe displayed the new wording with every example behaving as expected. Interactive checks verified case folding, rejected spaces, hyphens, `é` and emoji, exposed a useful `words` repair hint and recovered the copy action. The existing `word`, `not word` and reverse output stayed compatible. There was no overflow at 320px or page error. Thirteen served website, workshop, fixture and documentation files returned HTTP 200 and matched local SHA-256 values. All four complex examples also compiled, explained and translated correctly, with 34 browser-compatible input cases per viewport and captured-group rejection preserved.

### Equivalent path exclusions

Equivalent path-class translation was synchronized into the existing project folder at Pages commit `019c2f9`, whose build completed on 1 October 2026. Live desktop/mobile checks imported the served API and translated three ordinary, reordered/duplicated and padded-escape spellings across all eight supported flag combinations. All 432 native match-array/index comparisons per viewport agreed with rebuilt regexes; flags and input `lastIndex` stayed unchanged. Each spelling also produced the readable rule through the actual workshop, with correct focus, friendly explanation, Unicode matching and separator rejection. An unsupported capture still preserved the current rules. There was no overflow at 320px or page error. Eleven served website, workshop, translator and documentation files returned HTTP 200 and matched local SHA-256 values. All four complex examples also compiled, explained and translated correctly on the live site, with 34 browser-compatible input cases per viewport and captured-group rejection preserved.

### Complex examples and readable paths

Four complete format examples and the readable path rule were synchronized into the existing project folder at Pages commit `35cd517`, whose build completed on 1 October 2026. Live desktop/mobile checks compiled every example, verified its explanation fragments and translated it back through Ctrl + Enter with correct focus. All 34 browser-compatible accepted/rejected cases per viewport passed; the exact CRLF rejection remains covered by Node because textareas normalize line endings. Named captures still reported their unsupported-feature diagnostic through Meta + Enter. The simplified filename recipe showed the readable rule and friendly explanation, accepted a Unicode filename and rejected a slash separator. Nine served website, workshop and documentation files returned HTTP 200 and matched local SHA-256 values.

### Leading-zero Unicode escapes

Leading-zero code-point escapes were synchronized into the existing project folder at Pages commit `fef01d1`, whose build completed on 1 October 2026. Live desktop/mobile checks translated 48 frozen local/iframe regexes per viewport across eight supported flag combinations, using padded escapes in literals, character lists and repeated emoji groups. Their throwing metadata/protocol getters and matching methods were never called, and `lastIndex` stayed unchanged. All 480 native match text/index comparisons per viewport agreed with rebuilt regexes; eight unsupported-input diagnostics and four non-RegExp/lookalike rejections remained correct. An unsupported capture after a padded emoji escape selected the opening parenthesis through keyboard navigation; a repaired padded literal group focused the editor and matched correctly. The parent workshop output stayed unchanged, with no overflow at 320px or page errors. The served translator, README, language contract, testing guide, changelog and syntax guide returned HTTP 200 and matched local SHA-256 values.

### Matching protocol getters

Earlier matching-protocol bypass was synchronized into the existing project folder at Pages commit `54eb337`, whose build completed on 1 October 2026. Live desktop/mobile checks translated 48 frozen local/iframe regexes per viewport with throwing metadata getters, matching methods and `Symbol.match` getters across all eight supported flag combinations. Each translation retained the native pattern and flags without calling those overrides or changing `lastIndex`; 384 native match text/index comparisons per viewport agreed with rebuilt regexes. Subclass overrides preserved eight unsupported-input diagnostics, and four non-RegExp/lookalike inputs were rejected. The parent workshop output stayed unchanged; reverse-error keyboard navigation and a supported repair retained correct focus and matching. There was no overflow at 320px or page error. The served translator, README, language contract, testing guide and changelog returned HTTP 200 and matched local SHA-256 values.

### Native regex metadata

Earlier stored native regex metadata was synchronized into the existing project folder at Pages commit `166444f`, whose build completed on 1 October 2026. Live desktop/mobile checks translated 48 local/iframe regexes with throwing metadata getters and matching methods across eight supported flag combinations. Frozen inputs kept their `lastIndex`; 384 native match text/index comparisons per viewport agreed with rebuilt regexes. Subclass source overrides did not replace the stored pattern, eight overridden-input diagnostics retained their codes and four non-RegExp/lookalike inputs were rejected. The parent workshop output stayed unchanged; reverse-error keyboard navigation, repair, focus and case-insensitive matching still worked. There was no overflow at 320px or page error. The served translator, README, language contract, testing guide and changelog returned HTTP 200 and matched local SHA-256 values.

### Cross-context regexes

Earlier cross-context RegExp acceptance was synchronized into the existing project folder at Pages commit `44398fb`, whose build completed on 1 October 2026. Live desktop/mobile checks imported the served API and translated 24 genuine iframe regexes per viewport across eight supported flag combinations. Their rules and flags matched same-context translations; 192 native match text/index comparisons per viewport agreed with rebuilt regexes. Translation preserved `lastIndex`, rejected four non-RegExp/lookalike inputs and left the parent workshop output unchanged. Reverse-error keyboard navigation and supported repair still worked; the page had no overflow at 320px or page errors. The served translator, README, language contract, testing guide and changelog returned HTTP 200 and matched local SHA-256 values.

### Reverse error navigation

Earlier reverse-error navigation was synchronized into the existing Regex-For-Humans folder at Pages commit `32a72d5`, whose build completed on 1 October 2026. Live desktop/mobile keyboard checks verified selection at six unsupported syntax errors: alternation, named captures, nested lookahead, ranges and lazy quantifiers, including emoji, leading whitespace and native CRLF normalization. A long wrapped pattern scrolled within its field, and a field enlarged to 1,400px revealed the selected row in the page viewport. Each syntax error preserved edited rules, i/s options and the copied regex. Edits removed the stale action; malformed literals, flag errors and whole-translation limits kept explanatory feedback. A supported repair cleared the invalid state, focused the editor and matched correctly. The served workshop HTML, app module and stylesheet matched their local SHA-256 values. Desktop/mobile screenshots of the error control were inspected. The page had no horizontal overflow at 320px and no page errors. The syntax guide, README and language contract returned HTTP 200 and matched their local content hashes.

### Earlier workshop checks

Earlier live checks verified precise group diagnostics at `24d379b`, empty groups at `9a715a4`, repeated-list explanations at `a2024cc`, alternation diagnostics at `ace0da8`, literal hyphens at `845bcff`, control-letter support at `7de2793`, equivalent ASCII range orders at `6219331`, reverse-input validation states at `5c6c751`, startup readiness at `54c91fb`, regex-literal line-break validation at `55c45cd`, both reverse-output limits at `8e60b91`, Unicode reverse translation and incomplete repetition repairs; local browser tests covered all 14 recipes.

The updated site was published into the existing `Regex-For-Humans/` folder of `OthmaneBlial.github.io` at Pages commit `23da03f`. Its build completed successfully; all 46 served files match the local site by SHA-256. The live workshop shows `0.1.0-dev.2` and translates `/^.[^]$/u` into rules that match `A\n` and reject `\nA`. The project repository's GitHub Actions remains disabled.

This is a checked development deployment, not a stable release.

## Historical registry and release status

The source checkout now adds lazy repetition and all four positive/negative lookahead/lookbehind forms in both directions; those additions are unreleased beyond npm `0.1.0-dev.4`. All local verification components pass: 263 Node tests, 304 Chromium desktop/mobile workshop checks, 74 Firefox/WebKit checks, 64 homepage checks, lint/types/docs, builds, a clean JavaScript/TypeScript consumer and an audit with zero vulnerabilities. All 38 focused Node 22 checks and its separate clean package consumer pass too. The first full command needed two compatibility-fixture selection updates; the complete compatibility suite and remaining stages then pass separately. These local package candidates are not the published archive below; no registry upload or tag update is claimed for this source milestone.

The [0.1.0-dev.4 npm preview](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.4) is published from annotated tag [`v0.1.0-dev.4`](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.4), resolving to `af7029176f0c28669cbb1352f2137d07d3a95ddf`. Both `preview` and `latest` point to dev.4. It includes groups/captures, backward references, ordered alternatives, their supported reverse translations, the CLI and TypeScript declarations. Capture exploration and multiple search matches are browser-workshop features.

The exact retained archive is 192,138 bytes with 38 files, tested in clean JavaScript/TypeScript consumers on Node 25.9.0 and Node 22.23.3. Its SHA-256 is `06dadc8d4d06aa8d00326d07678b345364c7a037754bbfb3174681b7b4562ce2`; npm SHA-1 is `8de04ec95d20eb4105427de43c1f4c6a03eaccde`, and registry integrity is `sha512-V2HZuQ4hiWQRZmrLkLD5RcU9pylwutaoT86RzAXmyJsAJ+wjnMgg6vs6/aUrR/f0vjQ/pCuHM+k7bm1c7ZR3rQ==`. The downloaded npm and GitHub prerelease archives match the retained file byte for byte, and GitHub's `SHA256SUMS` matches too. Runtime files and package metadata are unchanged from the compiler/browser-verified candidate; the final archive adds verified documentation records.

Fresh-cache public `@preview` installs on both Node runtimes and a default installation on Node 25 each pass eighteen recipes, 704 native forward/reverse comparisons, 36 CLI directions, ordered-alternative capture checks, the README date example and the version guard. Initial version-endpoint reads returned 404 during propagation; later public installs and canonical tarball downloads passed. This is a development prerelease, with no runtime dependencies or standalone OS executable. GitHub Actions remains disabled; stable support, human usability, screen-reader and independent language reviews remain open. The immutable archive retains its preparation snapshot; current publication evidence is recorded here.

The third development preview, [regex-for-humans@0.1.0-dev.3](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.3), is published from annotated tag [`v0.1.0-dev.3`](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.3) at source commit `45d3eb9`. The prerelease attaches the same 110,701-byte archive as npm plus `SHA256SUMS`. Its SHA-256 is `63f61a5ea7bc9575306dac1c1dfef07c30bbf6652c988e3beb91d064b5bba5ba`; npm SHA-1 is `b5589b20045a47dd81603731a0e1bdc7d540953a`, and registry SHA-512 integrity is `sha512-KWvj2kEWqcANQHcEDKyCydqgmIv4E0mMWrsqzjpI54zKRaNaly3ML28DIpZXgUv6fu9W9Wmq+BQMzs/ltdd2jw==`. The downloaded GitHub assets and registry tarball match the retained local files byte for byte. At that release, both npm tags, `preview` and `latest`, pointed to `0.1.0-dev.3`. Fresh consumers installed through `@preview` and verified the CLI/library README examples on Node 25.9.0 and Node 22.23.3. This remains a development prerelease; human usability, screen-reader and stable-release gates remain open.

The existing `.io` site folder was updated at [Pages commit `d226658`](https://github.com/OthmaneBlial/OthmaneBlial.github.io/commit/d22665851b58dbbd673db273edd3c5a07a5d7298). Pages build `36990052689` completed successfully. The live homepage links the dev.3 npm package; the live workshop reports `0.1.0-dev.3` and displays a partial match with its context highlighted in Chrome at 1280 px. At 390 px and 320 px the document has no horizontal overflow; the observed browser console and page-error logs were empty.

The second development preview, [regex-for-humans@0.1.0-dev.2](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.2), was published locally on 2 October 2026 from checked release tag `v0.1.0-dev.2` at source commit `ad638fe`. The [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.2) contains the exact 109,481-byte, 26-file archive and `SHA256SUMS`. The archive SHA-256 is `b339d10aaad509485842af00babca8ab299c7c2adc023407f479ed6f8296ade8`; its npm SHA-1 is `f44836a9bfc0269a42d73c03cb5e3c733656ef64` and registry SHA-512 integrity is `sha512-iCa90804VVw6e/BPpG06Pz6B256YOIgRlcxEUZo0FJWs1pv8gV1pUmvRLiJ5XYmvJ9hGeXSh0RfhSICyxDYF7g==`. The downloaded registry and GitHub archives match the retained local tarball byte for byte, and GitHub's checksum file matches. At that release, npm tags `preview` and `latest` both pointed to `0.1.0-dev.2`. A fresh-cache registry installation passed the `[^]` API and multiline matching smoke check under Node 25.9.0 and 22.23.3. The release remains a prerelease; stable support and human review gates remain open.

The second development preview, [regex-for-humans@0.1.0-dev.1](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.1), was published locally on 2 October 2026 at the maintainer’s request. Its [GitHub prerelease](https://github.com/OthmaneBlial/Regex-For-Humans/releases/tag/v0.1.0-dev.1) uses annotated tag `v0.1.0-dev.1`, resolving to fully tested source commit `c1bae7c`. The exact retained tarball is 106,631 bytes with 26 files; its SHA-256 is `2b0f0cd5f9ce7c0c0a0efedc3181428ebaeed6edb497fe58eb4a63a39d7812e1`. The registry’s SHA-512 integrity matches the same bytes. GitHub includes the archive and its SHA256SUMS, and both downloaded assets are byte-identical to the local files in `artifacts/npm-0.1.0-dev.1/`. This archive retains the pre-upload preparation snapshot; the current guide records the publication checks below.

Public release verification passed on 2 October 2026: npm serves `regex-for-humans@0.1.0-dev.1`, with both `preview` and `latest` tags at that version. The registry tarball and both downloaded GitHub prerelease assets match the retained archive and SHA256SUMS exactly. Fresh caches/directories verified default npm installation on Node 25.9.0, preview-tag installation on Node 22.23.3, all eighteen recipes/176 inputs/704 option variants per runtime, 36 CLI directions, the installed README example and strict types. Standalone npx reverse translation also passed in an empty directory. Initial registry reads returned 404 and a first default install obtained the old version during propagation; version guards caught this before the successful fresh runs. The npx harness initially rejected npm’s own update notice; suppressing only that wrapper notice retained exact CLI-output checks. GitHub’s annotated `v0.1.0-dev.1` tag resolves to `c1bae7c`, and the release is explicitly marked as a prerelease. GitHub Actions stays disabled; stable-release and human-review gates remain open.

This preview adds CLI reverse translation, TypeScript metadata/optional-flag corrections and eighteen shared workshop recipes including the UUID shape. It requires Node.js 22+, has no runtime dependencies and does not include standalone OS executables. To roll back an installation, pin the original `regex-for-humans@0.1.0-dev`; immutable old versions remain available. Hosted-site evidence is recorded separately above.

The first development preview, [regex-for-humans@0.1.0-dev](https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev), was published locally on 1 October 2026 from source commit `0b94f9c` using the `othmaneblial` account. At that publication, the registry reported public access and both `preview` and `latest` tags at `0.1.0-dev`. The exact clean-consumer-tested tarball is 80,466 bytes, contains 25 files and matches the downloaded registry tarball byte for byte (including SHA-512 integrity). Its SHA-256 is `fd1723f4e35ce4e6bf4c9ba8e208e356335f92561920932531f84f3ee3bad80d`; the retained local copy is `artifacts/npm-0.1.0-dev/regex-for-humans-0.1.0-dev.tgz`.

Fresh public-registry installations verified both `npm install regex-for-humans` and `npm install regex-for-humans@preview`, plus the README's standalone `npx --yes --package=regex-for-humans@preview regex-for-humans` command. Installed CLI checks passed for version, stdin and positioned JSON errors. The exact README library example and strict TypeScript declarations worked; all 17 recipe patterns and 163 accepted/rejected inputs retained direct and reverse matching under Node 25.9.0 and Node 22.23.3. Early post-upload reads returned 404; later canonical download and fresh-install checks passed. This is a development preview requiring Node.js 22+, with no runtime dependencies or standalone OS executable. GitHub Actions remains disabled; human review and stable-release gates remain open.

The preview now provides the versioned npm library and `regex-for-humans` CLI, alongside the static browser workshop. The current hosted site is a development preview, not a stable release. The package requires Node.js 22 or newer. GitHub Actions is disabled for this repository. Local verification can preserve the exact tested tarball with `PACK_OUTPUT_DIR=artifacts npm run test:package`; that tarball is not a substitute for a published registry version.

## Standalone binary decision

No standalone OS executable is planned for the first release. The present product is a small JavaScript CLI and library, and there is no measured evidence yet that its target users need a bundled Node runtime. Maintaining separate Windows, macOS and Linux executables would add build, signature, platform smoke-test and update obligations. This is a provisional decision pending the three new-user sessions in [USABILITY-STUDY.md](USABILITY-STUDY.md). Ask whether Node installation is a practical barrier, which OS/architecture is involved, and whether a browser-only or npm route meets the need. Record the observations before closing roadmap task 5.3.

If those sessions show a concrete standalone need, select a maintained packaging tool, build and verify each claimed OS/architecture, smoke the exact downloadable files on each target, and publish SHA-256 checksums with the release. Do not link a binary that has not been built and verified. If the no-binary decision holds, state it explicitly in the release notes and keep the Node/npm and browser routes prominent.
