[KyleJune]

Summary

Running the Tailwind 4 test from this package inside the Udibo checkout fails when nested Deno resolution discovers Udibo's workspace and rejects the unregistered package config. Declare this package as its own workspace root so the nested resolver stops here.

Changes

• Add workspace: [] to this package's deno.json.
• Retain this package's independent lockfile and dependency policy. No parent workspace registration or starter dependency edits are needed.

Testing

• At 604a8383f173d9f107ca0d1ae7146be03208582f, deno task check passes (10 linted files, 45 formatting checks).
• Final deno task test --parallel --reporter=dot passes inside the Udibo checkout: 7 tests, 30 steps, zero failures.
• Negative control on current package main: removing only workspace: [] reproduces Config file must be a member of the workspace at plugins / tailwindcss 4 / should add tailwindcss to the css (6 tests, 28 steps pass; 1 test, 2 steps fail). Restoring it makes the full package gate pass.
• A standalone archive of this same commit outside the parent workspace also passes check and all 7 tests / 30 steps (6s), without approving install scripts.
• All four independent pinned reviews are CLEAN.
• Parent application validation and the pointer update will be recorded in a separate dependent Udibo PR.

Closes

Nothing. Refs udibo/udibo#1676; the parent pointer update completes that issue's integration.

[KyleJune]

At 604a8383f173d9f107ca0d1ae7146be03208582f, package checks and the full suite pass both inside Udibo and from a standalone committed snapshot: 7 tests / 30 steps, zero failures. Removing only the added workspace: [] line reproduces the exact Tailwind 4 nested-resolution failure; restoring it passes the final gate. All four pinned reviews are CLEAN. Parent application final checks and full tests are running for the dependent pointer integration. No package release was published.

[KyleJune]

Bug fixes

• Fix Tailwind 4 builds when the package is nested inside another Deno workspace. The package now declares its own workspace boundary. See fix: isolate nested package workspace #16.

The release workflow published this version to JSR, then failed while submitting provenance to the signing service. The published version and module are available; this release record restores the matching GitHub notes.