chore: release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tangle-network/ui@11.4.0

Minor Changes

• ef1be75: Publish the redaction renderer on its own ./redaction subpath.

  RedactedDocument is the client half of agent-app's reversible redaction: agent-app builds a document of masked spans and reveals one at a time through revealSpan, where authorization and the audit record happen, and this component renders that document and calls back for a reveal. It reached the package only through the root entry, and no consumer imports the bare package — every app takes ui through a subpath — so the component was unreachable in practice.

  The module gains a header stating what it pairs with, including why its segment type omits the cipher that agent-app's carries: the ciphertext stays on the server, so the type a browser holds cannot name it.

• b7c12be: RunRowShell's title prop widens from string to ReactNode — purely additive (strings render unchanged). Lets a row carry a treated title (e.g. an active-state shimmer sweep) so consumers composing the canonical run-row grammar don't have to re-fork the shell for it.

[tangletools]

✅ Auto-approved GitHub Actions PR — 894fbb36

This PR was opened by trusted GitHub Actions automation.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: github_actions_author · 2026-08-13T18:34:41Z}

[tangletools]

🟢 Value Audit — sound

Verdict	sound
Concerns	0 (none)
Heuristic	0.0s
Duplication	0.0s
Interrogation	36.2s (2 bridge agents)
Total	36.2s

💰 Value — sound

Automated changesets version bump (11.3.0→11.4.0) releasing an already-merged, backwards-compatible type widening of RunRowShell's title prop; nothing to redirect.

• What it does: Bumps @tangle-network/ui from 11.3.0 to 11.4.0 in packages/ui/package.json:4. This is the sole diff. It is the Changesets-action release snapshot for the minor change in commit b7c12be, which widened RunRowShellProps.title from string to ReactNode (packages/ui/src/run/run-row-shell.tsx:35).
• Goals it achieves: Publish the ReactNode title-widening to npm so consumers can compose treated titles (shimmer sweeps, live counters) into the canonical run-row grammar without re-forking the shell. The version bump is the mechanism that ships it.
• Assessment: Coherent and correct. The released feature is a strictly additive, backwards-compatible type widening (strings render unchanged), which is exactly the kind of change a minor bump is for. The release PR follows the repo's established changesets workflow — the git log shows a long cadence of identical chore: release commits (89, 84, 82, 80...). One file changed, one line, correct semver minor.
• Better / existing approach: none — this is the right approach. A version bump in a release PR is the only artifact this change produces; there is no architecture to reconsider. The underlying feature (title: string → ReactNode) is the idiomatic way to allow richer title content and matches the codebase's existing pattern where icon is already ReactNode (run-row-shell.tsx:34).
• Model: opencode/zai-coding-plan/glm-5.2
• Bridge attempts: 2
• Bridge warning: opencode/kimi-for-coding/k2p7: opencode: opencode error

🎯 Usefulness — sound

Routine changesets release PR — bumps @tangle-network/ui 11.3.0→11.4.0 and publishes the already-merged, backward-compatible ReactNode title widening; nothing to flag.

• Integration: The release is the integration mechanism: the changesets action publishes @tangle-network/ui@11.4.0 to npm on merge (stated in the PR body). The version bump in packages/ui/package.json:4 and the CHANGELOG entry at packages/ui/CHANGELOG.md:3-7 both correspond exactly to the consumed .changeset/run-row-shell-title-reactnode.md (which declares "@tangle-network/ui": minor). The feature being releas
• Fit with existing patterns: Changesets is the established release pattern in this repo — git log shows 10+ prior chore: release commits (e.g. 22e1e45, 5f3882b, a27c1f0), each structured identically (version bump + CHANGELOG + consume changeset). The released feature fits the codebase grain: RunRowShell is explicitly the 'canonical run-row grammar' (run-row-shell.tsx:73-78) shared by reasoning and tool rows, and widening a
• Real-world viability: A version bump and changelog edit have no runtime surface to break under load, concurrency, or edge inputs. The shipped feature itself is robust: title renders inline in the shell's title slot regardless of type, strings render unchanged, and the row's own title-slot styling still applies (run-row-shell.tsx:35-38 doc comment confirms this is the intent). The only new capability — passing a node li
• Model: opencode/zai-coding-plan/glm-5.2
• Bridge attempts: 1

No concerns — sound change, no better or existing approach found. ✅

---

What this audit checks

It judges the change on its merits — not whether it was tasked out in an issue. Unticketed, fast-moving work is fine; the question is whether the change is good and whether a better or existing approach should be used instead.

Pass	What it asks
Heuristic	Vague title? Whitespace-only or cruft-bearing diff? (content signals only)
Duplication	Do added function/class names already exist elsewhere in the repo?
Value Audit	What does it do? What goal does it achieve? Is it good? Better architecture or already-exists?
Usefulness Audit	Does it integrate and fit? Will it hold up in real use and actually get used?

Findings are concerns, not blocks — the human reviewer decides what to do with them.

_{value-audit · 20260813T183708Z}

[tangletools]

✅ No Blockers — 894fbb36

Review health 100/100 · Reviewer score 92/100 · Confidence 70/100 · 1 finding (1 low)

	opencode GLM 5.2	opencode DeepSeek v4 Pro	opencode DeepSeek v4 Flash	aggregate
Readiness	95	95	92	92
Confidence	70	70	70	70
Correctness	95	95	92	92
Security	95	95	92	92
Testing	95	95	92	92
Architecture	95	95	92	92

Reviewer score is advisory once the run is complete and the verdict has no blockers.

Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision. | Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision. | Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision.

🟡 LOW CHANGELOG references a short commit hash instead of a PR link — packages/ui/package.json

The release links the changelog line to commit hash 'b7c12be' (per the sibling CHANGELOG diff). This matches the repo's existing convention, so it is a nit, not a defect; noted only for traceability. Does not affect the version bump in this file.

---

_{tangletools · 2026-08-13T18:37:44Z · trace}

[tangletools]

✅ Approved — 1 non-blocking finding — 894fbb36

Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision. | Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision. | Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision.

Full immutable report for this review: trace

Summary comment for this run: full summary

---

_{tangletools · 2026-08-13T18:37:44Z · immutable trace}

[tangletools]

✅ Auto-approved GitHub Actions PR — 08a12729

This PR was opened by trusted GitHub Actions automation.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

This approval is provisional. It rests on the audit running. If the audit cannot run — for example the CLI bridge rejects it — this approval is dismissed rather than left standing, so an unrun check never reads as a passing one.

_{tangletools · auto-approval · reason: github_actions_author · 2026-08-13T19:23:30Z}