Release Token Tools 0.1.0

docs/ACCESSIBILITY.md

@@ -0,0 +1,3 @@
+# Accessibility
+
+Every editor has a native label. Token lists use buttons with visible selection, parse errors use alert regions, and validation never relies on colour alone. Tables provide header cells, export output is selectable text, the responsive layout becomes one column on narrow screens and the shared shell supplies visible focus and system/light/dark themes.

docs/ARCHITECTURE.md

@@ -0,0 +1,5 @@
+# Architecture
+
+The applied JSON document is separate from the editing draft, so malformed intermediate input never replaces the last valid state. `core/tokens.ts` extracts inherited nested tokens, composes ordered sets, resolves aliases through a guarded graph walk and validates resolved values. Export adapters consume only the selected theme's resolved records and append every unsupported conversion to a loss report.
+
+The `$sets`/`$themes` wrapper is local metadata; W3C-style export emits a plain nested `$type`/`$value` object. All Vite assets are relative for nested portal mounting, and release packaging fixes ordering, permissions and timestamps.

docs/PRIVACY-SECURITY.md

@@ -0,0 +1,5 @@
+# Privacy and security
+
+All input stays in memory in the current browser. CSP allows only same-origin connections and the application initiates none. There is no telemetry, storage, account or remote asset.
+
+Parsing is capped at 1 MiB, depth 64, 50,000 JSON values and 10,000 extracted tokens. Aliases are exact path references and cannot execute expressions. CSS/Sass strings, XML and Swift strings are target-escaped; normalized identifier collisions and unsupported composite values are recorded as explicit losses.