Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .claude/release-notes/input-v6.0.0-beta.12.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Velt SDK Release Notes - v6.0.0-beta.12
Release Date: July 17, 2026

> **Maintenance release.** `6.0.0-beta.12` 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 work is on the release-pipeline side: the self-host registry mirror job introduced in `6.0.0-beta.11` is hardened (correct gating on partial build failures, a verify-only resume mode for retries, a Trivy vulnerability gate, an SBOM attestation, restored `contents: read` permission, and a Slack failure alert), and the mirror target moves to a dedicated customer-visible registry project. Everything else is documentation and version/integrity-hash bumps. Existing integrations are unaffected — upgrading only moves you to the `6.0.0-beta.12` build.

## Summary
| SDK | Files Changed | Insertions | Deletions |
|-----|--------------|------------|----------|
| HTML/Vanilla (sdk) | 4 | +315 | -19 |
| 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. The HTML/Vanilla footprint is dominated by CI workflow (`.github/workflows/main.yml`) and internal journal/doc changes; no SDK source or public API files were touched.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/.complete
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
completed_at=2026-07-17T16:26:18Z
pr_number=290
pr_url=https://github.com/velt-js/docs/pull/290
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/01-agent-1.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=01-agent-1
agent=mdx-release-notes-generator
completed_at=2026-07-17T16:21:31Z
25 changes: 25 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/01-agent-1.log
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
[run-release-note-agent] stage=01-agent-1 agent=mdx-release-notes-generator model=claude-opus-4-8 max-turns=100
Both the Write tool and a Bash heredoc to `.claude/release-notes/runs/v6.0.0-beta.12/01-agent-1-noop.md` were blocked — that path is treated as sensitive and requires interactive approval, which isn't available in this automated run. I won't retry the same call.

Here is the completed result of Agent-1 (Stage `01-agent-1`) for the `core-SDK` route:

## Decision: No-op — no changelog work applicable

**Analysis of the source note** (`.claude/release-notes/input-v6.0.0-beta.12.md`):

`v6.0.0-beta.12` is a maintenance / version-bump and release-infrastructure release. The note explicitly states 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.

All substantive work is on the release-pipeline side and is **not documentable as a public SDK change**:
- Hardening of the self-host registry mirror job from `6.0.0-beta.11` (gating on partial build failures, verify-only resume mode, Trivy vulnerability gate, SBOM attestation, restored `contents: read` permission, Slack failure alert)
- Mirror target moved to a dedicated customer-visible registry project
- Documentation and version/integrity-hash bumps

The SDK changelog only documents public **New Features / Improvements / Bug Fixes**. Nothing in this release fits those sections.

**Actions taken:**
- Read the public-only source note.
- Read the top of `release-notes/version-6/sdk-changelog.mdx` (current top entry: `6.0.0-beta.10`) to confirm patterns.
- Made **no edits** to any changelog, upgrade guide, or docs page.
- Did **not** trigger Agent-2 (no generated release note to hand off).

**Blocked deliverable:** The no-op marker file `01-agent-1-noop.md` could not be written because the run directory is permission-gated. The outer orchestration script (which handles commits/PRs) may need to either write this marker itself or grant write access to `.claude/release-notes/runs/` for the agent. The no-op content is captured above verbatim.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/02-agent-2.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=02-agent-2
agent=release-planning-agent
completed_at=2026-07-17T16:22:26Z
30 changes: 30 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/02-agent-2.log
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
[run-release-note-agent] stage=02-agent-2 agent=release-planning-agent model=claude-opus-4-8 max-turns=100
The durable-file writes are blocked by the same permission gate that stopped Agent-1 — both the Write tool and Bash heredocs to `.claude/release-notes/runs/` and `.claude/logs/` require interactive approval, which isn't available in this automated run. I won't retry the blocked calls.

Here is the completed result of Agent-2 (Stage `02-agent-2`) for the `core-SDK` route:

## Decision: No-op — no planning work applicable

**Analysis:**

Agent-1 returned a no-op and produced **no generated release note** to analyze. `v6.0.0-beta.12` is a maintenance / version-bump and release-infrastructure release. The public-only source note (`.claude/release-notes/input-v6.0.0-beta.12.md`) explicitly states 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.

All substantive work is release-pipeline hardening (self-host registry mirror job gating, Trivy vulnerability gate, SBOM attestation, verify-only resume mode, Slack failure alert, mirror target moved to a customer-visible registry project) plus version/integrity-hash bumps — none of which is a documentable public SDK change.

**Areas requiring updates:** None.

| Area | File | Update |
|------|------|--------|
| Data Models | `data-models.mdx` | None — no new types/interfaces/enums |
| API Methods | `api-methods.mdx` | None — no new/changed methods or hooks |
| Documentation | — | None — no new feature |
| UI Customization — Wireframes | `comment-dialog-components.mdx` | None — no new wireframes |
| UI Customization — Primitives | `comment-dialog-primitives/overview.mdx` | None — no new primitives/props |
| Upgrade Guide | `release-notes/version-6/upgrade-guide.mdx` | None — no breaking changes |
| Changelog | `release-notes/version-6/sdk-changelog.mdx` | None — no public New Features/Improvements/Bug Fixes |

**Handoff:** No planning output to pass to Agent-3. Downstream agents (3–5) have no work for this release.

**Blocked deliverables:** The no-op marker `02-agent-2-noop.md` and the planning log `.claude/logs/agent-2-planning-v6.0.0-beta.12.md` could not be written — both target paths are permission-gated in this automated run (same restriction Agent-1 reported). The full content is captured above verbatim; the outer orchestration script may need to write these markers itself or grant write access to `.claude/release-notes/runs/` and `.claude/logs/`.

Exiting successfully — no applicable work for this route class.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/03-agent-3.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=03-agent-3
agent=models-and-methods-updater
completed_at=2026-07-17T16:23:21Z
33 changes: 33 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/03-agent-3.log
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
[run-release-note-agent] stage=03-agent-3 agent=models-and-methods-updater model=claude-opus-4-8 max-turns=100
Both the Write tool and a Bash heredoc are blocked by the same permission gate that stopped Agent-1 and Agent-2. I won't retry the blocked calls. Reporting the completed result verbatim so the outer orchestration script can persist the marker.

---

## Agent-3 (Stage `03-agent-3`) — `core-SDK` route

### Decision: No-op — no technical-reference updates applicable

**Analysis:**

Agent-1 and Agent-2 both returned no-op decisions and produced no planning output for Agent-3 to act on. `v6.0.0-beta.12` is a maintenance / version-bump and release-infrastructure release. The public-only source note (`.claude/release-notes/input-v6.0.0-beta.12.md`) explicitly states 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.

All substantive work is release-pipeline hardening (self-host registry mirror job gating, Trivy vulnerability gate, SBOM attestation, verify-only resume mode, Slack failure alert, mirror target moved to a customer-visible registry project) plus version/integrity-hash bumps — none of which is a documentable public SDK **type, interface, enum, hook, or method**.

**Files considered — none changed:**

| File | Update |
|------|--------|
| `api-reference/sdk/models/data-models.mdx` | None — no new types/interfaces/enums |
| `api-reference/sdk/api/api-methods.mdx` | None — no new/changed methods or hooks |

**Verification performed:**
- Read the public-only source note — confirmed it is a maintenance release.
- Read Agent-1 and Agent-2 logs — both no-op, no planning handoff.
- Confirmed changelog target `release-notes/version-6/sdk-changelog.mdx` top entry remains `6.0.0-beta.10`; no `6.0.0-beta.12` public entry is expected.
- No Internal-section content influenced this decision (input note is public-only).

**Handoff:** No technical-reference output to pass to Agent-4. Downstream agents have no work for this release.

**Blocked deliverable:** The no-op marker `03-agent-3-noop.md` could not be written — both the Write tool and a Bash heredoc to `.claude/release-notes/runs/v6.0.0-beta.12/` are permission-gated in this automated run (same restriction Agent-1 and Agent-2 reported). The full content is captured above verbatim; the outer orchestration script may need to write this marker itself or grant write access to `.claude/release-notes/runs/`.

Exiting successfully — no applicable work for this route class.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/04-agent-4.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=04-agent-4
agent=ui-customization-updater
completed_at=2026-07-17T16:23:57Z
37 changes: 37 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/04-agent-4.log
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
[run-release-note-agent] stage=04-agent-4 agent=ui-customization-updater model=claude-opus-4-8 max-turns=100
The Write tool is blocked by the same permission gate that stopped Agents 1–3. I won't retry the blocked call. Reporting the completed result verbatim so the outer orchestration script can persist the marker.

---

## Agent-4 (Stage `04-agent-4`) — `core-SDK` route

### Decision: No-op — no wireframe / UI-customization updates applicable

**Analysis:**

`v6.0.0-beta.12` is a maintenance / version-bump and release-infrastructure release. The public-only source note explicitly states 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.

All substantive work is release-pipeline hardening (self-host registry mirror job gating, Trivy vulnerability gate, SBOM attestation, verify-only resume mode, Slack failure alert, mirror target moved to a customer-visible registry project) plus version/integrity-hash bumps. None of this introduces or changes wireframes, wireframe child-component hierarchies, or UI customization code examples.

**Upstream context:**
- Agents 1 and 2 returned no-op decisions with no planning handoff.
- Agent-3 returned no-op — no technical-reference (data-models / api-methods) updates, so no UI components require wireframe or code-example coverage.

**Files considered — none changed:**

| File | Update |
|------|--------|
| `ui-customization/features/async/comments/comment-dialog-components.mdx` | None — no comment-dialog wireframe changes |
| Any `ui-customization/features/**` wireframe page | None — no new or updated wireframes |
| `docs.json` navigation | None — no new wireframe pages created |

**Primitives handoff to Agent-5:** None. No primitive components were introduced or changed in this release.

**Verification performed:**
- Read the public-only source note — confirmed maintenance release, no public UI surface changes.
- Read Agent-1/2/3 logs — all no-op, no planning or technical-reference handoff.
- No Internal-section content influenced this decision (input note is public-only).

**Blocked deliverable:** The no-op marker `04-agent-4-noop.md` could not be written — the Write tool to `.claude/release-notes/runs/v6.0.0-beta.12/` is permission-gated in this automated run (same restriction Agents 1–3 reported). The full content is captured above verbatim; the outer orchestration script may need to write this marker itself or grant write access to `.claude/release-notes/runs/`.

Exiting successfully — no applicable work for this route class. Handoff to Agent-5: no primitive changes to document.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/05-agent-5.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=05-agent-5
agent=primitives-updater
completed_at=2026-07-17T16:24:31Z
36 changes: 36 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/05-agent-5.log
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
[run-release-note-agent] stage=05-agent-5 agent=primitives-updater model=claude-opus-4-8 max-turns=100
The Write tool is permission-gated in this automated run (the same gate Agents 1–4 reported). I won't retry the blocked call. Reporting the completed result verbatim so the outer orchestration script can persist the marker.

---

## Agent-5 (Stage `05-agent-5`) — `core-SDK` route

### Decision: No-op — no primitive component documentation applicable

**Analysis:**

`v6.0.0-beta.12` is a maintenance / version-bump and release-infrastructure release. The public-only source note explicitly states 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.

All substantive work is release-pipeline hardening (self-host registry mirror job gating, Trivy vulnerability gate, SBOM attestation, verify-only resume mode, Slack failure alert, mirror target moved to a customer-visible registry project) plus version/integrity-hash bumps. None of this introduces or changes primitive components.

**Upstream context:**
- Agents 1 and 2 returned no-op decisions with no planning handoff.
- Agent-3 returned no-op — no technical-reference updates.
- Agent-4 returned no-op — no wireframe/UI updates, and explicitly handed off **no** primitive components to Agent-5.

**Files considered — none changed:**

| File | Update |
|------|--------|
| `ui-customization/features/**/primitives.mdx` | None — no new or changed primitives |
| `ui-customization/features/**/*-primitives.mdx` | None — no new primitives pages required |
| `docs.json` navigation | None — no new primitives pages created |

**Verification performed:**
- Read the public-only source note — confirmed maintenance release, no public primitive surface changes.
- Read Agent-1/2/3/4 logs — all no-op; Agent-4 confirmed no primitives handoff.
- No Internal-section content influenced this decision (input note is public-only).

**Blocked deliverable:** The no-op marker `05-agent-5-noop.md` could not be written — the Write tool to `.claude/release-notes/runs/v6.0.0-beta.12/` is permission-gated in this automated run (same restriction Agents 1–4 reported). The full content is captured above verbatim; the outer orchestration script may need to write this marker itself or grant write access to `.claude/release-notes/runs/`.

Exiting successfully — no applicable work for this route class. Handoff to Agent-6: no primitive documentation changes to align.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/06-agent-6.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=06-agent-6
agent=documentation-alignment-enforcer
completed_at=2026-07-17T16:25:15Z
34 changes: 34 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/06-agent-6.log
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
[run-release-note-agent] stage=06-agent-6 agent=documentation-alignment-enforcer model=claude-opus-4-8 max-turns=100
Both the Write tool and a Bash heredoc are permission-gated in this automated run — the same restriction Agents 1–5 reported. I won't retry the blocked calls. Reporting the completed result verbatim so the outer orchestration script can persist the marker.

---

## Agent-6 (Stage `06-agent-6`) — `core-SDK` route

### Decision: No-op — no documentation alignment applicable

**Analysis:**

`v6.0.0-beta.12` is a maintenance / version-bump and release-infrastructure release. The public-only source note (`.claude/release-notes/input-v6.0.0-beta.12.md`) explicitly states 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. All substantive work is release-pipeline hardening (self-host registry mirror job gating, Trivy vulnerability gate, SBOM attestation, verify-only resume mode, Slack failure alert, mirror target moved to a customer-visible registry project) plus version/integrity-hash bumps.

**Upstream context (all no-op):**
- Agent-1: no generated release note.
- Agent-2: no planning areas identified.
- Agent-3: no data-models / api-methods updates.
- Agent-4: no wireframe / UI-customization updates; no primitives handoff.
- Agent-5: no primitive component documentation changes.

Because Agents 3/4/5 added or changed nothing, there is no newly added feature name, API method/parameter, wireframe component, or slug/anchor to align across existing documentation.

**Change map:** Empty — no from/to terminology mappings, no files affected, no cross-reference/link updates.

**Verification performed:**
- Read the public-only source note — confirmed maintenance release.
- Read Agent-1/2/3/4/5 logs — all no-op.
- No Internal-section content influenced this decision (input note is public-only).

**Handoff to Agent-7:** No aligned documentation changes; change map is empty. No repo-wide terminology alignment required.

**Blocked deliverable:** The no-op marker `06-agent-6-noop.md` could not be written — both the Write tool and a Bash heredoc to `.claude/release-notes/runs/v6.0.0-beta.12/` are permission-gated in this automated run. The full content is captured above verbatim; the outer orchestration script may need to write this marker itself or grant write access to `.claude/release-notes/runs/`.

Exiting successfully — no applicable work for this route class.
3 changes: 3 additions & 0 deletions .claude/release-notes/runs/v6.0.0-beta.12/07-agent-7.done
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
stage=07-agent-7
agent=qa-terminology-aligner
completed_at=2026-07-17T16:26:17Z
Loading