anentrypoint-design 0.0.322 → 0.0.324

package/colors_and_type.css

@@ -535,6 +535,49 @@ select:focus-visible {
   }
 }
 
+/* ============================================================
+   Semantic alias tier — primitive -> semantic -> component
+   ------------------------------------------------------------
+   Three layers, in order:
+     1. PRIMITIVE  (above)  raw palette values: --acid, --green, --sky, --warn,
+        --panel-1/2/3, --paper/--ink, etc. These are the only tokens that ever
+        carry a literal color/length. A re-brand edits primitives.
+     2. SEMANTIC   (here)   named-by-INTENT aliases that resolve to a primitive
+        (e.g. --accent: var(--panel-accent)). A component or a future re-brand
+        can retune ONE semantic variable (say, --rail-danger) without hunting
+        through every primitive it happens to reuse elsewhere.
+     3. COMPONENT  (app-shell.css, community.css, etc.) component sheets keep
+        consuming primitives directly today (--accent, --panel-*, --green,
+        --warn, ...) exactly as before — this tier does not repoint any
+        existing component rule. It exists so a FUTURE swap has a semantic
+        layer ready to migrate onto, one component sheet at a time, without
+        a flag-day rewrite. Purely additive: no primitive token's name or
+        value changes here, and no component references these new names yet.
+
+   Naming matches vocabulary already established elsewhere in this system:
+   --surface-1/2 mirror the --panel-1/--panel-2 tonal-surface steps already
+   used across app-shell.css/community.css; --rail-info/-success/-warning/-error
+   mirror the canonical .tone-info/.tone-success/.tone-warning/.tone-error
+   banner/badge/chip severity names (app-shell.css L592, community.css
+   .cm-banner.tone-*) rather than inventing a new severity vocabulary.
+   ============================================================ */
+:root {
+  /* --accent already exists as a primitive-facing alias (var(--acid)) above;
+     restated here under the semantic tier for discoverability alongside its
+     siblings. Same value, same token — not a second definition. */
+  --surface-1: var(--panel-1);
+  --surface-2: var(--panel-2);
+
+  /* Rail/status severity aliases — map onto the same color choices the
+     existing .cm-banner.tone-* rules in community.css already use, so a
+     future rail/indicator component can consume one semantic name instead
+     of picking the right primitive per severity by hand. */
+  --rail-info:    var(--sky);
+  --rail-success: var(--green-2);
+  --rail-warning: var(--amber);
+  --rail-error:   var(--warn);
+}
+
 /* Elevation tokens consumed by overlays (Tooltip, Popover, Dropdown, Dialog). */
 :root {
   --shadow-1: 0 1px 2px color-mix(in oklab, var(--fg) 8%, transparent);

package/dist/247420.css

@@ -537,6 +537,49 @@
   }
 }
 
+/* ============================================================
+   Semantic alias tier — primitive -> semantic -> component
+   ------------------------------------------------------------
+   Three layers, in order:
+     1. PRIMITIVE  (above)  raw palette values: --acid, --green, --sky, --warn,
+        --panel-1/2/3, --paper/--ink, etc. These are the only tokens that ever
+        carry a literal color/length. A re-brand edits primitives.
+     2. SEMANTIC   (here)   named-by-INTENT aliases that resolve to a primitive
+        (e.g. --accent: var(--panel-accent)). A component or a future re-brand
+        can retune ONE semantic variable (say, --rail-danger) without hunting
+        through every primitive it happens to reuse elsewhere.
+     3. COMPONENT  (app-shell.css, community.css, etc.) component sheets keep
+        consuming primitives directly today (--accent, --panel-*, --green,
+        --warn, ...) exactly as before — this tier does not repoint any
+        existing component rule. It exists so a FUTURE swap has a semantic
+        layer ready to migrate onto, one component sheet at a time, without
+        a flag-day rewrite. Purely additive: no primitive token's name or
+        value changes here, and no component references these new names yet.
+
+   Naming matches vocabulary already established elsewhere in this system:
+   --surface-1/2 mirror the --panel-1/--panel-2 tonal-surface steps already
+   used across app-shell.css/community.css; --rail-info/-success/-warning/-error
+   mirror the canonical .tone-info/.tone-success/.tone-warning/.tone-error
+   banner/badge/chip severity names (app-shell.css L592, community.css
+   .cm-banner.tone-*) rather than inventing a new severity vocabulary.
+   ============================================================ */
+.ds-247420 {
+  /* --accent already exists as a primitive-facing alias (var(--acid)) above;
+     restated here under the semantic tier for discoverability alongside its
+     siblings. Same value, same token — not a second definition. */
+  --surface-1: var(--panel-1);
+  --surface-2: var(--panel-2);
+
+  /* Rail/status severity aliases — map onto the same color choices the
+     existing .cm-banner.tone-* rules in community.css already use, so a
+     future rail/indicator component can consume one semantic name instead
+     of picking the right primitive per severity by hand. */
+  --rail-info:    var(--sky);
+  --rail-success: var(--green-2);
+  --rail-warning: var(--amber);
+  --rail-error:   var(--warn);
+}
+
 /* Elevation tokens consumed by overlays (Tooltip, Popover, Dropdown, Dialog). */
 .ds-247420 {
   --shadow-1: 0 1px 2px color-mix(in oklab, var(--fg) 8%, transparent);
@@ -2686,6 +2729,17 @@
 @media (hover: none), (pointer: coarse) {
   .ds-247420 .ds-modal-input { font-size: 16px; min-height: 44px; }
 }
+/* PromptDialog's optional roots-chip row (destination-path prompts with more
+   than one allowed root) - same chip idiom the cwd editor's roots row uses. */
+.ds-247420 .ds-prompt-roots { display: flex; align-items: center; gap: 6px; flex-wrap: wrap; margin-top: 8px; }
+.ds-247420 .ds-prompt-root-chip {
+  background: var(--bg-2); border: var(--bw-hair) solid var(--rule); color: var(--fg-2);
+  border-radius: var(--r-pill); padding: 3px 10px; font: inherit; font-size: var(--fs-tiny);
+  cursor: pointer;
+}
+.ds-247420 .ds-prompt-root-chip:hover { border-color: var(--accent); color: var(--fg); }
+.ds-247420 .ds-prompt-root-chip:focus-visible { outline: var(--focus-w) solid var(--focus-color); outline-offset: var(--focus-offset); }
+@media (pointer: coarse) { .ds-247420 .ds-prompt-root-chip { min-height: 44px; } }
 /* In-body modal error (role=alert): mutation failures (409/403) surface INSIDE
    the dialog, not behind the fixed overlay. */
 .ds-247420 .ds-modal-error {
@@ -9652,9 +9706,26 @@
    the app-composition wrapper, the server+channel rail pills, the voice view grid,
    and the category-color tokens the consumer avatars use. All scoped under
    .ds-247420. Additive — defines only the ca- prefix, group, rail-empty, vx-view
-   classes plus the cat color tokens. */
-
-.ds-247420.ds-247420 .ca-app {
+   classes plus the cat color tokens.
+
+   Relationship to community.css: this is NOT a fork of community.css's content
+   -- it is a small (~150-line), genuinely distinct app-shell WRAPPER around the
+   canonical, complete community surface. community.css (~1650 lines) owns every
+   .cm-*/.ds-247420 .vx-* component (server rail, channel sidebar, chat header, member list,
+   voice PTT/VAD/webcam, thread panel, forum, page view) and is the canonical, .ds-247420 actively-referenced stylesheet -- it is the one listed in package.json's
+   `exports`/`files`, the one scripts/build.mjs and scripts/lint-tokens.mjs treat
+   as a first-class component sheet on its own, and the one THEME.md/
+   COMPONENT_API.md document as the load-order anchor
+   (colors_and_type.css -> app-shell.css -> community.css -> chat.css ->
+   editor-primitives.css -> community-app.css -> app-surfaces.css). This file
+   loads strictly AFTER community.css (see ui_kits/community-app/index.html) and
+   only adds the .ca-* composition shell + category-color tokens that
+   community.css deliberately has no opinion about -- it never redefines a
+   .cm-*/.vx-* rule community.css already owns. Canonical tokens/rules live in
+   community.css; only overrides/additions specific to mountCommunityApp's own
+   composition live here. */
+
+html.ds-247420 .ca-app {
   display: flex;
   flex-direction: column;
   height: 100vh;