@@ -45,19 +45,46 @@ jobs:
           RESULT: ${{ needs.test.result }}
         run: test "$RESULT" = success
 
+  publish:
+    name: Publish beta package
+    needs: verify
+    if: github.ref_type == 'tag' && startsWith(github.ref_name, 'v')
+    runs-on: ubuntu-latest
+    environment: npm
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          registry-url: https://registry.npmjs.org
+      - run: npm ci
+      - run: node scripts/validate-release.mjs
+      - run: npm run build
+      - run: npm run test:package
+      - name: Publish verified beta with provenance
+        run: npm publish --tag beta --access public --provenance
+        env:
+          # Used only to bootstrap the first package publication, then removed.
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_BOOTSTRAP_TOKEN }}
+
   deploy:
     name: Deploy website
-    needs: verify
-    if: github.event_name != 'pull_request'
+    needs: [verify, publish]
+    if: always() && needs.verify.result == 'success' && github.event_name != 'pull_request' && ((github.ref_type == 'tag' && needs.publish.result == 'success') || (github.ref_type != 'tag' && needs.publish.result == 'skipped'))
     runs-on: ubuntu-latest
     environment:
-      name: ${{ github.ref == 'refs/heads/main' && 'production' || 'preview' }}
+      name: ${{ (github.ref == 'refs/heads/main' || github.ref_type == 'tag') && 'production' || 'preview' }}
       url: ${{ steps.deploy.outputs.url }}
     env:
       VERCEL_ORG_ID: ${{ vars.VERCEL_ORG_ID }}
       VERCEL_PROJECT_ID: ${{ vars.VERCEL_PROJECT_ID }}
       VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
-      DEPLOY_ENVIRONMENT: ${{ github.ref == 'refs/heads/main' && 'production' || 'preview' }}
+      DEPLOY_ENVIRONMENT: ${{ (github.ref == 'refs/heads/main' || github.ref_type == 'tag') && 'production' || 'preview' }}
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
 
@@ -2,7 +2,7 @@
 
 A structured JavaScript data inspector for React: inspect the value you actually have.
 
-**Alpha package, not yet published to npm.** [Website](https://react-data-inspector.nipesolutions.com) · [Playground](https://react-data-inspector.nipesolutions.com/playground) · [Documentation](https://react-data-inspector.nipesolutions.com/docs). Run `npm install && npm run dev` locally. See [release readiness](docs/release-readiness.md) before production adoption.
+**Beta release channel.** [Website](https://react-data-inspector.nipesolutions.com) · [Playground](https://react-data-inspector.nipesolutions.com/playground) · [Documentation](https://react-data-inspector.nipesolutions.com/docs). Run `npm install && npm run dev` locally. See [release readiness](docs/release-readiness.md) before production adoption.
 
 ```tsx
 import { DataInspector } from '@nipe-solutions/react-data-inspector'
@@ -11,7 +11,11 @@ import '@nipe-solutions/react-data-inspector/styles.css'
 ;<DataInspector value={data} />
 ```
 
-Until publication, run `npm run build && npm pack` and install the generated tarball in your application.
+Install the beta release:
+
+```sh
+npm install @nipe-solutions/react-data-inspector@beta
+```
 
 ## Why this exists
 
@@ -49,7 +53,7 @@ Prefer quoted keys and object-viewer syntax? Set `presentation="classic"`; see [
 
 See the [compiled customization examples](examples/customization.tsx), [API reference](docs/api.md), [architecture and type matrix](docs/architecture.md), and [performance methodology](benchmarks/README.md).
 
-The alpha is read-only; editing is not part of the public API. Getters are not evaluated, promises are not awaited, functions are not executed, and WeakMap/WeakSet contents remain opaque. Collection paths are not presented as JSON Pointers.
+The beta is read-only; editing is not part of the public API. Getters are not evaluated, promises are not awaited, functions are not executed, and WeakMap/WeakSet contents remain opaque. Collection paths are not presented as JSON Pointers.
 
 ## Development
 
 
@@ -38,6 +38,7 @@ const cases: Record<string, Omit<DataInspectorProps, 'presentation'>> = {
 const results = Object.entries(cases).map(([name, props]) => {
   const timings = { inspector: [] as number[], classic: [] as number[] }
   const rowCounts = { inspector: 0, classic: 0 }
+  const closingLines = { inspector: 0, classic: 0 }
   for (let iteration = -1; iteration < samples; iteration++) {
     const order =
       iteration % 2 === 0
@@ -50,6 +51,9 @@ const results = Object.entries(cases).map(([name, props]) => {
       )
       const elapsed = performance.now() - start
       rowCounts[presentation] = (html.match(/data-rdi-node=/g) ?? []).length
+      closingLines[presentation] = (
+        html.match(/data-rdi-closing=/g) ?? []
+      ).length
       if (iteration >= 0) timings[presentation].push(elapsed)
     }
   }
@@ -66,6 +70,11 @@ const results = Object.entries(cases).map(([name, props]) => {
   return {
     name,
     dataRows: rowCounts.inspector,
+    visualLines: {
+      inspector: rowCounts.inspector + closingLines.inspector,
+      classic: rowCounts.classic + closingLines.classic,
+    },
+    closingLines,
     inspector: summarize(timings.inspector),
     classic: summarize(timings.classic),
   }
@@ -82,7 +91,7 @@ process.stdout.write(
         cpu: cpus()[0]?.model,
       },
       methodology:
-        'Paired in-process React SSR; one warmup per mode and fixture, ten measured samples, alternating mode order. Dataset construction excluded. Each render creates the same model and visible rows. No client windowing, scrolling, or browser timings. Deep fixture reaches the default maximum depth (100); wide and 500k cases use default grouping. Open-range fixture explicitly expands the first 10k range and first 100-value subrange. Customization, themes, and actions use defaults. Samples are descriptive, not timing assertions.',
+        'Paired in-process React SSR; one warmup per mode and fixture, ten measured samples, alternating mode order. Dataset construction excluded. Each render creates the same model and data rows. Classic adds separate decorative closing lines; visual-line counts are reported independently. No client windowing, scrolling, or browser timings. Deep fixture reaches the default maximum depth (100); wide and 500k cases use default grouping. Open-range fixture explicitly expands the first 10k range and first 100-value subrange. Customization, themes, and actions use defaults. Samples are descriptive, not timing assertions.',
       results,
     },
     null,
 
@@ -99,6 +99,6 @@ The canonical [styling reference](https://react-data-inspector.nipesolutions.com
 
 ## Presentation
 
-`presentation="inspector"` is the default. `presentation="classic"` changes built-in visual notation using quoted property keys and balanced inline container delimiters. It adds no closing-delimiter rows or selectable synthetic punctuation. Both presentations share paths, graph identity, search, selection, expansion, actions, grouping, virtualization, and SSR behavior.
+`presentation="inspector"` is the default. `presentation="classic"` changes built-in visual notation using quoted property keys and multiline container delimiters. Closing-delimiter lines are decorative and aria-hidden; they add visual offsets but no selectable data nodes. Both presentations share paths, graph identity, search, selection, expansion, actions, grouping, virtualization, and SSR behavior.
 
 Classic output is not serialized JSON or executable JavaScript. Non-JSON type summaries and separately addressed Map key/value rows retain their meaning. See [presentation modes](https://react-data-inspector.nipesolutions.com/guides/presentation) for examples and customization boundaries.
@@ -35,7 +35,7 @@ This audit maps the product deliverables to the implementation and honest releas
 | 29. Limitations              | [Architecture](architecture.md) and [readiness](release-readiness.md)                                           |
 | 30. Roadmap                  | Inspection-first; editing/continuation/integration after audited core                                           |
 | 31. Naming                   | Verified NIPE conventions, public GitHub repository and unpublished npm candidate                               |
-| 32. Readiness                | **PRIVATE PREVIEW READY**; no public-beta or stable claim                                                       |
+| 32. Readiness                | **Beta distribution**; outstanding manual production-qualification audits                                       |
 
 ## Mandatory customization scenarios
 
@@ -55,6 +55,6 @@ Cycle and shared-reference tests distinguish semantics without recursion; getter
 
 ## Accessibility audit
 
-Keyboard-only behavior, collapse/focus restoration, selection, search, actions, RTL/mobile and windowed active descendants have automated interaction coverage and live browser inspection. Axe passes the default and dark examples. No human screen-reader audit was performed. Editing accessibility is not applicable to this read-only alpha. See the public-beta blockers before describing the project as production-ready.
+Keyboard-only behavior, collapse/focus restoration, selection, search, actions, RTL/mobile and windowed active descendants have automated interaction coverage and live browser inspection. Axe passes the default and dark examples. No human screen-reader audit was performed. Editing accessibility is not applicable to this read-only beta. See the remaining production-qualification work before describing the project as production-ready.
 
 The dedicated [playground](playground.md) now includes externally updated data, typed-value scenarios, styling controls, lazy children and opt-in performance measurements. Standalone live examples are verified against the packed package.
@@ -13,7 +13,7 @@ The website uses the `react-data-inspector` project in the NIPE Solutions Vercel
 
 The GitHub `VERCEL_TOKEN` secret is scoped to this project and expires on 2027-09-07. Rotate it before expiry through Vercel and update the GitHub secret. `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` are repository variables. Optional diagnostic artifact uploads are non-blocking when GitHub storage is unavailable; tests, builds and packaging remain required.
 
-The website deployment does not publish the npm package or change its alpha classification. Application secrets are unnecessary for this static site. Keep `.vercel/` local and ignored.
+Version-tag builds publish the beta npm package after both React matrix jobs pass, then deploy the website. Ordinary branch pushes deploy the site without publishing packages. Application secrets are unnecessary for this static site. Keep `.vercel/` local and ignored.
 
 ## Domain
 
@@ -31,4 +31,4 @@ Check the custom hostname, a direct `/playground` URL, JavaScript/CSS asset resp
 
 `website/articles.ts` is the shared route and documentation registry. Article Markdown feeds navigation, rendered HTML and the sitemap; the API article imports `docs/api.md` directly. Each route gets a title, description, canonical URL, OpenGraph and social metadata. `social.svg` is the source for the 1200 × 630 social PNG. `npm run test:website` checks static metadata, internal links and compiles the React Data Inspector documentation snippets. Browser tests run against the production build, including JavaScript-disabled documentation and hydration.
 
-Registry publication is verified on each website build; network/registry errors fail the build instead of publishing stale installation claims. After an npm release, trigger the Verify workflow on main to refresh installation copy. The website does not publish packages.
+Registry publication is verified on each website build; network/registry errors fail the build instead of publishing stale installation claims. After successful npm publication, the same workflow rebuilds the website against registry metadata. A failed publication prevents the release deployment. See [releasing](releasing.md).
@@ -1,8 +1,8 @@
 # Release readiness
 
-Classification: **PRIVATE PREVIEW READY**
+Distribution: **beta**. Manual production-qualification audits remain open.
 
-Assessed 2026-09-07. Version: 0.1.0-alpha.0. The package is not published to npm. Website hosting and automatic deployment are configured separately; see [deployment](deployment.md).
+Assessed 2026-09-07. Version: 0.1.0-beta.0. Beta publication is performed by the verified version-tag workflow; check the [npm beta channel](https://www.npmjs.com/package/@nipe-solutions/react-data-inspector?activeTab=versions) and [release workflow](https://github.com/NIPE-Solutions/react-data-inspector/actions/workflows/ci.yml) for registry status. See [deployment](deployment.md).
 
 ## Verified
 
@@ -29,20 +29,20 @@ Opening the 500,000-item array produces 51 first-level model rows with defaults.
 
 The forced-GC experiment observed all 50 discarded model roots collected. It does not establish absence of leaks in mounted React components, browser heaps or application-held callback contexts. No frame-loss or retained-browser-heap claim is made.
 
-## Public-beta blockers
+## Remaining production-qualification work
 
 1. Perform and record actual VoiceOver/Safari and NVDA/Firefox or Chrome navigation, selection, search, actions and virtualization audits. Keyboard automation and axe are insufficient.
 2. Dogfood through the public API in an application such as source metadata/job payload inspection. No application integration has been performed.
 3. Audit mounted-browser retained heaps across repeated input replacement/unmount, and scrolling frame timing on representative hardware.
 4. Validate current desktop/mobile Safari and current evergreen browser versions beyond the locally available pinned WebKit.
-5. Review the deliberately limited alpha contracts: uniform-height virtualization, first 10,000 Map/Set entries, indexed-only arrays, bounded search/reveal and discovery-scoped reference targets.
+5. Review the deliberately limited beta contracts: uniform-height virtualization, first 10,000 Map/Set entries, indexed-only arrays, bounded search/reveal and discovery-scoped reference targets.
 
 ## Deferred features
 
 Editing, add/remove proposals, JSON Patch conversion, collection continuation, prototype inspection and specialized binary/DOM views are not implemented. There is no editing prop that implies otherwise. See the current [public API](api.md) and [limitations](https://react-data-inspector.nipesolutions.com/limitations).
 
 ## Naming and publication
 
-The public GitHub repository is `NIPE-Solutions/react-data-inspector`, matching this checkout's origin. The npm registry returned 404 for `@nipe-solutions/react-data-inspector` on 2026-09-07. The name follows neighboring NIPE packages; it is not reserved and publication permission has not been proven by a publish attempt.
+The public GitHub repository and npm package are `NIPE-Solutions/react-data-inspector` and `@nipe-solutions/react-data-inspector`. The first beta is `0.1.0-beta.0`, published with dist-tag `beta`; a beta version does not claim stable API or completion of the manual audits above.
 
-`react-data-inspector.nipesolutions.com` follows the NIPE docs-host pattern. Its GoDaddy CNAME points to the Vercel project in the NIPE Solutions team. GitHub Actions deploys `website/dist` from `main` after both React verification jobs pass. The repository is public; the npm package remains unpublished. Website publication does not raise the library release classification.
+GitHub Actions checks React 18/19, builds the package, publishes a matching version tag, and deploys the website after publication so the real npm installation command is visible. Future publication uses package-scoped trusted publishing. See [release process](releasing.md).
@@ -0,0 +1,15 @@
+# Beta releases
+
+The package uses versions such as `0.1.0-beta.0` and the npm `beta` dist-tag. It does not promote prereleases to `latest`.
+
+1. Update `package.json` and the lockfile with `npm version 0.1.0-beta.N --no-git-tag-version`.
+2. Commit the reviewed change to `main`.
+3. Push a matching tag: `git tag v0.1.0-beta.N` then `git push origin v0.1.0-beta.N`.
+
+The Verify workflow runs the complete React 18.3.1/19 matrix, including unit, browser, SSR, package and website checks. Its publication job requires the tag to equal the package version, the lockfile to match, the commit to belong to main, and the version to be absent from npm. Publication uses public access, `beta`, and provenance. Existing versions are never overwritten; bump the version for another release.
+
+Configure npm trusted publishing for organization `NIPE-Solutions`, repository `react-data-inspector`, workflow `ci.yml`, environment `npm`, with direct publish allowed. GitHub-hosted runners supply OIDC credentials. The first package creation may require the temporary `NPM_BOOTSTRAP_TOKEN` secret because no package settings exist yet; revoke and delete it after configuring trusted publishing. Never commit credentials.
+
+A successful tag publication is followed by a production website build, which checks npm and displays the real installation command. Failed publication blocks that release deployment. Ordinary main pushes continue to deploy verified website updates without publishing a package.
+
+The beta channel is a release designation. It does not imply that the manual screen-reader, current mobile Safari, dogfooding and retained-browser-heap audits in [release readiness](release-readiness.md) are complete.
@@ -1,6 +1,6 @@
 {
   "name": "@nipe-solutions/react-data-inspector",
-  "version": "0.1.0-alpha.0",
+  "version": "0.1.0-beta.0",
   "description": "A structured JavaScript data inspector for React.",
   "type": "module",
   "license": "MIT",
@@ -36,7 +36,7 @@
   },
   "publishConfig": {
     "access": "public",
-    "tag": "alpha",
+    "tag": "beta",
     "provenance": true
   },
   "scripts": {