@adea-ai/themes 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,110 @@
+Copyright 2026 0xPlayerOne
+
+The Adea theme catalogue is distributed under the Apache License, Version 2.0.
+You may obtain a copy of the License at:
+
+https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed
+under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
+CONDITIONS OF ANY KIND, either express or implied. See the License for the
+specific language governing permissions and limitations under the License.
+
+---
+
+# Third-party palettes
+
+Every theme in this package except Adea's own two is **somebody else's palette**,
+reproduced rather than authored. This section records whose, under what terms, and
+where the specific bytes came from. The per-theme machine-readable form of the same
+information is on each catalogue entry's `provenance` field, and
+`tests/provenance.test.ts` asserts that the values match each project's published
+palette.
+
+## The chain of custody
+
+The colour values in `palettes/` were not typed in by hand, and they are not read
+from any package at runtime. They were produced once, by
+`scripts/vendor-palettes.ts`, which reproduces the Base24 scheme for each theme from
+one pinned revision of:
+
+- **oklch-terminal-themes** — https://github.com/williamzujkowski/oklch-terminal-themes
+  — revision `9e800e7fe760081d4c10317498038ed4227341d6` — MIT.
+  This is the bootstrap dataset. Its Base24 schemes are, in turn, derived from the
+  terminal ports published in:
+- **iTerm2-Color-Schemes** — https://github.com/mbadolato/iTerm2-Color-Schemes — MIT.
+
+`oklch-terminal-themes` is a build-time input only. It is not a dependency of this
+package, in either `dependencies` or `devDependencies`, and nothing here reads it at
+run time. What it contributed is a starting set of values, which was then checked
+against each palette's own project before being committed.
+
+## The palettes, and the terms they are used under
+
+Each entry names the project the palette belongs to — the place its design is
+defined and the authority on what "Catppuccin Mocha" means — and the licence the
+vendored values are used under. `tests/provenance.test.ts` asserts that the
+background and foreground of every one of these matches the project's published
+palette.
+
+| Family | Project | Licence | Vendored values |
+| --- | --- | --- | --- |
+| Adea | this package | Apache-2.0 | authored here |
+| Catppuccin | https://github.com/catppuccin/catppuccin | MIT | via the chain above |
+| Tokyo Night | https://github.com/folke/tokyonight.nvim | Apache-2.0 | via the chain above |
+| Rosé Pine | https://github.com/rose-pine/rose-pine-theme | MIT | via the chain above |
+| Gruvbox | https://github.com/morhetz/gruvbox | MIT | via the chain above |
+| Nord | https://github.com/nordtheme/nord | MIT | via the chain above |
+| Dracula | https://github.com/dracula/dracula-theme | MIT | via the chain above |
+| One Dark | https://github.com/atom/one-dark-syntax | MIT | Atom's own palette |
+| Solarized | https://github.com/altercation/solarized | MIT | via the chain above |
+| Everforest | https://github.com/sainnhe/everforest | MIT | via the chain above |
+| Ayu | https://github.com/ayu-theme/ayu-colors | MIT | via the chain above |
+| Kanagawa | https://github.com/rebelot/kanagawa.nvim | MIT | via the chain above |
+| Vesper | https://github.com/raunofreiberg/vesper | MIT | via the chain above |
+| Monokai | https://monokai.pro (design origin) | MIT | via the chain above |
+
+### Two entries that need a note
+
+**Gruvbox** grants the MIT/X11 licence in the *Licence* section of its README and
+ships no `LICENSE` file, which is why automated licence detection reports nothing
+for the repository. The README is the grant, and it is recorded here as MIT. The
+source for this statement is
+https://github.com/morhetz/gruvbox#license.
+
+**Monokai** is the one family whose own repository carries no licence at all: the
+repository under the Monokai organisation has none, so there is no permissively
+licensed artefact of Monokai's own to vendor from. The values in this package are
+therefore taken from the MIT-licensed iTerm2-Color-Schemes port through the chain
+above, which is the artefact the MIT licence attaches to, and Monokai is credited as
+the design's origin without a licence claim being made on its behalf. If Monokai's
+terms are ever clarified, this entry should be revisited — and if they turn out to
+be incompatible, `monokai` should be removed from `VENDORED_SOURCES` and the
+catalogue regenerated, which is a one-line change plus a rebuild.
+
+### One deliberate deviation from the vendored values
+
+**One Dark** is normalized from Atom's own editor palette rather than from the
+terminal port. iTerm2's One Dark port darkens the canvas to `#21252b` so that a
+terminal window reads as a distinct surface, but "One Dark" as a design means Atom's
+`hsl(220, 13%, 18%)` = `#282c34`, with comments at `#5c6370` rather than the port's
+`#767676`. Adea themes an application, so the project's value is the one used. The
+substitution is declared in `src/sources.ts` and reported as a finding on every
+build.
+
+---
+
+# Contrast repairs
+
+Some themes in this catalogue do not ship the exact colour a palette specifies for
+every role, because the palette's own value fails a contrast floor on the palette's
+own background. Solarized Light's body text is the clearest case: `#657b83` on
+`#fdf6e3` measures 4.28:1, below the WCAG AA floor of 4.5:1.
+
+Where that happens, the value's **lightness** is moved by the smallest amount that
+clears the floor, and nothing else is changed — OKLCH makes that a single-axis edit
+that preserves hue and chroma exactly, and `tests/provenance.test.ts` asserts the hue
+is unmoved. In the rare case where lightness alone cannot reach the floor, the colour
+is blended toward the palette's own foreground, which is recorded on the entry and
+reported on every build. No colour is ever invented: every value in the catalogue is
+a value from the palette it is attributed to, viewed at a different brightness.

package/README.md

@@ -0,0 +1,157 @@
+# @adea-ai/themes
+
+The Adea theme catalogue. Twenty-seven themes — every one an OKLCH theme with the
+full set of semantic surface roles, sixteen ANSI colours, a cursor and a selection —
+normalized from mature upstream palettes, with adapters for the places a theme has
+to arrive in a foreign shape.
+
+```sh
+bun add @adea-ai/themes
+```
+
+## The catalogue
+
+| Family | Variants |
+| --- | --- |
+| **Adea** | Light, Dark |
+| **Catppuccin** | Latte, Frappé, Macchiato, Mocha |
+| **Tokyo Night** | Day, Storm, Night |
+| **Rosé Pine** | Dawn, Moon, Main |
+| **Gruvbox** | Light, Dark |
+| **Everforest** | Light, Dark |
+| **Ayu** | Light, Mirage, Dark |
+| **Solarized** | Light, Dark |
+| **Monokai** | Classic |
+| **Nord**, **Dracula**, **One Dark**, **Kanagawa**, **Vesper** | one each |
+
+`adea-light` and `adea-dark` are the defaults. Everything else is somebody else's
+palette, reproduced from a named revision and credited in [NOTICE](NOTICE).
+
+## Using it
+
+```ts
+import { getTheme, themeFamilies, resolveTheme } from '@adea-ai/themes'
+import { themeCssVariables } from '@adea-ai/themes/adapters/css'
+import { toXtermTheme } from '@adea-ai/themes/adapters/xterm'
+import { toShikiTheme } from '@adea-ai/themes/adapters/shiki'
+
+// Apply a theme to the document.
+const theme = resolveTheme('catppuccin-mocha', 'dark')
+for (const [name, value] of Object.entries(themeCssVariables(theme))) {
+  document.documentElement.style.setProperty(name, value)
+}
+
+// Colour a terminal.
+terminal.options.theme = toXtermTheme(theme)
+
+// Register a syntax theme.
+const highlighter = await createHighlighter({ themes: [toShikiTheme(theme)], langs: [...] })
+```
+
+Every exported theme value is an `oklch()` string, which means the browser does the
+colour work and a consumer can compose — `color-mix(in oklch, var(--adea-accent),
+transparent 20%)` — and get a predictable result. The adapters that need hex (xterm,
+Shiki) convert, gamut-mapping rather than clipping.
+
+## The design, in four decisions
+
+**Adea owns the schema and the transformation, not the colours.** The seventeen
+surface roles in `src/schema.ts` are the contract. No upstream project is asked to
+satisfy it, and no palette is hand-authored here: `palettes/` holds Base24 schemes
+reproduced from a pinned revision, and `src/normalize.ts` is the single place a
+terminal palette becomes an application theme. Adding a theme is a line in
+`src/sources.ts` plus a rebuild.
+
+**OKLCH is the representation.** Perceptually uniform lightness is what makes a
+surface ladder buildable by adding fixed steps, a contrast failure repairable by
+moving one axis, and a theme re-hueable without re-deriving its ramp by eye.
+
+**Contrast is measured, not assumed.** Nothing enters the catalogue without clearing
+the floors in `src/validate.ts`, and `bun run catalogue:build` fails if a theme
+cannot be repaired within budget. The pipeline caught real defects that a
+hand-authored catalogue would have shipped:
+
+- Solarized Light's body text measures 4.28:1 on its own background — under WCAG AA.
+- Tokyo Night's black is 1.17:1 against its canvas, and Gruvbox Light's `white` was
+  resolving to a near-black, both from light schemes that invert Base24's greyscale
+  ramp.
+- Everforest Light contains no colour above 2.6:1 on its own canvas, so its status
+  and accent roles have to be deepened rather than used as published.
+
+**Derived colours are derived.** Syntax roles, chart series and status fills are
+functions of the roles a theme does hold (`src/derive.ts`), so two consumers cannot
+disagree about what colour a keyword is.
+
+## Base24 is a bridge, not the schema
+
+Base24 is an excellent interchange format and a poor application schema: it has a
+slot for the colour of a deprecated API and nothing that means "the surface one step
+above the card". So Base24 is how values get *in* and how they get *out*:
+
+```ts
+import { toBase24, formatBase24Scheme, parseBase24Scheme } from '@adea-ai/themes'
+import { getBase24Scheme } from '@adea-ai/themes'
+
+formatBase24Scheme(toBase24(getTheme('nord')!))   // a Base24 scheme
+getBase24Scheme('nord')                            // the vendored original, untouched
+```
+
+`toBase24` re-derives Base24's orange and brown slots, because Adea's schema has no
+role for them; `getBase24Scheme` returns the artefact as reproduced, for callers that
+need it byte-for-byte. The mapping is documented in `src/adapters/base24.ts`.
+
+## Adapters
+
+| Import | For | Output |
+| --- | --- | --- |
+| `adapters/css` | the application | CSS custom properties in OKLCH |
+| `adapters/tailwind` | the application | a Tailwind v4 `@theme inline` block |
+| `adapters/shadcn` | this org's components | the shadcn vocabulary, bridged from the same source |
+| `adapters/xterm` | shells | xterm.js's hex-only `ITheme` |
+| `adapters/shiki` | code views | a Shiki theme registration |
+| `adapters/base24` | interop | Base24, both directions |
+
+The shadcn bridge is worth knowing about before you read the code: Adea's `accent`
+becomes shadcn's **`primary`**, because in shadcn `--primary` is the action colour and
+`--accent` is a hover wash. Mapping it the other way turns every primary button grey.
+The mapping is in `src/adapters/shadcn.ts`.
+
+## Working on it
+
+```sh
+bun install
+bun run verify          # typecheck, lint, catalogue freshness, tests, build
+bun run catalogue:build # regenerate src/generated from palettes/ and sources.ts
+bun run catalogue:check # fail if the committed catalogue is stale
+bun run vendor          # refresh palettes/ from the pinned upstream revision
+```
+
+The generated catalogue is **committed**, and `catalogue:check` fails when it and its
+inputs disagree. A palette change is therefore a reviewable diff rather than an
+invisible drift.
+
+`palettes/` is regenerated by `bun run vendor`, which reproduces Base24 schemes from
+a revision pinned in `src/sources.ts`. To adopt a newer upstream, change
+`CATALOGUE_REVISION`, run `vendor`, then `catalogue:build` and read the diff — the
+build prints every value it repaired and why.
+
+### Adding a theme
+
+1. Add its Base24 scheme to `palettes/` (or let `vendor` fetch it: add the slug to
+   `VENDORED_SOURCES` in `src/sources.ts` first).
+2. Record its family's project, URL and licence in `FAMILY_PROVENANCE`, and its
+   entry in `VENDORED_SOURCES` — id, labels, description, appearance, tags.
+3. Declare `accentSlot` if the family's identity is not in its blue slot. Everforest
+   is green, Rosé Pine is iris, Monokai is magenta.
+4. Add a fidelity assertion to `tests/provenance.test.ts`. The suite fails without
+   one — a theme cannot be added without recording where its colours come from.
+5. `bun run catalogue:build && bun run verify`.
+
+If the build reports a role it could not repair within budget, the answer is a
+decision rather than a tweak: either the palette genuinely cannot express that role,
+in which case say so in the entry's description, or the floor is wrong, in which case
+change it in `CONTRAST_FLOORS` and justify it there.
+
+## Licence
+
+Apache-2.0. The palettes are not: see [NOTICE](NOTICE) for each project and its terms.

package/dist/adapters/base24.d.ts

@@ -0,0 +1,117 @@
+/**
+ * The Base24 bridge.
+ *
+ * Base24 is the interchange format this package speaks to the outside world, in
+ * both directions. Importing is the normalizer's first step for every theme that
+ * is not authored here ({@link "./normalize"}); exporting is how a theme reaches a
+ * terminal, a tmux theme, or another tool that has never heard of Adea.
+ *
+ * ## The slot order is not the ANSI order
+ *
+ * Base24's `base12`–`base17` are *bright red, bright yellow, bright green, bright
+ * cyan, bright blue, bright magenta* — the order Base16 needed to keep its ramps
+ * monotonic, not the ANSI order of yellow before green. Reading them positionally
+ * as ANSI 1–6 silently swaps green and yellow and blue and cyan, which is the kind
+ * of mistake that survives review because the theme still *looks* like itself.
+ * {@link BASE24_TO_ANSI} names the mapping explicitly so it cannot be inferred
+ * wrongly.
+ *
+ * ## The two slots with no Adea role
+ *
+ * `base09` (orange) and `base0F` (brown) have no counterpart in the canonical
+ * schema: Adea has no "constant" or "deprecated" role, because a UI does not. On
+ * export they are re-derived from `red` and `yellow` by a fixed rotation, and
+ * {@link AdeaThemeRecord} carries the vendored schemes separately for callers who
+ * need the originals byte-for-byte. Round-tripping is therefore lossless for every
+ * role Adea models, and explicitly approximate for the two it does not — rather
+ * than silently lossy, which is what an unnamed slot would have been.
+ */
+import type { AdeaTheme, AdeaThemeColors } from '../schema';
+import type { Oklch } from '../oklch';
+/** The twenty-four Base24 slots, in the order the specification lists them. */
+export declare const BASE24_SLOTS: readonly ["base00", "base01", "base02", "base03", "base04", "base05", "base06", "base07", "base08", "base09", "base0A", "base0B", "base0C", "base0D", "base0E", "base0F", "base10", "base11", "base12", "base13", "base14", "base15", "base16", "base17"];
+export type Base24Slot = (typeof BASE24_SLOTS)[number];
+/** A Base24 palette. Values are colours in any notation {@link parseColor} accepts. */
+export type Base24Palette = Readonly<Record<Base24Slot, string>>;
+/** A Base24 scheme: the palette plus the metadata the specification defines. */
+export interface Base24Scheme {
+    system: 'base24';
+    name: string;
+    author: string;
+    variant: 'dark' | 'light';
+    palette: Base24Palette;
+}
+/**
+ * What each slot means, in the specification's own terms.
+ *
+ * Kept as data because the normalizer reads it rather than hard-coding slot names
+ * in its logic, and because it is the documentation a reader needs to check that
+ * the mapping is right.
+ */
+export declare const BASE24_SLOT_MEANING: Readonly<Record<Base24Slot, string>>;
+/**
+ * Base24 slot → ANSI role.
+ *
+ * `black`, `white` and `brightBlack` are absent because Base24 does not name them:
+ * the background and foreground slots do double duty. The normalizer decides those
+ * three; see its `ANSI_FROM_BASE24` note for why the choice is the one it is.
+ */
+export declare const BASE24_TO_ANSI: Readonly<{
+    readonly red: "base08";
+    readonly yellow: "base0A";
+    readonly green: "base0B";
+    readonly cyan: "base0C";
+    readonly blue: "base0D";
+    readonly magenta: "base0E";
+    readonly brightRed: "base12";
+    readonly brightYellow: "base13";
+    readonly brightGreen: "base14";
+    readonly brightCyan: "base15";
+    readonly brightBlue: "base16";
+    readonly brightMagenta: "base17";
+}>;
+/** The inverse of {@link BASE24_TO_ANSI}, for export. */
+export declare const ANSI_TO_BASE24: Readonly<Record<string, Base24Slot>>;
+/**
+ * How each semantic role is written back to a Base24 slot on export.
+ *
+ * The choices are not arbitrary. `base01` receives `black` rather than the
+ * background because an ANSI black that equals the background is invisible as
+ * foreground text — which is precisely the defect the import side documents. The
+ * surface ladder has no Base24 slot at all, so it is deliberately absent here:
+ * Base24 cannot express it, and pretending otherwise by packing four rungs into
+ * `base01`/`base02` would make the export lie about what it preserves.
+ */
+export declare const THEME_TO_BASE24: Readonly<Record<keyof AdeaThemeColors, Base24Slot | undefined>>;
+/** Thrown when a palette is missing a slot or holds an unparseable colour. */
+export declare class Base24ParseError extends Error {
+    readonly slot: string;
+    constructor(message: string, slot: string);
+}
+/** Parses every slot of a palette into OKLCH, or throws naming the offending slot. */
+export declare function parseBase24Palette(palette: Base24Palette): Record<Base24Slot, Oklch>;
+/**
+ * Writes a theme back to Base24.
+ *
+ * `base09` and `base0F` are synthesised — see this module's header. `base10` and
+ * `base11` are the two rungs below `base00`, which is what the specification
+ * defines them as and what a terminal needs in order to draw a black that is
+ * darker than the background.
+ */
+export declare function toBase24(theme: AdeaTheme, options?: {
+    author?: string;
+    name?: string;
+}): Base24Scheme;
+/** Serialises a scheme to the YAML dialect Base24 schemes are published in. */
+export declare function formatBase24Scheme(scheme: Base24Scheme): string;
+/**
+ * Reads the YAML dialect Base24 schemes are published in.
+ *
+ * Hand-written rather than pulled from a YAML library: the format is a fixed set
+ * of scalar keys, the package has no runtime dependencies and no build-time
+ * dependencies beyond the TypeScript compiler, and a general parser would accept
+ * documents this bridge cannot actually honour. Anything outside the specification
+ * is rejected loudly instead of being parsed into a half-scheme.
+ */
+export declare function parseBase24Scheme(source: string): Base24Scheme;
+//# sourceMappingURL=base24.d.ts.map

package/dist/adapters/base24.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"base24.d.ts","sourceRoot":"","sources":["../../src/adapters/base24.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AAEH,OAAO,KAAK,EAAY,SAAS,EAAE,eAAe,EAAE,MAAM,WAAW,CAAA;AACrE,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,UAAU,CAAA;AAGrC,+EAA+E;AAC/E,eAAO,MAAM,YAAY,2PAyBf,CAAA;AAEV,MAAM,MAAM,UAAU,GAAG,CAAC,OAAO,YAAY,CAAC,CAAC,MAAM,CAAC,CAAA;AAEtD,uFAAuF;AACvF,MAAM,MAAM,aAAa,GAAG,QAAQ,CAAC,MAAM,CAAC,UAAU,EAAE,MAAM,CAAC,CAAC,CAAA;AAEhE,gFAAgF;AAChF,MAAM,WAAW,YAAY;IAC3B,MAAM,EAAE,QAAQ,CAAA;IAChB,IAAI,EAAE,MAAM,CAAA;IACZ,MAAM,EAAE,MAAM,CAAA;IACd,OAAO,EAAE,MAAM,GAAG,OAAO,CAAA;IACzB,OAAO,EAAE,aAAa,CAAA;CACvB;AAED;;;;;;GAMG;AACH,eAAO,MAAM,mBAAmB,EAAE,QAAQ,CAAC,MAAM,CAAC,UAAU,EAAE,MAAM,CAAC,CAyBnE,CAAA;AAEF;;;;;;GAMG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;EAasC,CAAA;AAEjE,yDAAyD;AACzD,eAAO,MAAM,cAAc,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,UAAU,CAAC,CAI/D,CAAA;AAED;;;;;;;;;GASG;AACH,eAAO,MAAM,eAAe,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,eAAe,EAAE,UAAU,GAAG,SAAS,CAAC,CAmBxF,CAAA;AAEJ,8EAA8E;AAC9E,qBAAa,gBAAiB,SAAQ,KAAK;IAGvC,QAAQ,CAAC,IAAI,EAAE,MAAM;gBADrB,OAAO,EAAE,MAAM,EACN,IAAI,EAAE,MAAM;CAKxB;AAED,sFAAsF;AACtF,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,aAAa,GAAG,MAAM,CAAC,UAAU,EAAE,KAAK,CAAC,CAcpF;AAcD;;;;;;;GAOG;AACH,wBAAgB,QAAQ,CACtB,KAAK,EAAE,SAAS,EAChB,OAAO,GAAE;IAAE,MAAM,CAAC,EAAE,MAAM,CAAC;IAAC,IAAI,CAAC,EAAE,MAAM,CAAA;CAAO,GAC/C,YAAY,CAgDd;AAQD,+EAA+E;AAC/E,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,YAAY,GAAG,MAAM,CAU/D;AAED;;;;;;;;GAQG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,MAAM,GAAG,YAAY,CAwD9D"}