v0.6.1

Fixed

• A style module that lives outside the application's build root now loads its own generated CSS, in development and in production, under any public base. This is the ordinary shape for a source-shipping component library — a package whose *.css.ts files are compiled by the application that consumes them — and in v0.6.0 its stylesheets failed to resolve at every base. Hot updates to such modules now reach the browser as well, so editing a shipped component swaps its styles without a reload.

Changed

• Compiler-owned stylesheets now share one internal address scheme under the artifact directory inside the build root. This is internal: no consumer-visible identity, asset name, or API moves, and production output is unchanged. The development-server URL for a stylesheet now sits under that directory, so a stylesheet's request path in browser tools reads /.vanity/virtual/style/… while its filename stays the one it had.

No upgrade action is required.