chore(release): 0.83.0

[Tjemmmic]

Overview

Publishes the workflow-graph density-toggle work merged in #178: deterministic fit-on-toggle computed from the layout's own geometry, density-aware zoom ceiling (compact fits up to 1.5×), the geometry+camera layout tween with the mid-morph density swap and content fade, and the write-time run-state merge inside the tween.

[Tjemmmic]

🤖 AI Code Review (ensemble)

Summary

This PR is a metadata-only version bump from 0.82.0 to 0.83.0 in package.json. All three reviewers correctly identified that there are no functional, security, or architectural concerns in this diff.

No Issues Found

✅ APPROVE

The diff contains only a single-line version bump with no runtime, API, or configuration changes. There are no bugs, security risks, or testing gaps to flag in a metadata-only release update.

---

Synthesized by Sokuza AI from multiple independent reviewers

[tangletools]

✅ No Blockers — c0c41002

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

	glm	kimi-code	aggregate
Readiness	92	95	92
Confidence	65	65	65
Correctness	92	95	92
Security	92	95	92
Testing	92	95	92
Architecture	92	95	92

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

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

🟡 LOW CHANGELOG.md missing 0.83.0 (and 0.82.0) entry — package.json

CLAUDE.md states 'CHANGELOG.md is hand-maintained — add an entry when bumping the version.' The current CHANGELOG.md top entry is 0.81.0 (lines 1-40 verified). This PR bumps to 0.83.0 with no CHANGELOG update in this shot, and 0.82.0 is also absent — so two consecutive releases lack changelog entries. The release workflow does not gate on this, so it is non-blocking, but downstream consumers and the generated GitHub Release lose human-readable release notes. Fix: add a ## 0.83.0 section to CHANGELOG.md describing the changes since 0.81.0 before merge.

---

_{tangletools · 2026-07-15T03:14:05Z · trace}

[tangletools]

✅ Approved — 1 non-blocking finding — c0c41002

Full multi-shot audit completed 1/1 planned shots over 1 changed files. Global verifier still owns final merge decision. | Full multi-shot audit completed 1/1 planned shots over 1 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-07-15T03:14:05Z · immutable trace}

[tangletools]

🟡 Value Audit — sound-with-nits

Verdict	sound-with-nits
Concerns	1 (1 weak-concern)
Heuristic	0.0s
Duplication	0.0s
Interrogation	132.7s (2 bridge agents)
Total	132.7s

💰 Value — sound-with-nits

Single-line version bump 0.82.0 → 0.83.0 in package.json that fires the documented Auto Release & Publish flow to ship the already-merged workflow-graph density-toggle work (#178); correct mechanism and correct semver size, with only a skipped CHANGELOG entry as a nit.

• What it does: Changes version in package.json from 0.82.0 to 0.83.0 (package.json:3). Per CLAUDE.md ('Release flow') and .github/workflows/release.yml, a push to main that changes package.json's version triggers build + npm publish of @tangle-network/sandbox-ui@0.83.0 plus GitHub Packages and a GitHub Release. No code changes — the shipped content is commit 4531350 (#178), which contains feat and fix commits
• Goals it achieves: Publish the merged #178 work (deterministic density-toggle fit, density-aware 1.5× compact zoom ceiling, geometry+camera morph with run-state merge) to npm as 0.83.0 so the consumer bump in agent-dev-container#3615 can pin it. This repo's release model is 'bumping the version is the release trigger' (CLAUDE.md), so a dedicated release PR after a feature merges without a bump is exactly how the sys
• Assessment: Good on its merits. It uses the repo's one sanctioned release mechanism, the minor (not patch) bump matches #178's feat content, and git history confirms the pattern (chore(release) commits interleaved with feature merges — e.g. 33757d2, 8ab95ac). The one deviation: CLAUDE.md says 'CHANGELOG.md is hand-maintained — add an entry when bumping the version,' yet CHANGELOG.md's top entry is 0.81.0 (CHA
• Better / existing approach: none — this is the right approach. The version-field-on-package.json trigger is the documented, automated release path (CLAUDE.md 'Release flow', release.yml OIDC publish); there is no alternate release mechanism in the repo to prefer, and folding the bump into #178 vs. a standalone release PR is a wash (both patterns already exist in git history: #174 bumped+released inline, #177/#178 split it).
• Model: opencode/kimi-for-coding/k2p7
• Bridge attempts: 1

🎯 Usefulness — sound

A clean version-bump release PR that fires the repo's documented auto-publish pipeline for already-merged, tested, reachable WorkflowGraph density-toggle work.

• Integration: The change (a package.json version bump 0.82.0 → 0.83.0) is the repo's documented release trigger: release.yml fires on push to main with paths:[package.json], detects the new version, and publishes to npm + GitHub Packages + creates a GitHub Release. The shipped functionality (density-toggle fit, zoom ceiling, layout tween, run-state merge) lives in src/workflows/WorkflowGraph.tsx, is exported vi
• Fit with existing patterns: Follows the established release pattern exactly — prior releases used the same version-bump-triggers-publish mechanism (e.g. 0.71.0 at commit 33757d2). The functionality being released continues the WorkflowGraph redesign lineage (#170→#178) without introducing a competing pattern.
• Real-world viability: The published work has regression tests (WorkflowGraphFitView.test.tsx drives a mid-tween status tick and asserts the final frame keeps it; WorkflowNode.test.tsx covers density toggle). The release pipeline is idempotent (release.yml gates on gh release view v${VERSION} not existing) and concurrency-serialized, so a re-push won't double-publish.
• Model: opencode/zai-coding-plan/glm-5.2
• Bridge attempts: 1

💰 Value Audit

🟡 Version bump skips the hand-maintained CHANGELOG (0.82.0 and 0.83.0 both absent) [maintenance] ``

CLAUDE.md's Release flow section states 'CHANGELOG.md is hand-maintained — add an entry when bumping the version,' but CHANGELOG.md's newest entry is 0.81.0 (line 3); grep '^## ' CHANGELOG.md shows no 0.82.0 or 0.83.0. #178's density-toggle work is substantive user-facing change (new morph behavior, new fit semantics) of exactly the kind the existing 0.76–0.81 entries document. Non-blocking for publish, but the release notes consumers read will jump from 0.81.0 to 0.83.0 with no record — worth

---

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 · 20260715T031528Z}