fix(release): inline bundled assets as string modules so JSR publish accepts them

[rickylabs]

Fix partial publish of v0.0.1-alpha.5 — inline bundled assets as string modules

The v0.0.1-alpha.5 whole-workspace JSR publish partial-failed: 23 of 31 members published, but @netscript/fresh-ui and @netscript/plugin were rejected and 6 dependents (incl. @netscript/cli) were skipped:

failed to build module graph: The import attribute type of 'text' is unsupported

Root cause — a deno publish defect, not a config gap

The bundled-asset barrels embedded each asset via a with { type: 'text' } import attribute. The deno publish module-graph build (the deno_graph crate) never sets unstable_text_imports, so it rejects text-attribute imports — even though text imports are otherwise stable and pass deno check, deno info, and deno publish --dry-run.

There is no flag or deno.json lever that force-enables it on the publish path:

• Text imports are stable, so there is deliberately no CLI flag for them.
• --unstable-raw-imports only toggles the separate bytes feature, which this workspace does not use. The flag added in a prior attempt was a no-op for the text error and is reverted here.
• deno publish --dry-run does not enforce the restriction, so publish:dry-run stayed green while the real publish failed — a true dry-run blind spot.

Fix

The assets-barrel generator now inlines each asset's content as a plain string constant:

const template_000 = ".ns-alert { ... }";   // was: import template_000 from '...' with { type: 'text' }

• The three generated barrels keep their exact export shapes — EMBEDDED_TEMPLATE_CONTENT, PLUGIN_SKELETON_TEMPLATE_CONTENT, FRESH_UI_REGISTRY_CONTENT (Record<…, string>) — so every consumer is unchanged and the runtime asset-read path is identical.
• Plain string constants carry no import attribute, so the publish graph builder has nothing to reject.
• The generator pipes its rendered output through deno fmt before writing, so the committed barrels are already fmt-canonical — check:assets-barrel (regen + git diff --exit-code) and fmt:check stay byte-stable.
• Removes the now-dead raw-imports from the workspace-root unstable list (no bytes imports exist repo-wide; text imports are stable).

Gates (all green)

Gate	Result
check:assets-barrel	exit 0 (deterministic regen)
deno task check	0 findings / 1735 files
deno task lint	0 occurrences
deno task fmt:check	0 findings
fresh-ui barrel + consumer deno check	exit 0
asset consumer unit tests	5/5 (incl. "reads embedded content without hydration", "no direct Deno.read")

Why re-publish is safe

deno publish skips versions already on the registry, so re-running after the partial publish is idempotent — the 23 already-published members are skipped; only fresh-ui, plugin, cli, and the 6 skipped dependents publish at alpha.5.

Follow-ups (tracked)

• deno publish --dry-run is a blind spot for this failure class — a real-publish-equivalent preflight is tracked under the deterministic JSR release/publish e2e (PR-C: alpha-1 legacy/deprecated purge + hygiene (breaking) #114).
• An upstream deno issue for the publish-graph unstable_text_imports gap will be filed.

🤖 Generated with Claude Code