v6.0.0-beta.11

.claude/release-notes/input-v6.0.0-beta.11.md

@@ -0,0 +1,12 @@
+# Velt SDK Release Notes - v6.0.0-beta.11
+Release Date: July 15, 2026
+
+> **Maintenance release.** `6.0.0-beta.11` is a version-bump and release-infrastructure release. It ships **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes** for either the HTML/Vanilla or React SDK. The substantive change is on the release-pipeline side: the SDK's CI now mirrors each published npm tarball to Velt's self-host release registry so self-host installs can fetch a byte-identical copy. Everything else is documentation and version/integrity-hash bumps. Existing integrations are unaffected — upgrading only moves you to the `6.0.0-beta.11` build.
+
+## Summary
+| SDK | Files Changed | Insertions | Deletions |
+|-----|--------------|------------|----------|
+| HTML/Vanilla (sdk) | 4 | +152 | -9 |
+| React (sdk-react) | 3 | +4 | -4 |
+
+> Counts reflect the code-change footprint. The React SDK's raw PR totals, including the `package-lock.json` churn, were 4 files / +11 / -11.

.claude/release-notes/runs/v6.0.0-beta.11/.complete

@@ -0,0 +1,3 @@
+completed_at=2026-07-16T04:36:58Z
+pr_number=288
+pr_url=https://github.com/velt-js/docs/pull/288

.claude/release-notes/runs/v6.0.0-beta.11/01-agent-1.done

@@ -0,0 +1,3 @@
+stage=01-agent-1
+agent=mdx-release-notes-generator
+completed_at=2026-07-16T04:31:44Z

.claude/release-notes/runs/v6.0.0-beta.11/01-agent-1.log

@@ -0,0 +1,21 @@
+[run-release-note-agent] stage=01-agent-1 agent=mdx-release-notes-generator model=claude-opus-4-8 max-turns=100
+The `.claude/` path writes are permission-gated in this environment and were declined; the durable log is optional ("when useful"), so I won't retry it. The essential deliverable — the changelog edit — succeeded.
+
+## Agent-1 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK → `release-notes/version-6/sdk-changelog.mdx`
+
+**Source assessment:** `input-v6.0.0-beta.11.md` is a maintenance / version-bump + release-infrastructure release with **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes**. The single user-relevant change is CI-side: published SDK builds are now mirrored to Velt's self-host release registry.
+
+**Action taken:** Inserted one `<Update label="6.0.0-beta.11" description="July 15, 2026">` block at the top of the changelog (above beta.10), with a single Improvements bullet:
+
+> - [**Self-Hosting**]: Each published SDK build is now mirrored to Velt's self-host release registry, so self-host installs fetch a byte-identical copy of the npm tarball.
+
+**Key decisions:**
+- One bullet, one sentence — the only substantive change. Classified under `[**Self-Hosting**]`, consistent with prior beta entries.
+- **No "Learn More" link:** grep found no docs page for the SDK release-registry/tarball mirroring (`/self-host-data/*` covers data self-hosting, not SDK distribution). Per rules, did not invent a URL; omitted the link since this is a minor infra note, not a major feature.
+- No Breaking Changes / `<Warning>` block (none applicable). No new docs pages created.
+
+**Verified:** chronological order (Jul 15 above Jul 14) intact; only the applicable section present; within verbosity limits.
+
+**Handoff to Agent-2:** Expected planning finding — no downstream doc-area updates required (no API/model/wireframe/primitive changes). Per run rules, I did not dispatch Agent-2; the outer script invokes it.

.claude/release-notes/runs/v6.0.0-beta.11/02-agent-2.done

@@ -0,0 +1,3 @@
+stage=02-agent-2
+agent=release-planning-agent
+completed_at=2026-07-16T04:32:33Z

.claude/release-notes/runs/v6.0.0-beta.11/02-agent-2.log

@@ -0,0 +1,22 @@
+[run-release-note-agent] stage=02-agent-2 agent=release-planning-agent model=claude-opus-4-8 max-turns=100
+Both `.claude/` writes are permission-gated in this environment and were declined — the same behavior Agent-1 encountered. These durable artifacts are optional ("when useful"), so I won't retry verbatim. My analysis is complete.
+
+## Agent-2 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK
+
+**Finding: no-op — no downstream documentation updates required.**
+
+I analyzed Agent-1's release note (the single changelog Improvements bullet). This is a maintenance / release-infrastructure release:
+
+- **Data Models** — no new/changed types, interfaces, or enums → `data-models.mdx` unchanged
+- **API Methods** — no new methods/hooks, no signature changes → `api-methods.mdx` unchanged
+- **Documentation** — no new feature lacking docs → no new pages
+- **UI Customization (Wireframes / Primitives)** — no new wireframes, components, or props → unchanged
+- **Upgrade Guide** — no breaking changes → `upgrade-guide.mdx` unchanged
+
+The only user-relevant change (SDK builds mirrored to the self-host release registry) is CI-side and is already fully captured in the changelog by Agent-1.
+
+**Handoff to Agent-3:** nothing to implement — no data-model or api-method updates flagged. Per run rules, I did not dispatch Agent-3; the outer script handles sequencing.
+
+Note: the planning log (`.claude/logs/agent-2-planning-v6.0.0-beta.11.md`) and no-op note (`.claude/release-notes/runs/v6.0.0-beta.11/02-agent-2-noop.md`) could not be persisted because `.claude/` writes are declined in this environment; the analysis conclusion above stands regardless.

.claude/release-notes/runs/v6.0.0-beta.11/03-agent-3.done

@@ -0,0 +1,3 @@
+stage=03-agent-3
+agent=models-and-methods-updater
+completed_at=2026-07-16T04:33:15Z

.claude/release-notes/runs/v6.0.0-beta.11/03-agent-3.log

@@ -0,0 +1,18 @@
+[run-release-note-agent] stage=03-agent-3 agent=models-and-methods-updater model=claude-opus-4-8 max-turns=100
+All `.claude/` writes are permission-gated and declined in this environment (consistent with Agent-1 and Agent-2). The durable no-op note is optional ("when useful"), so I won't fight the permission gate. My conclusion stands regardless.
+
+## Agent-3 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK
+**Finding: no-op — no technical reference updates required.**
+
+I reviewed the public-only source note (`.claude/release-notes/input-v6.0.0-beta.11.md`) and the upstream Agent-1/Agent-2 conclusions. `v6.0.0-beta.11` is a maintenance / release-infrastructure release with **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes**.
+
+- **`data-models.mdx`** — no change. No new/changed types, interfaces, or enums.
+- **`api-methods.mdx`** — no change. No new methods/hooks, no signature changes.
+
+The only user-relevant change (published SDK builds now mirrored to Velt's self-host release registry) is CI-side and introduces no types, hooks, or API methods. It was already fully captured by Agent-1 in the changelog. Agent-2 explicitly flagged nothing for this stage to implement.
+
+**Handoff to Agent-4:** nothing to implement in the technical reference; no wireframe/primitive prerequisites created. Per run rules, I did not dispatch Agent-4, commit, or push — the outer script handles sequencing.
+
+**Note:** The intended no-op artifact (`03-agent-3-noop.md`) and the stage-log append could not be persisted because `.claude/` writes are declined in this environment; the conclusion above is authoritative regardless.

.claude/release-notes/runs/v6.0.0-beta.11/04-agent-4.done

@@ -0,0 +1,3 @@
+stage=04-agent-4
+agent=ui-customization-updater
+completed_at=2026-07-16T04:33:50Z

.claude/release-notes/runs/v6.0.0-beta.11/04-agent-4.log

@@ -0,0 +1,19 @@
+[run-release-note-agent] stage=04-agent-4 agent=ui-customization-updater model=claude-opus-4-8 max-turns=100
+The `.claude/` write is permission-gated and was declined — consistent with what Agent-1, Agent-2, and Agent-3 each encountered in this environment. The no-op note is an optional durable artifact ("when useful"), so I won't fight the permission gate. My conclusion is authoritative regardless.
+
+## Agent-4 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK
+**Finding: no-op — no wireframe or UI customization work required.**
+
+`v6.0.0-beta.11` is a maintenance / release-infrastructure release. The public-only source note confirms **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes** for either SDK. The only user-relevant change (npm tarballs mirrored to the self-host release registry) is CI-side and introduces no UI surface. Both Agent-2 and Agent-3 independently reached the same no-op conclusion.
+
+**Scope check (nothing applied):**
+- Wireframe pages under `ui-customization/features/` — unchanged (no new/changed wireframes)
+- Comment Dialog `comment-dialog-components.mdx` — unchanged
+- React / Other Frameworks code examples — none needed
+- `docs.json` navigation — unchanged (no new wireframe pages created)
+
+**Handoff to Agent-5 (primitives-updater):** No primitive component changes to pass through. Agent-5 should confirm no-op and pass through to Agent-6.
+
+Per run rules: I did not commit, push, create branches/PRs, or dispatch the next agent — the outer script handles sequencing. The intended no-op artifact (`04-agent-4-noop.md`) could not be persisted because `.claude/` writes are declined in this environment; the conclusion above stands regardless.

.claude/release-notes/runs/v6.0.0-beta.11/05-agent-5.done

@@ -0,0 +1,3 @@
+stage=05-agent-5
+agent=primitives-updater
+completed_at=2026-07-16T04:34:26Z

.claude/release-notes/runs/v6.0.0-beta.11/05-agent-5.log

@@ -0,0 +1,20 @@
+[run-release-note-agent] stage=05-agent-5 agent=primitives-updater model=claude-opus-4-8 max-turns=100
+The `.claude/` write is permission-gated and was declined — the same behavior Agent-1 through Agent-4 each encountered in this environment. The no-op note is an optional durable artifact ("when useful"), so I won't fight the permission gate. My conclusion stands regardless.
+
+## Agent-5 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK
+**Finding: no-op — no primitive component documentation work required.**
+
+`v6.0.0-beta.11` is a maintenance / release-infrastructure release. The public-only source note explicitly confirms **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes** for either the HTML/Vanilla or React SDK. The only user-relevant change (published npm tarballs mirrored to the self-host release registry) is CI-side and introduces no new or changed primitives.
+
+**Scope check (nothing applied):**
+- Primitive pages under `ui-customization/features/**` — unchanged (no new/changed primitives)
+- `comment-dialog/primitives.mdx`, `comment-sidebar-v2-primitives.mdx`, `activity-logs-primitives.mdx` — unchanged
+- `docs.json` navigation — unchanged (no new primitives pages created)
+
+**Upstream corroboration:** Agent-2 (planning) and Agent-4 (wireframes) each independently reached the same no-op conclusion, with Agent-4 explicitly noting no primitives to pass through.
+
+**Handoff to Agent-6:** No primitive documentation changes to align. Agent-6 should confirm no-op and pass through to Agent-7.
+
+Per run rules: I did not commit, push, create branches/PRs, or dispatch the next agent — the outer script handles sequencing. The intended no-op artifact (`05-agent-5-noop.md`) could not be persisted because `.claude/` writes are declined in this environment; the conclusion above stands regardless.

.claude/release-notes/runs/v6.0.0-beta.11/06-agent-6.done

@@ -0,0 +1,3 @@
+stage=06-agent-6
+agent=documentation-alignment-enforcer
+completed_at=2026-07-16T04:35:38Z

.claude/release-notes/runs/v6.0.0-beta.11/06-agent-6.log

@@ -0,0 +1,20 @@
+[run-release-note-agent] stage=06-agent-6 agent=documentation-alignment-enforcer model=claude-opus-4-8 max-turns=100
+Both `.claude/` writes are permission-gated and declined in this environment — the same behavior Agents 2–5 each encountered. The durable no-op artifact is optional ("when useful"), so I won't fight the permission gate. My conclusion is authoritative regardless and is recorded below.
+
+## Agent-6 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK
+**Finding: no-op — no documentation alignment required.**
+
+`v6.0.0-beta.11` is a maintenance / release-infrastructure release. The public-only source note confirms **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes**. Agents 2–5 each independently reached a no-op — nothing new was added or changed for this stage to align.
+
+**Scope check (nothing applied):**
+- New feature names, API methods/parameters, wireframe components, primitives — none.
+- Cross-references, anchors, bidirectional links — no slug or method changes, nothing to update.
+
+**Changelog verification:**
+- `release-notes/version-6/sdk-changelog.mdx` — `6.0.0-beta.11` `<Update>` block present, correctly in the **version-6** directory, single well-formed **Improvements** bullet.
+- Terminology consistent with the source note ("Self-Hosting", "self-host release registry") — no from/to mappings needed.
+- Repo-wide scan for `6.0.0-beta.11` across `**/*.{md,mdx,markdown}` returns only the changelog and this run's own artifacts — no stray references.
+
+**Handoff to Agent-7:** No alignment edits to carry forward; confirm no-op for repo-wide terminology alignment. Per run rules: no commit, push, branch, PR, or next-agent dispatch — the outer script handles sequencing. The intended no-op artifact (`06-agent-6-noop.md`) and log append could not be persisted because `.claude/` writes are declined here; this conclusion stands regardless.

.claude/release-notes/runs/v6.0.0-beta.11/07-agent-7.done

@@ -0,0 +1,3 @@
+stage=07-agent-7
+agent=qa-terminology-aligner
+completed_at=2026-07-16T04:36:57Z

.claude/release-notes/runs/v6.0.0-beta.11/07-agent-7.log

@@ -0,0 +1,31 @@
+[run-release-note-agent] stage=07-agent-7 agent=qa-terminology-aligner model=claude-opus-4-8 max-turns=100
+All `.claude/` writes are permission-gated and declined in this environment — the same behavior Agents 1–6 each encountered. The QA log is an optional durable artifact ("when useful"), so I won't fight the permission gate; my conclusion is recorded below and is authoritative regardless.
+
+## Agent-7 complete — v6.0.0-beta.11
+
+**Route class:** core-SDK → `release-notes/version-6/sdk-changelog.mdx`
+**Finding: QA pass — 0 issues, 0 fixes. No search/replace necessary.**
+
+### QA Summary
+
+**Issues Found: 0**
+
+| Check | Result |
+|-------|--------|
+| Changelog `<Update>` block placement | ✅ `6.0.0-beta.11` at top, above `beta.10`; chronological (Jul 15 > Jul 14) |
+| Section structure | ✅ Single well-formed **Improvements** bullet under `[**Self-Hosting**]`; no duplicate headings; no Breaking Changes in changelog |
+| Terminology consistency | ✅ "Self-Hosting" / "self-host release registry" matches source note and beta.10's label; no from/to mappings needed |
+| Repo-wide scan for `6.0.0-beta.11` | ✅ Only the changelog + this run's own artifacts; no stray references |
+| "Learn more" link omission (Agent-1) | ✅ Confirmed correct — `self-host-data/*` covers *data* self-hosting, not SDK build/tarball distribution; no dedicated page exists, so no link was manufactured |
+
+### Validation of Prior Agents
+Agents 2–6 each independently reached a no-op, corroborated here. `v6.0.0-beta.11` is a maintenance / release-infrastructure release with **no public API changes, no new components, no prop/attribute/event changes, and no runtime behavior changes**. The single user-relevant change (published SDK builds mirrored to Velt's self-host release registry) is CI-side and was accurately captured by Agent-1 in the changelog. No manufactured work; no unnecessary edits made by prior agents.
+
+- Files corrected: **0**
+- Critical issues: **0**
+- Terminology alignments: **0**
+
+### Handoff
+Documentation is consistent and the changelog edit is validated as accurate, complete, and correctly placed. **Agent-1 is ready** for the next release note. Pipeline may proceed to Plugin Agent 1 (Skills Delta Extractor); no skill-relevant deltas expected given the no-op nature of this release.
+
+Per run rules: I did not commit, push, create branches/PRs, or dispatch the next agent — the outer script handles sequencing. The intended QA log (`.claude/logs/agent-7-qa-v6.0.0-beta.11.md`) and run-dir copy could not be persisted because `.claude/` writes are declined in this environment; the conclusion above stands regardless.

.claude/release-notes/runs/v6.0.0-beta.11/pr-body.md

@@ -0,0 +1,18 @@
+## Summary
+
+Automated release-note docs pipeline for `release-notes/v6.0.0-beta.11.md`.
+
+- Route: `core-SDK`
+- Source note: https://github.com/snippyly/internal-release-notes/blob/a02fd5724196578ace7b1932d4ac75c499b3ce86/release-notes/v6.0.0-beta.11.md
+- Rerun URL: https://github.com/snippyly/internal-release-notes/blob/a02fd5724196578ace7b1932d4ac75c499b3ce86/release-notes/v6.0.0-beta.11.md
+- Status: Complete
+- Run: https://github.com/velt-js/docs/actions/runs/29471495822
+
+## Needs human follow-up
+
+- Review the generated docs changes before merging.
+- Confirm the conservative automation defaults were appropriate for this note.
+
+## Checkpoints
+
+Runtime checkpoints are saved under `.claude/release-notes/runs/v6.0.0-beta.11`.

.claude/release-notes/runs/v6.0.0-beta.11/public-note.env

@@ -0,0 +1 @@
+trimmed_internal_section=true

.claude/release-notes/runs/v6.0.0-beta.11/route.json

@@ -0,0 +1,11 @@
+{
+  "class": "core-SDK",
+  "version": "v6.0.0-beta.11",
+  "stem": "v6.0.0-beta.11",
+  "safe_stem": "v6.0.0-beta.11",
+  "branch": "v6.0.0-beta.11",
+  "title": "v6.0.0-beta.11",
+  "changelog": "release-notes/version-6/sdk-changelog.mdx",
+  "major": "6",
+  "triage_reason": ""
+}

.claude/release-notes/runs/v6.0.0-beta.11/run.env

@@ -0,0 +1,13 @@
+NOTE_REPO=snippyly/internal-release-notes
+SOURCE_REPO=snippyly/internal-release-notes
+NOTE_PATH=release-notes/v6.0.0-beta.11.md
+SOURCE_SHA=a02fd5724196578ace7b1932d4ac75c499b3ce86
+CHANGE_TYPE=added
+PIPELINE_MODE=resume
+RUN_URL=https://github.com/velt-js/docs/actions/runs/29471495822
+RN_CLASS=core-SDK
+RN_VERSION=v6.0.0-beta.11
+RN_BRANCH=v6.0.0-beta.11
+RN_TITLE=v6.0.0-beta.11
+RN_CHANGELOG=release-notes/version-6/sdk-changelog.mdx
+trimmed_internal_section=true

release-notes/version-6/sdk-changelog.mdx

@@ -10,6 +10,14 @@ description: Release Notes of changes added to the core Velt SDK
 - `@veltdev/sdk`
 - `@veltdev/types`
 
+<Update label="6.0.0-beta.11" description="July 15, 2026">
+
+### Improvements
+
+- [**Self-Hosting**]: Each published SDK build is now mirrored to Velt's self-host release registry, so self-host installs fetch a byte-identical copy of the npm tarball.
+
+</Update>
+
 <Update label="6.0.0-beta.10" description="July 14, 2026">
 
 ### New Features