j3w1 1.2.0 — terminal themes for Orca, Warp and Ghostty

The j3w1 theme now ships terminal themes you can download and import: Orca, Warp and Ghostty. The component package's implementation identity also stops reacting to unrelated dependency changes.

Terminal themes (experimental)

File	Import	Carries
config.ghostty	Orca → Settings → Terminal → Import from Ghostty, after saving it as %APPDATA%\ghostty\config.ghostty on Windows (or ~/.config/ghostty/config.ghostty)	terminal colours, cursor text, selection, all sixteen ANSI slots, pane divider, font SauceCodePro NFM at 13 px
j3w1.yaml	Warp themes folder, or Orca's Import from YAML / Import from Warp	terminal colours, accent
j3w1	Ghostty: ~/.config/ghostty/themes/j3w1, then theme = j3w1	terminal colours, selection, divider

Each file is generated from the default profile's tokens and its mapping.json. Every role a format cannot carry is recorded with a reason. Downloads are also in the README and on the Ports page. Install and rollback steps are in each port's README under ports/.

On Windows, prefer config.ghostty. Orca's YAML import gives each file one second, and that includes starting its parser, so on a busy machine it can report "Theme file took too long to parse" for any file. The Ghostty import has no such limit.

The files pass Orca 1.4.209's own YAML and Ghostty parsers. No real application import is recorded yet, so all three ports stay experimental.

Package

• @j3w1/ui 1.2.0: each component's implementationId hashes its definition and the exact emitted modules its class reaches (#50). A lockfile or tooling change that leaves a component's runtime code alone no longer moves its id. Before, any such change moved all 67 ids.
• The bundled entities licence notice now comes from the copy parse5 actually bundles. The text is unchanged.
• Every component class carries version = "1.2.0", so this release moves each id once.

Download j3w1-ui-1.2.0.tgz, verify it against release.json, then install it:

npm install --save-exact ./j3w1-ui-1.2.0.tgz

No token values change.

Verification

The delivery workflow ran on revision 0838171 and passed:

• source validation, generated-artifact checks and the source tests
• the build and distribution tests
• 63 packed-consumer checks across Chromium, Firefox and WebKit
• 234 specification browser checks (134 scoped skips)
• the verification-report gates

It then deployed. The attached tarball, evidence and theme files come from that run and match the deployed site byte for byte. delivery-provenance.json binds the release to the revision, the run, and the tarball and theme-file digests.

This is automated implementation evidence. There is no manual screen-reader, physical-device or independent acceptance claim, and no npm registry publication; registry publication remains an owner release action. The v1.0.0 and v1.1.0 tags remain immutable.