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/brand@1.5.0

Minor Changes

• 532a6d8: Add --shadow-overlay, the elevation step above --shadow-dropdown for a surface that covers the page rather than sitting beside it — a drawer, a modal, a floating dock.

  It is derived from --hsl-foreground rather than a fixed rgba, so it inverts with the theme: dark ink in light, a soft halo in dark. That is what makes it work on a dark canvas, where a black shadow renders as nothing. One declaration serves both themes, and the token is declared in the @theme block as well so Tailwind emits a shadow-overlay utility.

[tangletools]

✅ Auto-approved GitHub Actions PR — 144398a2

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-12T23:08:19Z}

[tangletools]

🟢 Value Audit — sound

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

💰 Value — sound

Automated Changesets release bumping @tangle-network/brand 1.4.0→1.5.0 for the already-merged --shadow-overlay token; correct version, correct changelog, nothing to redesign.

• What it does: Bumps packages/brand/package.json from 1.4.0 to 1.5.0, appends a 1.5.0 CHANGELOG section generated from the consumed .changeset/shadow-overlay-token.md, and deletes that changeset. Three files, +9/-8, all generated by the Changesets action. The shipped feature is the --shadow-overlay elevation token, landed in commit 532a6d8 (#90): declared at packages/brand/src/styles/tokens.css:331 and re-declar
• Goals it achieves: Publish the --shadow-overlay design token to npm so consumers can use shadow-overlay (drawers/modals/floating docks) — a lift step above --shadow-dropdown for surfaces that cover the page. The minor bump reflects that this is purely additive: one new token, no breaking change to existing exports.
• Assessment: Textbook Changesets release flow. Version bump is correct (additive token → minor, not patch or major). CHANGELOG entry is accurate and references the real source commit. The consumed changeset is removed. The feature itself was reviewed and merged in #90 with parity tests (theme-parity.test.ts) guarding the tokens.css↔theme.css value equality. There is no design decision left in this PR — it is p
• Better / existing approach: none — this is the right approach. Searched packages/brand/src/styles/ for shadow-overlay: it lives in exactly the two files the release documents (tokens.css:331, theme.css:110) and is tested in theme-parity.test.ts. The release PR is the only mechanism this repo uses to publish (prior chore: release commits at 5f3882b, a27c1f0, 8f4c8d1 follow the same pattern), so reinventing it would fight the
• Model: opencode/zai-coding-plan/glm-5.2
• Bridge attempts: 2
• Bridge warning: opencode/kimi-for-coding/k2p7: opencode: opencode error

🎯 Usefulness — sound

Release bump for --shadow-overlay, a theme-inverting elevation token that extends the existing shadow ladder correctly and is reachable via both the CSS variable and the Tailwind shadow-overlay utility.

• Integration: Fully wired. The token is declared in tokens.css:331 (base/dark spine) and re-declared in theme.css:110 inside the @theme block, so Tailwind v4 emits a shadow-overlay utility — that is the documented consumer path (theme.css:108-109). Both files ship through the ./styles export (package.json:31-34 -> index.css -> tokens.css + theme.css). The token depends on --hsl-foreground, which is defined
• Fit with existing patterns: Slots cleanly into the established shadow ladder (--shadow-card, --shadow-dropdown, --shadow-glow, --shadow-accent) as the step above --shadow-dropdown, exactly the grain the codebase already uses. Follows the codebase convention of declaring tokens in both tokens.css and theme.css with a parity test (theme-parity.test.ts) guarding drift — the same pattern the surrounding shadows use. No competing
• Real-world viability: Holds up. It is a static CSS custom property derived from an existing token, so there are no concurrency or error paths. The self-inverting design (hsl(var(--hsl-foreground)) instead of fixed rgba) is the correct fix for the documented failure mode — a black shadow on a dark canvas renders as nothing (tokens.css:326-329). The light spine deliberately does not restate it (confirmed: tokens.css:655-
• 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 · 20260812T233748Z}

[tangletools]

✅ No Blockers — 144398a2

Review health 100/100 · Reviewer score 95/100 · Confidence 70/100 · 0 findings (none)

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

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.

No findings.

---

_{tangletools · 2026-08-12T23:38:06Z · trace}

[tangletools]

✅ Clean — 144398a2

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-12T23:38:06Z · immutable trace}