docs(v0.44): write beta.1 prerelease release-truth copy and dist-tag-aware anchor generator (#1150) (#1283)

The v0.44.0-beta.1 prepare (e5cd55c) composed bumped registry anchors with
stable-era prose, claiming the beta published under dist-tag latest; npm
latest stays on stable 0.43.3. Head anchor zones still named v0.43.3, the
www roadmap current-line entry still carried the superseded Alpha.10 theme,
and NEXT_PUBLIC_PRERELEASE equalled the published line, tripping the #813
in-flight binding once publish evidence completes.

- docs: state the prerelease truth everywhere governed: v0.44.0-beta.1 under
  dist-tag beta, latest = 0.43.3 stable; Alpha.10 closed (verifier PASS,
  #1150); next stage Beta.2 per ADR-0151.
- www roadmap: current-line entry (en+zh) names the Beta.1 theme
  'framework qualification + governance freeze'; getting-started no longer
  calls the beta the stable latest line.
- generator: buildVersionAnchorReplacements rewrites the registry-line
  dist-tag annotation on prerelease bumps (annotation-aware rules precede
  the generic ones), so future prepares emit prerelease-correct copy.
- constants: NEXT_PUBLIC_PRERELEASE=v0.44.0-beta.2; ACTIVE_INTERNAL_CHECKPOINT
  records the Alpha checkpoint train closure.

Unblocks PR #1282.

Co-authored-by: DevBot <devbot@openelement.dev>

Author: SisyphusZheng

README.md

@@ -7,11 +7,10 @@ Standard Custom Elements are the durable component contract; JSX is the
 authoring syntax; Declarative Shadow DOM is the default server representation;
 and interactive regions activate selectively.
 
-The published stable line is `v0.43.3`. Work on `dev` is at Alpha.10, the
-internal Truth Closure checkpoint (unpublished; umbrella issue #1155) that
-hard-blocks Beta.1. Alpha checkpoints are internal work identifiers, not
-package releases. The first intended public v0.44 prerelease is Beta.1
-(`v0.44.0-beta.1`).
+The published stable line remains the 0.43 series on npm `latest`.
+`v0.44.0-beta.1` is the first public v0.44 prerelease — Beta.1, Framework
+Qualification + Governance Freeze (ADR-0151) — published under dist-tag
+`beta`. The next stage is Beta.2 (`v0.44.0-beta.2`).
 The `1.0.0` target remains unscheduled and requires separate evidence and approval.
 
 ```text
@@ -20,7 +19,7 @@ current proven scope = static-first applications with fullstack output paths
 ```
 
 Source package line: `0.44.0-beta.1` (`v0.44.0-beta.1`).
-npm registry line: `v0.44.0-beta.1` (dist-tag `latest`), published as stable `0.43.3`.
+npm registry line: `v0.44.0-beta.1` (prerelease, dist-tag `beta`); npm `latest` remains the stable `0.43.3` line.
 
 ## Why
 

README.zh.md

@@ -7,10 +7,10 @@
 长期保存的应用组件模型；JSX 与 Basic Element 是作者层；Declarative Shadow
 DOM 是默认服务端表示；交互区域按需升级。
 
-源码包行为 `0.44.0-beta.1`（`v0.44.0-beta.1`）——ADR-0119 范围化接口冻结下的
-在途五包源码行；已放弃的 beta 命名不再是当前版本线。
-npm registry 行为 `v0.44.0-beta.1`——已发布的五包版本(dist-tag `latest`)；registry 行可与
-源码行存在 patch 级滞后。
+源码包行为 `0.44.0-beta.1`（`v0.44.0-beta.1`）——首个公开 v0.44 预发布线
+（Beta.1：框架资格验证 + 治理冻结，ADR-0151）。
+npm registry 行为 `v0.44.0-beta.1`——预发布版本(dist-tag `beta`)；npm `latest` 仍为
+已发布的稳定 0.43 线。
 
 ## 当前产品
 

docs/current/VERSION_PLAN.md

@@ -2,24 +2,26 @@
 
 OpenElement = Web Components-native fullstack application framework.
 
-The published stable line remains `v0.43.3`. The active target is the internal,
-unpublished Alpha.10 Truth Closure checkpoint tracked by umbrella issue #1155.
+The published stable line remains the 0.43 series on npm `latest`.
+`v0.44.0-beta.1` is published as the first public v0.44 prerelease (Beta.1 —
+Framework Qualification + Governance Freeze) under dist-tag `beta`. The next
+stage is Beta.2 (`v0.44.0-beta.2`) per ADR-0151.
 
 ADR-0147 defines the Alpha workspace train, which is complete through Alpha.9.
 ADR-0151 retopologizes the release train and supersedes the ADR-0149 five-Beta
 mapping; the remainder of ADR-0149 and ADR-0150 that is not about Beta topology
 is unaffected. ADR-0146 remains the release-role authority and activates at
 Beta.1.
 
-- Repository package line: `v0.43.3`
-- npm registry line: `v0.43.3`
+- Repository package line: `v0.44.0-beta.1`
+- npm registry line: `v0.44.0-beta.1` (prerelease, dist-tag `beta`; npm `latest` remains the stable 0.43 line)
 - Current source package line: `v0.44.0-beta.1`
 - Current npm registry line: `v0.44.0-beta.1`
 - Latest landed train: `v0.44.0-beta.1`
-- Active internal target: Alpha.10 Truth Closure (internal, unpublished; umbrella #1155)
+- Active internal target: none — internal Alpha checkpoints closed at Alpha.10 (verifier PASS, #1150); the active line is the public Beta train (ADR-0151)
 - Active release target: `v0.44.0-beta.1`
-- Next planned public train: `v0.44.0-beta.1`
-- Next public prerelease: `v0.44.0-beta.1`
+- Next planned public train: `v0.44.0-beta.2`
+- Next public prerelease: `v0.44.0-beta.2`
 
 The coherent five-package distribution contract follows
 [PACKAGE_SURFACE.md](./PACKAGE_SURFACE.md) and ADR-0114. The supported server

docs/governance/PROJECT_WORKFLOW.md

@@ -14,15 +14,16 @@ the implementation, and the gates that prove the claim.
 Current execution anchor:
 
 - source package line `v0.44.0-beta.1`;
-- npm registry line `v0.44.0-beta.1` (published);
+- npm registry line `v0.44.0-beta.1` (prerelease, dist-tag `beta`; npm `latest`
+  remains the stable 0.43 line);
 - active target `v0.44.0-beta.1`;
-- current internal checkpoint: Alpha.10 (Truth Closure, unpublished; umbrella
-  issue #1155);
-- next public prerelease: `v0.44.0-beta.1`.
+- current internal checkpoint: none — the internal Alpha checkpoint train closed
+  at Alpha.10 (Truth Closure; verifier PASS, #1150);
+- next public prerelease: `v0.44.0-beta.2`.
 
 ADR-0143 explicitly reopens the minor train after the 0.43 maintenance freeze.
 The compiled OpenElement execution order — internal Alpha workspaces (complete
-through Alpha.9) → Alpha.10 truth closure → Beta.1 framework qualification and
+through Alpha.10) → Beta.1 framework qualification and
 governance freeze → Beta.2 productization and governance offload → Beta.3 final
 hardening, formal benchmark and real SaaS qualification → RC1 frozen candidate
 and soak → Stable/1.0 decision on Beta.3 evidence — lives in

docs/roadmap/ROADMAP.md

@@ -3,41 +3,41 @@
 OpenElement = Web Components-native fullstack application framework.
 
 Source package line: `v0.44.0-beta.1`.
-npm registry line: `v0.44.0-beta.1` (dist-tag `latest`).
-`0.43.3` is both the current source package line and the npm `latest` line.
+npm registry line: `v0.44.0-beta.1` (prerelease, dist-tag `beta`).
+The npm `latest` dist-tag remains on the published stable 0.43 line.
 Active execution target: `v0.44.0-beta.1`.
 Latest landed train: `v0.44.0-beta.1`.
 Next planned train: `v0.44.0-beta.2`.
-Next public prerelease: `v0.44.0-beta.1`.
+Next public prerelease: `v0.44.0-beta.2`.
 Long-term stable product target: `1.0.0` (unscheduled).
 
 Execution follows
 [PROJECT_WORKFLOW.md](../governance/PROJECT_WORKFLOW.md).
 
-## Current: internal Alpha.10 truth closure
+## Current: Beta.1 framework qualification + governance freeze
 
-The internal Alpha workspace train is complete through Alpha.9. Alpha.0 supplied
+The internal Alpha workspace train is complete through Alpha.10. Alpha.0 supplied
 the accepted compiler proof, exact-SHA CI foundation and minimum history safety;
 alpha.1 through alpha.7 ran as independent parallel workspaces; Alpha.8 was the
 sole aggregation workspace; Alpha.9 closed semantic convergence before Beta.1
-admission.
+admission; Alpha.10 (Truth Closure, umbrella issue #1155, work issues #1209
+through #1220) closed with verifier PASS at #1150 and admitted Beta.1.
 
-The current internal checkpoint is Alpha.10 (Truth Closure), tracked by umbrella
-issue #1155 with work issues #1209 through #1220. Alpha.10 is a hard blocker for
-Beta.1 and publishes nothing: no tag, npm publication, GitHub Release, dist-tag
-change or `main` promotion.
+Alpha identifiers were internal work identifiers, not package releases, and the
+three-role loop was off for all Alpha work.
 
-Alpha identifiers are internal work identifiers, not package releases. The
-three-role loop is off for all Alpha work.
+Beta.1 (`v0.44.0-beta.1`) is published as the first public v0.44 prerelease
+under dist-tag `beta`; npm `latest` stays on the stable 0.43 line. The next
+stage is Beta.2 (`v0.44.0-beta.2`).
 
 ## Release train
 
 ADR-0151 defines the canonical train and supersedes the ADR-0149 five-Beta
 mapping. Each phase answers one question:
 
 1. Beta.1 — Framework Qualification + Governance Freeze: is the framework itself
-   trustworthy? First intended public v0.44 prerelease (`v0.44.0-beta.1`); the
-   three-role release loop activates here.
+   trustworthy? First public v0.44 prerelease (`v0.44.0-beta.1`), published
+   under dist-tag `beta`; the three-role release loop activated here.
 2. Beta.2 — Productization + Governance Offload: can external users really use
    and maintain it?
 3. Beta.3 — Final Hardening + Formal Benchmark + Real SaaS Qualification: can

docs/status/STATUS.md

@@ -3,14 +3,14 @@
 Updated: 2026-09-02
 
 - Repository package line: `v0.44.0-beta.1`
-- npm registry line: `v0.44.0-beta.1` (dist-tag `latest`)
+- npm registry line: `v0.44.0-beta.1` (prerelease, dist-tag `beta`)
 - Latest landed train: `v0.44.0-beta.1`
 - Active release target: `v0.44.0-beta.1`
 - Next planned train: `v0.44.0-beta.2`
-- Next public prerelease: `v0.44.0-beta.1`
+- Next public prerelease: `v0.44.0-beta.2`
 - Published stable package line: `v0.43.3` on npm `latest`
-- Current development mode: internal Alpha.10 Truth Closure checkpoint
-  (unpublished; umbrella issue #1155)
+- Current development mode: public Beta train — Beta.1 published as a
+  prerelease under dist-tag `beta`; next stage Beta.2 (ADR-0151)
 - Minimum branch rules: active on `dev` and `main` through ruleset `21775463`
 - Deferred hardening: #1192 Beta.3 with #1156 #1187 #1188 #1189
 - Long-term `1.0.0` target: unscheduled
@@ -30,15 +30,15 @@ PR #1195 landed the corrected workspace train at exact SHA
 collaboration contract and executable ownership map and is the alpha.1-alpha.7 common
 base.
 
-Alpha.1 through Alpha.9 are complete: the parallel workspaces, the Alpha.8
-integration and the ADR-0150 Alpha.9 semantic convergence all closed with their
-recorded evidence. The current internal checkpoint is Alpha.10 (Truth Closure),
-governed by ADR-0151 through umbrella issue #1155 and its issue tree #1209
-through #1220. Alpha.10 is a hard blocker for Beta.1 and is internal-only: no
-tag, npm publication, GitHub Release, dist-tag change, `main` promotion or
-external release claim.
+Alpha.1 through Alpha.10 are complete: the parallel workspaces, the Alpha.8
+integration, the ADR-0150 Alpha.9 semantic convergence and the Alpha.10 Truth
+Closure checkpoint (umbrella issue #1155, issue tree #1209 through #1220,
+verifier PASS at #1150) all closed with their recorded evidence. Alpha
+checkpoints were internal-only: no tag, npm publication, GitHub Release,
+dist-tag change, `main` promotion or external release claim.
 
-Beta.1 is the first intended public v0.44 prerelease and the first phase that
-activates the thinker/implementer/fresh-verifier release loop. The npm `latest`
+Beta.1 (`v0.44.0-beta.1`) is published as the first public v0.44 prerelease
+under dist-tag `beta` — the first phase of the
+thinker/implementer/fresh-verifier release loop. The npm `latest`
 dist-tag stays stable at
 `0.43.3` until an explicitly approved 0.44 Stable release.

tools/autoflow/__tests__/release.test.ts

@@ -180,6 +180,67 @@ Deno.test('buildVersionAnchorReplacements: registry anchors cover current and la
   }
 });
 
+Deno.test('buildVersionAnchorReplacements: prerelease bumps rewrite the registry dist-tag annotation (#1282)', () => {
+  // The v0.43.3 → v0.44.0-beta.1 prepare composed the bumped registry anchor
+  // with the stale "(dist-tag `latest`)" suffix, claiming the beta published
+  // under latest. Prereleases publish under --tag alpha|beta|rc only
+  // (npmPublishTag in tools/publish-npm.ts) and `latest` stays on the stable
+  // line, so the bump must rewrite the annotation together with the version.
+  const version = '9.9.9-beta.1';
+  const tag = `v${version}`;
+  const reps = buildVersionAnchorReplacements(version);
+
+  for (const path of ['README.md', 'docs/roadmap/ROADMAP.md', 'docs/status/STATUS.md']) {
+    for (const fromTag of [PACKAGE_VERSION_TAG, PREVIOUS_PACKAGE_VERSION_TAG]) {
+      const from = `npm registry line: \`${fromTag}\` (dist-tag \`latest\`)`;
+      const to = `npm registry line: \`${tag}\` (prerelease, dist-tag \`beta\`)`;
+      assert(
+        reps.some(([p, f, t]) => p === path && f === from && t === to),
+        `missing prerelease dist-tag replacement ${path}: ${from} -> ${to}`,
+      );
+    }
+  }
+  // README.zh.md carries the same annotation in its own prose shape.
+  for (const fromTag of [PACKAGE_VERSION_TAG, PREVIOUS_PACKAGE_VERSION_TAG]) {
+    const from = `npm registry 行为 \`${fromTag}\`——已发布的五包版本(dist-tag \`latest\`)`;
+    const to = `npm registry 行为 \`${tag}\`——预发布版本(dist-tag \`beta\`)`;
+    assert(
+      reps.some(([p, f, t]) => p === 'README.zh.md' && f === from && t === to),
+      `missing prerelease dist-tag replacement README.zh.md: ${from} -> ${to}`,
+    );
+  }
+
+  // The annotation-aware rules must precede the generic registry-line rules:
+  // updateCurrentVersionAnchors applies rules in order, and the generic rule
+  // would otherwise consume the anchor first and strand the stale suffix.
+  const specificIndex = reps.findIndex(([p, f]) =>
+    p === 'README.md' && f === `npm registry line: \`${PACKAGE_VERSION_TAG}\` (dist-tag \`latest\`)`
+  );
+  const genericIndex = reps.findIndex(([p, f]) =>
+    p === 'README.md' && f === `npm registry line: \`${PACKAGE_VERSION_TAG}\``
+  );
+  assert(specificIndex !== -1 && genericIndex !== -1 && specificIndex < genericIndex);
+
+  // The dist-tag name follows the prerelease channel (alpha|beta|rc).
+  assert(
+    buildVersionAnchorReplacements('9.9.9-alpha.2').some(([, , t]) =>
+      t.includes('(prerelease, dist-tag `alpha`)')
+    ),
+  );
+  assert(
+    buildVersionAnchorReplacements('9.9.9-rc.1').some(([, , t]) =>
+      t.includes('(prerelease, dist-tag `rc`)')
+    ),
+  );
+
+  // Stable targets never touch the dist-tag annotation: a stable cut IS the
+  // latest line, and the rule surface stays at the exact 40 entries.
+  assertFalse(
+    buildVersionAnchorReplacements('9.9.9').some(([, f]) => f.includes('dist-tag')),
+  );
+  assertEquals(buildVersionAnchorReplacements('9.9.9').length, 40);
+});
+
 Deno.test('buildVersionAnchorReplacements: every target carries the previous or current line', () => {
   // Coverage gate: every file that is a replacement target must still carry
   // the previous package line (or its tag), so the bump has something to
@@ -197,9 +258,10 @@ Deno.test('buildVersionAnchorReplacements: every target carries the previous or
   }
   // README carries one head package-line anchor, the currency claim the
   // strategic-docs gate enforces ("convergence is published as"), and the
-  // registry line in both accepted states (#754).
+  // registry line in both accepted states (#754). A prerelease source line
+  // adds the two dist-tag-correcting registry forms (#1282).
   const readmeReps = reps.filter(([p]) => p === 'README.md');
-  assertEquals(readmeReps.length, 4);
+  assertEquals(readmeReps.length, PACKAGE_VERSION.includes('-') ? 6 : 4);
 });
 
 Deno.test('createReleasePlan: rejects shell metacharacters in approval ids', () => {

tools/autoflow/version-anchors.ts

@@ -418,7 +418,37 @@ export function buildVersionAnchorReplacements(
       .replaceAll('$PV', pv)
       .replaceAll('$TAG', tag)
       .replaceAll('$VER', version);
-  return raw.map(([path, from, to]) => [path, resolve(from), resolve(to)]);
+  // Prerelease bumps (#1282): the generic registry-line rules advance the
+  // anchor version but leave the stable-era "(dist-tag `latest`)" annotation
+  // untouched, composing a false claim — prereleases publish under
+  // --tag alpha|beta|rc only (npmPublishTag in tools/publish-npm.ts) and
+  // `latest` stays on the stable line. Rewrite the annotation together with
+  // the version. These forms must precede the generic registry-line rules:
+  // updateCurrentVersionAnchors applies rules in order and the generic rule
+  // would otherwise consume the anchor first, stranding the stale suffix.
+  // Docs whose registry line carries no annotation (VERSION_PLAN,
+  // PROJECT_WORKFLOW) need no rule — the generic replacement is correct.
+  const prereleaseDistTag = version.match(/-(alpha|beta|rc)\.\d+$/u)?.[1];
+  const prereleaseRules: Array<[string, string, string]> = [];
+  if (prereleaseDistTag !== undefined) {
+    for (const path of ['README.md', 'docs/roadmap/ROADMAP.md', 'docs/status/STATUS.md']) {
+      for (const fromTag of ['$PVT', '$PREV_PVT']) {
+        prereleaseRules.push([
+          path,
+          `npm registry line: \`${fromTag}\` (dist-tag \`latest\`)`,
+          `npm registry line: \`$TAG\` (prerelease, dist-tag \`${prereleaseDistTag}\`)`,
+        ]);
+      }
+    }
+    for (const fromTag of ['$PVT', '$PREV_PVT']) {
+      prereleaseRules.push([
+        'README.zh.md',
+        `npm registry 行为 \`${fromTag}\`——已发布的五包版本(dist-tag \`latest\`)`,
+        `npm registry 行为 \`$TAG\`——预发布版本(dist-tag \`${prereleaseDistTag}\`)`,
+      ]);
+    }
+  }
+  return [...prereleaseRules, ...raw].map(([path, from, to]) => [path, resolve(from), resolve(to)]);
 }
 
 export async function updateCurrentVersionAnchors(version: string): Promise<void> {

tools/project-constants.ts

@@ -9,12 +9,13 @@ export const PACKAGE_VERSION_TAG = `v${PACKAGE_VERSION}`;
 export const LATEST_LANDED_TRAIN = 'v0.44.0-beta.1';
 export const ACTIVE_EXECUTION_VERSION = 'v0.44.0-beta.1';
 export const NEXT_EXECUTION_VERSION = 'v0.44.0-beta.2';
-// Internal v0.44 admission checkpoints are not package versions. Keep them
-// separate from release-bump constants so Alpha.10 cannot be interpreted as a
-// publishable npm/tag target.
+// Internal v0.44 admission checkpoints are not package versions. The Alpha
+// checkpoint train closed at Alpha.10 (verifier PASS, #1150); with Beta.1
+// published as a public prerelease there is no active internal checkpoint —
+// the value records that closure so the VERSION_PLAN anchor stays honest.
 export const ACTIVE_INTERNAL_CHECKPOINT =
-  'Alpha.10 Truth Closure (internal, unpublished; umbrella #1155)';
-export const NEXT_PUBLIC_PRERELEASE = 'v0.44.0-beta.1';
+  'none — internal Alpha checkpoints closed at Alpha.10 (verifier PASS, #1150); the active line is the public Beta train (ADR-0151)';
+export const NEXT_PUBLIC_PRERELEASE = 'v0.44.0-beta.2';
 export const RETAINED_PACKAGE_NAMES = Object.freeze([
   '@openelement/adapter-vite',
   '@openelement/app',

www/app/routes/roadmap.tsx

@@ -35,11 +35,12 @@ const entries: Record<'en' | 'zh', TimelineEntry[]> = {
   en: [
     {
       version: 'v0.44.0-beta.1',
-      theme: 'renderer-owned light DOM hydration — robustness audit closure',
+      theme: 'framework qualification + governance freeze',
       copy:
-        'The published stable line remains available while 0.44 is prerelease. It proves Universal WC SSR, in-place light-DOM activation and the application delivery baseline that the compiled architecture must preserve.',
-      state: 'stable',
+        'The first public prerelease of the compiled line, published under dist-tag beta while the stable 0.43 line keeps npm latest. It qualifies the framework itself — compiler, page-route SSR bound to the Part Program, delivery gates — under a frozen governance envelope (ADR-0151).',
+      state: 'next',
       stamp: 'CURRENT',
+      status: 'prerelease',
     },
     {
       version: 'v0.44 alpha',
@@ -85,12 +86,13 @@ const entries: Record<'en' | 'zh', TimelineEntry[]> = {
   ],
   zh: [
     {
-      version: 'v0.43.3',
-      theme: '渲染方所有的 light DOM 水合 — 鲁棒性审计闭环',
+      version: 'v0.44.0-beta.1',
+      theme: '框架资格验证 + 治理冻结',
       copy:
-        '已发布稳定线会在 0.44 预发布期间继续可用。它证明了 Universal WC SSR、light DOM 原地激活与应用交付基线；新的编译架构必须保持这些能力。',
-      state: 'stable',
+        '编译型线路的首个公开预发布版本，以 dist-tag beta 发布，npm latest 仍由稳定 0.43 线保持。它在冻结的治理边界内验证框架本身——编译器、绑定到 Part Program 的页面路由 SSR 与交付门禁（ADR-0151）。',
+      state: 'next',
       stamp: 'CURRENT',
+      status: '预发布',
     },
     {
       version: 'v0.44 alpha',