@elytracms/studio 0.0.98 → 0.0.99

package/dist/components/nav-issues-registry.js

@@ -1,8 +1,10 @@
 import { jsx as _jsx } from "react/jsx-runtime";
-import { createContext, useContext, useEffect, useMemo, useSyncExternalStore } from 'react';
-/** The shell-scoped store of contributed findings, keyed by source. */
+import { createContext, useContext, useEffect, useId, useMemo, useSyncExternalStore } from 'react';
+import { translate } from '../lib/i18n/index.js';
+import { isReservedFindingSource } from './notifications/notice-model.js';
+/** The shell-scoped store of contributed findings, keyed by PUBLISHER. */
 export class NavIssuesRegistry {
-    bySource = new Map();
+    byPublisher = new Map();
     listeners = new Set();
     snapshot = [];
     subscribe = (listener) => {
@@ -12,23 +14,48 @@ export class NavIssuesRegistry {
         };
     };
     getSnapshot = () => this.snapshot;
-    /** Publish (or replace) one source's findings; an empty list removes the source. */
-    publish(source, issues) {
-        if (issues.length === 0)
-            this.bySource.delete(source);
-        else
-            this.bySource.set(source, issues);
+    /**
+     * Publish (or replace) ONE publisher's findings under `source`; an empty list removes the
+     * publisher. `publisher` is the registry-assigned identity ({@link useNavIssues} passes its
+     * `useId`), so another publisher naming the same source is untouched.
+     */
+    publish(publisher, source, issues) {
+        if (issues.length === 0) {
+            if (!this.byPublisher.delete(publisher))
+                return;
+        }
+        else {
+            this.byPublisher.set(publisher, { source, issues });
+        }
         this.recompute();
     }
-    retract(source) {
-        if (this.bySource.delete(source))
+    retract(publisher) {
+        if (this.byPublisher.delete(publisher))
             this.recompute();
     }
     recompute() {
         const items = [];
-        for (const [source, issues] of this.bySource) {
+        for (const [publisher, { source, issues }] of this.byPublisher) {
             for (const issue of issues) {
-                items.push({ key: `contributed:${source}:${issue.key}`, message: issue.message, severity: issue.severity ?? 'warning' });
+                items.push({
+                    id: `${publisher}:${issue.key}`,
+                    source,
+                    key: issue.key,
+                    message: issue.message,
+                    severity: issue.severity ?? 'warning',
+                    ...(issue.title !== undefined ? { title: issue.title } : {}),
+                    ...(issue.location !== undefined ? { location: issue.location } : {}),
+                });
+            }
+            if (isReservedFindingSource(source)) {
+                items.push({
+                    id: `${publisher}:reserved-source`,
+                    source: 'engine:registry',
+                    key: `reserved-source:${source}`,
+                    message: translate('shell.notices.reservedSource', { source }),
+                    severity: 'error',
+                    location: { kind: 'config', declaredIn: 'studio' },
+                });
             }
         }
         this.snapshot = items;
@@ -37,7 +64,7 @@ export class NavIssuesRegistry {
     }
 }
 const NavIssuesContext = createContext(null);
-/** Mounted once by the studio project screen, around the shell (rail + content). */
+/** Mounted once by the studio project screen, around the shell (header, rail + content). */
 export function NavIssuesProvider({ children }) {
     const registry = useMemo(() => new NavIssuesRegistry(), []);
     return _jsx(NavIssuesContext.Provider, { value: registry, children: children });
@@ -50,18 +77,20 @@ function useRegistry(caller) {
     return registry;
 }
 /**
- * Publish findings to the rail foot while this component is mounted. `source` names the
- * publisher (`'forms'`, `'analytics:beacon'`); pass the same `issues` array identity
- * between renders (memoize it) or the foot re-renders on every render.
+ * Publish findings to the shell's issues tray while this component is mounted. `source`
+ * names the publisher's kind (`'forms'`, `'analytics:beacon'`) — it groups and orders, it is
+ * not an address: each mounted call is its own publisher. Pass the same `issues` array
+ * identity between renders (memoize it) or the tray re-renders on every render.
  */
 export function useNavIssues(source, issues) {
     const registry = useRegistry('useNavIssues');
+    const publisher = useId();
     useEffect(() => {
-        registry.publish(source, issues);
-    }, [registry, source, issues]);
-    useEffect(() => () => registry.retract(source), [registry, source]);
+        registry.publish(publisher, source, issues);
+    }, [registry, publisher, source, issues]);
+    useEffect(() => () => registry.retract(publisher), [registry, publisher]);
 }
-/** The contributed findings, for the rail foot. */
+/** The contributed findings, for the issues tray. */
 export function useContributedNavIssues() {
     const registry = useRegistry('useContributedNavIssues');
     return useSyncExternalStore(registry.subscribe, registry.getSnapshot, registry.getSnapshot);

package/dist/components/nav-issues-registry.js.map

@@ -1 +1 @@
-{"version":3,"file":"nav-issues-registry.js","sourceRoot":"","sources":["../../src/components/nav-issues-registry.tsx"],"names":[],"mappings":";AAAA,OAAO,EAAE,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,OAAO,EAAE,oBAAoB,EAAE,MAAM,OAAO,CAAA;AAiC3F,uEAAuE;AACvE,MAAM,OAAO,iBAAiB;IACX,QAAQ,GAAG,IAAI,GAAG,EAA+B,CAAA;IACjD,SAAS,GAAG,IAAI,GAAG,EAAY,CAAA;IACxC,QAAQ,GAA4B,EAAE,CAAA;IAE9C,SAAS,GAAG,CAAC,QAAkB,EAAgB,EAAE;QAC/C,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAA;QAC5B,OAAO,GAAG,EAAE;YACV,IAAI,CAAC,SAAS,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAA;QACjC,CAAC,CAAA;IACH,CAAC,CAAA;IAED,WAAW,GAAG,GAA4B,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAA;IAE1D,oFAAoF;IACpF,OAAO,CAAC,MAAc,EAAE,MAA2B;QACjD,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC;YAAE,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,MAAM,CAAC,CAAA;;YAChD,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;QACtC,IAAI,CAAC,SAAS,EAAE,CAAA;IAClB,CAAC;IAED,OAAO,CAAC,MAAc;QACpB,IAAI,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,MAAM,CAAC;YAAE,IAAI,CAAC,SAAS,EAAE,CAAA;IACpD,CAAC;IAEO,SAAS;QACf,MAAM,KAAK,GAAmB,EAAE,CAAA;QAChC,KAAK,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,IAAI,IAAI,CAAC,QAAQ,EAAE,CAAC;YAC7C,KAAK,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;gBAC3B,KAAK,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,eAAe,MAAM,IAAI,KAAK,CAAC,GAAG,EAAE,EAAE,OAAO,EAAE,KAAK,CAAC,OAAO,EAAE,QAAQ,EAAE,KAAK,CAAC,QAAQ,IAAI,SAAS,EAAE,CAAC,CAAA;YAC1H,CAAC;QACH,CAAC;QACD,IAAI,CAAC,QAAQ,GAAG,KAAK,CAAA;QACrB,KAAK,MAAM,QAAQ,IAAI,CAAC,GAAG,IAAI,CAAC,SAAS,CAAC;YAAE,QAAQ,EAAE,CAAA;IACxD,CAAC;CACF;AAED,MAAM,gBAAgB,GAAG,aAAa,CAA2B,IAAI,CAAC,CAAA;AAEtE,oFAAoF;AACpF,MAAM,UAAU,iBAAiB,CAAC,EAAE,QAAQ,EAA2B;IACrE,MAAM,QAAQ,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,IAAI,iBAAiB,EAAE,EAAE,EAAE,CAAC,CAAA;IAC3D,OAAO,KAAC,gBAAgB,CAAC,QAAQ,IAAC,KAAK,EAAE,QAAQ,YAAG,QAAQ,GAA6B,CAAA;AAC3F,CAAC;AAED,SAAS,WAAW,CAAC,MAAc;IACjC,MAAM,QAAQ,GAAG,UAAU,CAAC,gBAAgB,CAAC,CAAA;IAC7C,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd,MAAM,IAAI,KAAK,CAAC,GAAG,MAAM,oFAAoF,CAAC,CAAA;IAChH,CAAC;IACD,OAAO,QAAQ,CAAA;AACjB,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,YAAY,CAAC,MAAc,EAAE,MAA2B;IACtE,MAAM,QAAQ,GAAG,WAAW,CAAC,cAAc,CAAC,CAAA;IAC5C,SAAS,CAAC,GAAG,EAAE;QACb,QAAQ,CAAC,OAAO,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;IAClC,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,CAAC,CAAC,CAAA;IAC9B,SAAS,CAAC,GAAG,EAAE,CAAC,GAAG,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,MAAM,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC,CAAC,CAAA;AACrE,CAAC;AAED,mDAAmD;AACnD,MAAM,UAAU,uBAAuB;IACrC,MAAM,QAAQ,GAAG,WAAW,CAAC,yBAAyB,CAAC,CAAA;IACvD,OAAO,oBAAoB,CAAC,QAAQ,CAAC,SAAS,EAAE,QAAQ,CAAC,WAAW,EAAE,QAAQ,CAAC,WAAW,CAAC,CAAA;AAC7F,CAAC","sourcesContent":["import { createContext, useContext, useEffect, useMemo, useSyncExternalStore } from 'react'\nimport type { ReactNode } from 'react'\nimport type { IssueSeverity } from './issue-severity'\nimport type { NavIssueItem } from './nav-issues'\n\n/**\n * EC-616 — the rail foot's CONTRIBUTION seam (`useNavIssues`, ruling § 6b item 1).\n *\n * The issues foot (`SectionNav`) is on every studio surface, so it is where a finding the\n * developer must not miss belongs — but its sources were a fixed list (config, nav,\n * renderers, reuse, routes, orphans), and a custom view or an addon had no way in. Now any\n * component under the studio shell publishes findings with {@link useNavIssues}; the foot\n * renders them beside its own. While the publishing component is mounted its findings\n * show; on unmount they go. A rail item that must ALWAYS report (not only while its view\n * is open) declares `useIssues` on its view (`nav.view({ useIssues })` /\n * `nav.rail(kind, { useIssues })`) — the rail mounts that hook for it.\n *\n * A finding is plain data: a stable `key` (unique within its source), the localized\n * `message`, and a `severity` (`'error' | 'warning'`, default `'warning'`).\n */\n\n/** One finding a view or addon puts in the rail foot. */\nexport interface NavIssue {\n  /** Stable within its source (re-publishing the same key replaces, never duplicates). */\n  key: string\n  /** The localized message, shown as written. */\n  message: string\n  /** Default `'warning'`. */\n  severity?: IssueSeverity\n}\n\ntype Listener = () => void\n\n/** The shell-scoped store of contributed findings, keyed by source. */\nexport class NavIssuesRegistry {\n  private readonly bySource = new Map<string, readonly NavIssue[]>()\n  private readonly listeners = new Set<Listener>()\n  private snapshot: readonly NavIssueItem[] = []\n\n  subscribe = (listener: Listener): (() => void) => {\n    this.listeners.add(listener)\n    return () => {\n      this.listeners.delete(listener)\n    }\n  }\n\n  getSnapshot = (): readonly NavIssueItem[] => this.snapshot\n\n  /** Publish (or replace) one source's findings; an empty list removes the source. */\n  publish(source: string, issues: readonly NavIssue[]): void {\n    if (issues.length === 0) this.bySource.delete(source)\n    else this.bySource.set(source, issues)\n    this.recompute()\n  }\n\n  retract(source: string): void {\n    if (this.bySource.delete(source)) this.recompute()\n  }\n\n  private recompute(): void {\n    const items: NavIssueItem[] = []\n    for (const [source, issues] of this.bySource) {\n      for (const issue of issues) {\n        items.push({ key: `contributed:${source}:${issue.key}`, message: issue.message, severity: issue.severity ?? 'warning' })\n      }\n    }\n    this.snapshot = items\n    for (const listener of [...this.listeners]) listener()\n  }\n}\n\nconst NavIssuesContext = createContext<NavIssuesRegistry | null>(null)\n\n/** Mounted once by the studio project screen, around the shell (rail + content). */\nexport function NavIssuesProvider({ children }: { children: ReactNode }) {\n  const registry = useMemo(() => new NavIssuesRegistry(), [])\n  return <NavIssuesContext.Provider value={registry}>{children}</NavIssuesContext.Provider>\n}\n\nfunction useRegistry(caller: string): NavIssuesRegistry {\n  const registry = useContext(NavIssuesContext)\n  if (!registry) {\n    throw new Error(`${caller} must be used inside the studio shell (no NavIssuesProvider above this component).`)\n  }\n  return registry\n}\n\n/**\n * Publish findings to the rail foot while this component is mounted. `source` names the\n * publisher (`'forms'`, `'analytics:beacon'`); pass the same `issues` array identity\n * between renders (memoize it) or the foot re-renders on every render.\n */\nexport function useNavIssues(source: string, issues: readonly NavIssue[]): void {\n  const registry = useRegistry('useNavIssues')\n  useEffect(() => {\n    registry.publish(source, issues)\n  }, [registry, source, issues])\n  useEffect(() => () => registry.retract(source), [registry, source])\n}\n\n/** The contributed findings, for the rail foot. */\nexport function useContributedNavIssues(): readonly NavIssueItem[] {\n  const registry = useRegistry('useContributedNavIssues')\n  return useSyncExternalStore(registry.subscribe, registry.getSnapshot, registry.getSnapshot)\n}\n"]}
+{"version":3,"file":"nav-issues-registry.js","sourceRoot":"","sources":["../../src/components/nav-issues-registry.tsx"],"names":[],"mappings":";AAAA,OAAO,EAAE,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,KAAK,EAAE,OAAO,EAAE,oBAAoB,EAAE,MAAM,OAAO,CAAA;AAElG,OAAO,EAAE,SAAS,EAAE,MAAM,aAAa,CAAA;AAEvC,OAAO,EAAE,uBAAuB,EAAE,MAAM,8BAA8B,CAAA;AA8CtE,0EAA0E;AAC1E,MAAM,OAAO,iBAAiB;IACX,WAAW,GAAG,IAAI,GAAG,EAAuB,CAAA;IAC5C,SAAS,GAAG,IAAI,GAAG,EAAY,CAAA;IACxC,QAAQ,GAAuB,EAAE,CAAA;IAEzC,SAAS,GAAG,CAAC,QAAkB,EAAgB,EAAE;QAC/C,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAA;QAC5B,OAAO,GAAG,EAAE;YACV,IAAI,CAAC,SAAS,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAA;QACjC,CAAC,CAAA;IACH,CAAC,CAAA;IAED,WAAW,GAAG,GAAuB,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAA;IAErD;;;;OAIG;IACH,OAAO,CAAC,SAAiB,EAAE,MAAc,EAAE,MAA2B;QACpE,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YACxB,IAAI,CAAC,IAAI,CAAC,WAAW,CAAC,MAAM,CAAC,SAAS,CAAC;gBAAE,OAAM;QACjD,CAAC;aAAM,CAAC;YACN,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,SAAS,EAAE,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC,CAAA;QACrD,CAAC;QACD,IAAI,CAAC,SAAS,EAAE,CAAA;IAClB,CAAC;IAED,OAAO,CAAC,SAAiB;QACvB,IAAI,IAAI,CAAC,WAAW,CAAC,MAAM,CAAC,SAAS,CAAC;YAAE,IAAI,CAAC,SAAS,EAAE,CAAA;IAC1D,CAAC;IAEO,SAAS;QACf,MAAM,KAAK,GAAc,EAAE,CAAA;QAC3B,KAAK,MAAM,CAAC,SAAS,EAAE,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC,IAAI,IAAI,CAAC,WAAW,EAAE,CAAC;YAC/D,KAAK,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;gBAC3B,KAAK,CAAC,IAAI,CAAC;oBACT,EAAE,EAAE,GAAG,SAAS,IAAI,KAAK,CAAC,GAAG,EAAE;oBAC/B,MAAM;oBACN,GAAG,EAAE,KAAK,CAAC,GAAG;oBACd,OAAO,EAAE,KAAK,CAAC,OAAO;oBACtB,QAAQ,EAAE,KAAK,CAAC,QAAQ,IAAI,SAAS;oBACrC,GAAG,CAAC,KAAK,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,KAAK,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;oBAC5D,GAAG,CAAC,KAAK,CAAC,QAAQ,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,KAAK,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;iBACtE,CAAC,CAAA;YACJ,CAAC;YACD,IAAI,uBAAuB,CAAC,MAAM,CAAC,EAAE,CAAC;gBACpC,KAAK,CAAC,IAAI,CAAC;oBACT,EAAE,EAAE,GAAG,SAAS,kBAAkB;oBAClC,MAAM,EAAE,iBAAiB;oBACzB,GAAG,EAAE,mBAAmB,MAAM,EAAE;oBAChC,OAAO,EAAE,SAAS,CAAC,8BAA8B,EAAE,EAAE,MAAM,EAAE,CAAC;oBAC9D,QAAQ,EAAE,OAAO;oBACjB,QAAQ,EAAE,EAAE,IAAI,EAAE,QAAQ,EAAE,UAAU,EAAE,QAAQ,EAAE;iBACnD,CAAC,CAAA;YACJ,CAAC;QACH,CAAC;QACD,IAAI,CAAC,QAAQ,GAAG,KAAK,CAAA;QACrB,KAAK,MAAM,QAAQ,IAAI,CAAC,GAAG,IAAI,CAAC,SAAS,CAAC;YAAE,QAAQ,EAAE,CAAA;IACxD,CAAC;CACF;AAED,MAAM,gBAAgB,GAAG,aAAa,CAA2B,IAAI,CAAC,CAAA;AAEtE,4FAA4F;AAC5F,MAAM,UAAU,iBAAiB,CAAC,EAAE,QAAQ,EAA2B;IACrE,MAAM,QAAQ,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,IAAI,iBAAiB,EAAE,EAAE,EAAE,CAAC,CAAA;IAC3D,OAAO,KAAC,gBAAgB,CAAC,QAAQ,IAAC,KAAK,EAAE,QAAQ,YAAG,QAAQ,GAA6B,CAAA;AAC3F,CAAC;AAED,SAAS,WAAW,CAAC,MAAc;IACjC,MAAM,QAAQ,GAAG,UAAU,CAAC,gBAAgB,CAAC,CAAA;IAC7C,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd,MAAM,IAAI,KAAK,CAAC,GAAG,MAAM,oFAAoF,CAAC,CAAA;IAChH,CAAC;IACD,OAAO,QAAQ,CAAA;AACjB,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,YAAY,CAAC,MAAc,EAAE,MAA2B;IACtE,MAAM,QAAQ,GAAG,WAAW,CAAC,cAAc,CAAC,CAAA;IAC5C,MAAM,SAAS,GAAG,KAAK,EAAE,CAAA;IACzB,SAAS,CAAC,GAAG,EAAE;QACb,QAAQ,CAAC,OAAO,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,CAAC,CAAA;IAC7C,CAAC,EAAE,CAAC,QAAQ,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,CAAC,CAAC,CAAA;IACzC,SAAS,CAAC,GAAG,EAAE,CAAC,GAAG,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,SAAS,CAAC,EAAE,CAAC,QAAQ,EAAE,SAAS,CAAC,CAAC,CAAA;AAC3E,CAAC;AAED,qDAAqD;AACrD,MAAM,UAAU,uBAAuB;IACrC,MAAM,QAAQ,GAAG,WAAW,CAAC,yBAAyB,CAAC,CAAA;IACvD,OAAO,oBAAoB,CAAC,QAAQ,CAAC,SAAS,EAAE,QAAQ,CAAC,WAAW,EAAE,QAAQ,CAAC,WAAW,CAAC,CAAA;AAC7F,CAAC","sourcesContent":["import { createContext, useContext, useEffect, useId, useMemo, useSyncExternalStore } from 'react'\nimport type { ReactNode } from 'react'\nimport { translate } from '../lib/i18n'\nimport type { IssueSeverity } from './issue-severity'\nimport { isReservedFindingSource } from './notifications/notice-model'\nimport type { Finding, NoticeLocation } from './notifications/notice-model'\n\n/**\n * EC-616 — the studio's CONTRIBUTION seam for findings (`useNavIssues`, ruling § 6b item 1);\n * since EC-690 the registry of the ONE notification-and-issue surface: everything it holds\n * is listed in the shell header's issues tray (the badge), beside the engine's own findings.\n *\n * Any component under the studio shell publishes findings with {@link useNavIssues}. While\n * the publishing component is mounted its findings are listed; on unmount they go. A rail\n * item that must ALWAYS report (not only while its view is open) declares `useIssues` on its\n * view (`nav.view({ useIssues })` / `nav.rail(kind, { useIssues })`) — the shell mounts that\n * hook for it.\n *\n * A finding is plain data: a stable `key` (unique within its source), the localized\n * `message`, a `severity` (`'error' | 'warning'`, default `'warning'`), and since EC-690 an\n * optional short `title` and a `location` (where the tray's \"Go to\" leads, or the file it names).\n *\n * EC-690 (critic point 1): every publisher has its OWN identity, assigned by the registry\n * (`useId`), so two mounted publishers that name the same source both stay listed — one can\n * never overwrite or retract the other's findings. The engine's sources (`config`, `routes`,\n * …, and the `engine:` prefix) are reserved: a contributor using one is still listed, and the\n * misuse is reported as a finding of its own.\n */\n\n/** One finding a view or addon publishes. */\nexport interface NavIssue {\n  /** Stable within its source (re-publishing the same key replaces, never duplicates). */\n  key: string\n  /** The localized message, shown as written. */\n  message: string\n  /** Default `'warning'`. */\n  severity?: IssueSeverity\n  /** EC-690: a short localized title the tray leads the row with (e.g. \"Invalid redirect\"). */\n  title?: string\n  /** EC-690: where the finding is — the tray's \"Go to\" (or the file it names). */\n  location?: NoticeLocation\n}\n\ntype Listener = () => void\n\ninterface Publication {\n  source: string\n  issues: readonly NavIssue[]\n}\n\n/** The shell-scoped store of contributed findings, keyed by PUBLISHER. */\nexport class NavIssuesRegistry {\n  private readonly byPublisher = new Map<string, Publication>()\n  private readonly listeners = new Set<Listener>()\n  private snapshot: readonly Finding[] = []\n\n  subscribe = (listener: Listener): (() => void) => {\n    this.listeners.add(listener)\n    return () => {\n      this.listeners.delete(listener)\n    }\n  }\n\n  getSnapshot = (): readonly Finding[] => this.snapshot\n\n  /**\n   * Publish (or replace) ONE publisher's findings under `source`; an empty list removes the\n   * publisher. `publisher` is the registry-assigned identity ({@link useNavIssues} passes its\n   * `useId`), so another publisher naming the same source is untouched.\n   */\n  publish(publisher: string, source: string, issues: readonly NavIssue[]): void {\n    if (issues.length === 0) {\n      if (!this.byPublisher.delete(publisher)) return\n    } else {\n      this.byPublisher.set(publisher, { source, issues })\n    }\n    this.recompute()\n  }\n\n  retract(publisher: string): void {\n    if (this.byPublisher.delete(publisher)) this.recompute()\n  }\n\n  private recompute(): void {\n    const items: Finding[] = []\n    for (const [publisher, { source, issues }] of this.byPublisher) {\n      for (const issue of issues) {\n        items.push({\n          id: `${publisher}:${issue.key}`,\n          source,\n          key: issue.key,\n          message: issue.message,\n          severity: issue.severity ?? 'warning',\n          ...(issue.title !== undefined ? { title: issue.title } : {}),\n          ...(issue.location !== undefined ? { location: issue.location } : {}),\n        })\n      }\n      if (isReservedFindingSource(source)) {\n        items.push({\n          id: `${publisher}:reserved-source`,\n          source: 'engine:registry',\n          key: `reserved-source:${source}`,\n          message: translate('shell.notices.reservedSource', { source }),\n          severity: 'error',\n          location: { kind: 'config', declaredIn: 'studio' },\n        })\n      }\n    }\n    this.snapshot = items\n    for (const listener of [...this.listeners]) listener()\n  }\n}\n\nconst NavIssuesContext = createContext<NavIssuesRegistry | null>(null)\n\n/** Mounted once by the studio project screen, around the shell (header, rail + content). */\nexport function NavIssuesProvider({ children }: { children: ReactNode }) {\n  const registry = useMemo(() => new NavIssuesRegistry(), [])\n  return <NavIssuesContext.Provider value={registry}>{children}</NavIssuesContext.Provider>\n}\n\nfunction useRegistry(caller: string): NavIssuesRegistry {\n  const registry = useContext(NavIssuesContext)\n  if (!registry) {\n    throw new Error(`${caller} must be used inside the studio shell (no NavIssuesProvider above this component).`)\n  }\n  return registry\n}\n\n/**\n * Publish findings to the shell's issues tray while this component is mounted. `source`\n * names the publisher's kind (`'forms'`, `'analytics:beacon'`) — it groups and orders, it is\n * not an address: each mounted call is its own publisher. Pass the same `issues` array\n * identity between renders (memoize it) or the tray re-renders on every render.\n */\nexport function useNavIssues(source: string, issues: readonly NavIssue[]): void {\n  const registry = useRegistry('useNavIssues')\n  const publisher = useId()\n  useEffect(() => {\n    registry.publish(publisher, source, issues)\n  }, [registry, publisher, source, issues])\n  useEffect(() => () => registry.retract(publisher), [registry, publisher])\n}\n\n/** The contributed findings, for the issues tray. */\nexport function useContributedNavIssues(): readonly Finding[] {\n  const registry = useRegistry('useContributedNavIssues')\n  return useSyncExternalStore(registry.subscribe, registry.getSnapshot, registry.getSnapshot)\n}\n"]}

package/dist/components/nav-issues.d.ts

@@ -1,62 +1,55 @@
 import type { CmsValidationIssue, OrphanedCollection } from '@elytracms/core/cms-core';
 import type { CustomizationIssue } from '@elytracms/core/studio-core';
 import type { IssueSeverity } from './issue-severity.js';
+import type { NavIssue } from './nav-issues-registry.js';
 /**
- * What the rail foot needs to render one finding: a stable key, a message, and the
- * finding's severity. The least common shape across its contributing sources —
- * customization issues (`CustomizationIssue`) and URL-map validation
- * (`CmsValidationIssue`, EC-469) — so a new source joins by mapping to this, not by
- * pretending to be a customization issue.
+ * The engine's own project-level findings, mapped to the one shape the issues tray lists
+ * (EC-690; before it, the rail foot's cards). The least common shape across the sources —
+ * customization issues (`CustomizationIssue`) and URL-map validation (`CmsValidationIssue`,
+ * EC-469) — so a new source joins by mapping to this, not by pretending to be a
+ * customization issue.
  *
  * `severity` was added by EC-493: both mappers used to drop it and the widget painted
- * every finding amber, which stopped being a style nit once EC-488 re-derived
- * `shadowedMountSpaces` from `error` to `warning` ON THE REASONING that the two mean
- * different things, and EC-482 shipped one producer (`hierarchyMountConflicts`)
- * emitting both into this very list.
+ * every finding amber. EC-690 added `title` (the short label a row leads with) and
+ * `location` (where "Go to" leads, or the file the row names).
  */
-export interface NavIssueItem {
-    key: string;
-    message: string;
+export type NavIssueItem = Required<Pick<NavIssue, 'key' | 'message'>> & {
     severity: IssueSeverity;
-}
+} & Pick<NavIssue, 'title' | 'location'>;
 /**
- * Customization issues, as rail-foot items — localized (EC-478). The producers
+ * Customization issues, as findings — localized (EC-478). The producers
  * (`studio-core/customization.ts`, `default-modules.tsx`, `builder/reuse.ts`) emit a
  * catalog key + identifier values rather than a sentence, because the EC-236 seam
  * lives in `packages/core` and may not import the studio catalog;
- * {@link customizationIssueMessage} resolves them here, so this list renders wholly in
- * the active locale instead of half of it.
+ * {@link customizationIssueMessage} resolves them here.
  *
- * EC-493: `severity` rides along. It used to be dropped here, which is half of why an
- * error and a warning were indistinguishable at the foot — `CustomizationIssue` has
- * carried the field since EC-236, the mapper simply did not read it.
+ * EC-690: located where the developer fixes them — the project config's own issues
+ * (EC-479, point `project`) in `elytra.config.ts`, every other point (the rail, field
+ * renderers, app views, reuse, the AI endpoint) in the studio config (`defineStudio`).
  */
 export declare function customizationItems(issues: readonly CustomizationIssue[]): NavIssueItem[];
 /**
- * URL-map validation issues (EC-469), as rail-foot items.
+ * URL-map validation issues (EC-469), as findings.
  *
- * Copy follows the issues-pane convention (EC-192): the localized plain-language label,
- * then the detail — both localized since EC-487, which gave `CmsValidationIssue` the
- * same catalog-reference carriage EC-478 gave `CustomizationIssue`.
+ * EC-690: the localized plain-language label (EC-192) is the row's `title`, the detail its
+ * `message` — the two used to be joined into one sentence. A redirect finding is located at
+ * its row in the redirects rail (by record kind), a route finding at `elytra.config.ts`.
  *
- * EC-493: `severity` rides along, the other half of the fix. It matters most here:
- * EC-482's `hierarchyMountConflicts` emits `error` for two mounts on the same path and
- * `warning` for a nested pair FROM ONE FUNCTION, and EC-488 re-derived
- * `shadowedMountSpaces` to `warning` precisely because the fall-through made it
- * conditional. Both land in this list.
+ * EC-493: `severity` rides along — EC-482's `hierarchyMountConflicts` emits `error` and
+ * `warning` from one function, and both land here.
  */
 export declare function routeIssueItems(issues: readonly CmsValidationIssue[]): NavIssueItem[];
 /** The stable key of the one orphaned-collections finding (EC-606). */
 export declare const ORPHANED_COLLECTIONS_ISSUE_KEY = "orphaned-collections";
 /**
  * EC-606 — stored documents whose collection the project does not declare, as ONE
- * rail-foot item (or none).
+ * finding (or none).
  *
  * Session hydration keeps only the declared collections' documents and counts the
  * rest (`HydratedCms.orphans`, via core's `orphanedCollections`). Before EC-606 those
  * rows were dropped with no trace, so renaming a collection id in config made its
  * documents vanish from the studio. One item for the whole list: it is one condition
- * with one remedy, and N cards would crowd out the rail.
+ * with one remedy, and N rows would crowd out the rest.
  *
  * `warning`, not `error`: nothing is lost (the rows are stored, untouched) and nothing
  * the editor does is blocked. The message names only one remedy, declaring the
@@ -66,23 +59,3 @@ export declare const ORPHANED_COLLECTIONS_ISSUE_KEY = "orphaned-collections";
  * that has one: those rows are still on the public delivery snapshot.
  */
 export declare function orphanedCollectionItems(orphans: readonly OrphanedCollection[]): NavIssueItem[];
-/**
- * Visible project-level issues at the rail foot — the seam's "never silent" (EC-236,
- * extended by EC-467's reuse issues, EC-469's URL-map issues, EC-479's config
- * issues and EC-606's orphaned collections).
- *
- * EC-493: an `error` and a `warning` render distinguishably here, in the treatment the
- * document Issues pane already uses. Each finding is its own tinted card (as in the
- * pane) rather than one shared amber box, because a shared box cannot express a mixed
- * list; collapsed, the single glyph follows {@link highestIssueSeverity}. EC-507 moved
- * that treatment to `components/issue-severity.ts`, the one home all three surfaces
- * import from.
- *
- * `data-nav-issue-severity` is on each card (and on the collapsed glyph) as the
- * machine-readable form of the same distinction — what the smoke test pins, and what an
- * agent inspecting the DOM reads without decoding Tailwind classes.
- */
-export declare function NavIssues({ issues, collapsed }: {
-    issues: NavIssueItem[];
-    collapsed: boolean;
-}): import("react").JSX.Element;

package/dist/components/nav-issues.js

@@ -1,60 +1,63 @@
-import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-import { cn } from '../lib/utils.js';
 import { translate } from '../lib/i18n/index.js';
-import { PROJECT_CONFIG_FILE } from '../lib/workspace/index.js';
+import { PROJECT_CONFIG_FILE, PROJECT_CONFIG_POINT } from '../lib/workspace/index.js';
 import { cmsIssueLabel, cmsValidationIssueMessage, customizationIssueMessage, } from '../lib/persona/labels.js';
-import { Row, Stack, Text } from '@elytracms/studio/ui';
-import { highestIssueSeverity, issueSeverityIcon, issueSeverityStyle } from './issue-severity.js';
+import { routeIssueLocation } from './notifications/notice-model.js';
 /**
- * Customization issues, as rail-foot items — localized (EC-478). The producers
+ * Customization issues, as findings — localized (EC-478). The producers
  * (`studio-core/customization.ts`, `default-modules.tsx`, `builder/reuse.ts`) emit a
  * catalog key + identifier values rather than a sentence, because the EC-236 seam
  * lives in `packages/core` and may not import the studio catalog;
- * {@link customizationIssueMessage} resolves them here, so this list renders wholly in
- * the active locale instead of half of it.
+ * {@link customizationIssueMessage} resolves them here.
  *
- * EC-493: `severity` rides along. It used to be dropped here, which is half of why an
- * error and a warning were indistinguishable at the foot — `CustomizationIssue` has
- * carried the field since EC-236, the mapper simply did not read it.
+ * EC-690: located where the developer fixes them — the project config's own issues
+ * (EC-479, point `project`) in `elytra.config.ts`, every other point (the rail, field
+ * renderers, app views, reuse, the AI endpoint) in the studio config (`defineStudio`).
  */
 export function customizationItems(issues) {
     return issues.map((issue, index) => ({
         key: `${issue.point}:${issue.id ?? index}`,
         message: customizationIssueMessage(issue),
         severity: issue.severity,
+        location: {
+            kind: 'config',
+            declaredIn: issue.point === PROJECT_CONFIG_POINT ? 'project' : 'studio',
+            ...(issue.id !== undefined ? { entry: issue.id } : {}),
+        },
     }));
 }
 /**
- * URL-map validation issues (EC-469), as rail-foot items.
+ * URL-map validation issues (EC-469), as findings.
  *
- * Copy follows the issues-pane convention (EC-192): the localized plain-language label,
- * then the detail — both localized since EC-487, which gave `CmsValidationIssue` the
- * same catalog-reference carriage EC-478 gave `CustomizationIssue`.
+ * EC-690: the localized plain-language label (EC-192) is the row's `title`, the detail its
+ * `message` — the two used to be joined into one sentence. A redirect finding is located at
+ * its row in the redirects rail (by record kind), a route finding at `elytra.config.ts`.
  *
- * EC-493: `severity` rides along, the other half of the fix. It matters most here:
- * EC-482's `hierarchyMountConflicts` emits `error` for two mounts on the same path and
- * `warning` for a nested pair FROM ONE FUNCTION, and EC-488 re-derived
- * `shadowedMountSpaces` to `warning` precisely because the fall-through made it
- * conditional. Both land in this list.
+ * EC-493: `severity` rides along — EC-482's `hierarchyMountConflicts` emits `error` and
+ * `warning` from one function, and both land here.
  */
 export function routeIssueItems(issues) {
-    return issues.map((issue, index) => ({
-        key: `route-issue:${issue.code}:${issue.path.join('/') || index}`,
-        message: `${cmsIssueLabel(issue.code, issue.severity)} — ${cmsValidationIssueMessage(issue)}`,
-        severity: issue.severity,
-    }));
+    return issues.map((issue, index) => {
+        const location = routeIssueLocation(issue);
+        return {
+            key: `route-issue:${issue.code}:${issue.path.join('/') || index}`,
+            title: cmsIssueLabel(issue.code, issue.severity),
+            message: cmsValidationIssueMessage(issue),
+            severity: issue.severity,
+            ...(location !== undefined ? { location } : {}),
+        };
+    });
 }
 /** The stable key of the one orphaned-collections finding (EC-606). */
 export const ORPHANED_COLLECTIONS_ISSUE_KEY = 'orphaned-collections';
 /**
  * EC-606 — stored documents whose collection the project does not declare, as ONE
- * rail-foot item (or none).
+ * finding (or none).
  *
  * Session hydration keeps only the declared collections' documents and counts the
  * rest (`HydratedCms.orphans`, via core's `orphanedCollections`). Before EC-606 those
  * rows were dropped with no trace, so renaming a collection id in config made its
  * documents vanish from the studio. One item for the whole list: it is one condition
- * with one remedy, and N cards would crowd out the rail.
+ * with one remedy, and N rows would crowd out the rest.
  *
  * `warning`, not `error`: nothing is lost (the rows are stored, untouched) and nothing
  * the editor does is blocked. The message names only one remedy, declaring the
@@ -76,39 +79,8 @@ export function orphanedCollectionItems(orphans) {
             key: ORPHANED_COLLECTIONS_ISSUE_KEY,
             message: translate('shell.nav.orphanedCollections', { collections, file: PROJECT_CONFIG_FILE }),
             severity: 'warning',
+            location: { kind: 'config', declaredIn: 'project' },
         },
     ];
 }
-/**
- * Visible project-level issues at the rail foot — the seam's "never silent" (EC-236,
- * extended by EC-467's reuse issues, EC-469's URL-map issues, EC-479's config
- * issues and EC-606's orphaned collections).
- *
- * EC-493: an `error` and a `warning` render distinguishably here, in the treatment the
- * document Issues pane already uses. Each finding is its own tinted card (as in the
- * pane) rather than one shared amber box, because a shared box cannot express a mixed
- * list; collapsed, the single glyph follows {@link highestIssueSeverity}. EC-507 moved
- * that treatment to `components/issue-severity.ts`, the one home all three surfaces
- * import from.
- *
- * `data-nav-issue-severity` is on each card (and on the collapsed glyph) as the
- * machine-readable form of the same distinction — what the smoke test pins, and what an
- * agent inspecting the DOM reads without decoding Tailwind classes.
- */
-export function NavIssues({ issues, collapsed }) {
-    if (collapsed) {
-        const severity = highestIssueSeverity(issues);
-        const Icon = issueSeverityIcon(severity);
-        return (_jsx("div", { className: cn('grid h-9 place-items-center', issueSeverityStyle(severity).text), "data-nav-issue-severity": severity, title: issues.map((issue) => issue.message).join('\n'), children: _jsx(Icon, { className: "size-4", "aria-label": translate('shell.nav.issuesCount', { count: issues.length }) }) }));
-    }
-    return (_jsx(Stack, { gap: "1", className: "mb-1", children: issues.map((issue) => (_jsx(NavIssueCard, { issue: issue }, issue.key))) }));
-}
-/** One finding at the rail foot, tinted + glyphed by its severity. */
-function NavIssueCard({ issue }) {
-    const style = issueSeverityStyle(issue.severity);
-    const Icon = issueSeverityIcon(issue.severity);
-    return (_jsxs(Row, { gap: "1", align: "start", 
-        // `gap-1.5` (the pre-EC-493 icon/text spacing) merged over the primitive's `gap-1`.
-        className: cn('gap-1.5 rounded-md border px-2 py-1.5', style.card, style.text), "data-nav-issue-severity": issue.severity, title: issue.message, children: [_jsx(Icon, { className: "mt-0.5 size-3.5 shrink-0", "aria-hidden": true }), _jsx(Text, { size: "xs", className: "min-w-0 leading-snug", children: issue.message })] }));
-}
 //# sourceMappingURL=nav-issues.js.map

package/dist/components/nav-issues.js.map

@@ -1 +1 @@
-{"version":3,"file":"nav-issues.js","sourceRoot":"","sources":["../../src/components/nav-issues.tsx"],"names":[],"mappings":";AAEA,OAAO,EAAE,EAAE,EAAE,MAAM,cAAc,CAAA;AACjC,OAAO,EAAE,SAAS,EAAE,MAAM,aAAa,CAAA;AACvC,OAAO,EAAE,mBAAmB,EAAE,MAAM,kBAAkB,CAAA;AACtD,OAAO,EACL,aAAa,EACb,yBAAyB,EACzB,yBAAyB,GAC1B,MAAM,uBAAuB,CAAA;AAC9B,OAAO,EAAE,GAAG,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAA;AACvD,OAAO,EAAE,oBAAoB,EAAE,iBAAiB,EAAE,kBAAkB,EAAE,MAAM,kBAAkB,CAAA;AAsB9F;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,kBAAkB,CAAC,MAAqC;IACtE,OAAO,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,KAAK,EAAE,EAAE,CAAC,CAAC;QACnC,GAAG,EAAE,GAAG,KAAK,CAAC,KAAK,IAAI,KAAK,CAAC,EAAE,IAAI,KAAK,EAAE;QAC1C,OAAO,EAAE,yBAAyB,CAAC,KAAK,CAAC;QACzC,QAAQ,EAAE,KAAK,CAAC,QAAQ;KACzB,CAAC,CAAC,CAAA;AACL,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,eAAe,CAAC,MAAqC;IACnE,OAAO,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,KAAK,EAAE,EAAE,CAAC,CAAC;QACnC,GAAG,EAAE,eAAe,KAAK,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,IAAI,KAAK,EAAE;QACjE,OAAO,EAAE,GAAG,aAAa,CAAC,KAAK,CAAC,IAAI,EAAE,KAAK,CAAC,QAAQ,CAAC,MAAM,yBAAyB,CAAC,KAAK,CAAC,EAAE;QAC7F,QAAQ,EAAE,KAAK,CAAC,QAAQ;KACzB,CAAC,CAAC,CAAA;AACL,CAAC;AAED,uEAAuE;AACvE,MAAM,CAAC,MAAM,8BAA8B,GAAG,sBAAsB,CAAA;AAEpE;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,uBAAuB,CAAC,OAAsC;IAC5E,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAA;IACnC,MAAM,WAAW,GAAG,OAAO;SACxB,GAAG,CAAC,CAAC,EAAE,UAAU,EAAE,KAAK,EAAE,SAAS,EAAE,EAAE,EAAE,CACxC,SAAS,GAAG,CAAC;QACX,CAAC,CAAC,SAAS,CAAC,6CAA6C,EAAE,EAAE,UAAU,EAAE,KAAK,EAAE,SAAS,EAAE,CAAC;QAC5F,CAAC,CAAC,SAAS,CAAC,oCAAoC,EAAE,EAAE,UAAU,EAAE,KAAK,EAAE,CAAC,CAC3E;SACA,IAAI,CAAC,IAAI,CAAC,CAAA;IACb,OAAO;QACL;YACE,GAAG,EAAE,8BAA8B;YACnC,OAAO,EAAE,SAAS,CAAC,+BAA+B,EAAE,EAAE,WAAW,EAAE,IAAI,EAAE,mBAAmB,EAAE,CAAC;YAC/F,QAAQ,EAAE,SAAS;SACpB;KACF,CAAA;AACH,CAAC;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,SAAS,CAAC,EAAE,MAAM,EAAE,SAAS,EAAkD;IAC7F,IAAI,SAAS,EAAE,CAAC;QACd,MAAM,QAAQ,GAAG,oBAAoB,CAAC,MAAM,CAAC,CAAA;QAC7C,MAAM,IAAI,GAAG,iBAAiB,CAAC,QAAQ,CAAC,CAAA;QACxC,OAAO,CACL,cACE,SAAS,EAAE,EAAE,CAAC,6BAA6B,EAAE,kBAAkB,CAAC,QAAQ,CAAC,CAAC,IAAI,CAAC,6BACtD,QAAQ,EACjC,KAAK,EAAE,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,YAEtD,KAAC,IAAI,IACH,SAAS,EAAC,QAAQ,gBACN,SAAS,CAAC,uBAAuB,EAAE,EAAE,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,GACxE,GACE,CACP,CAAA;IACH,CAAC;IACD,OAAO,CACL,KAAC,KAAK,IAAC,GAAG,EAAC,GAAG,EAAC,SAAS,EAAC,MAAM,YAC5B,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,CACrB,KAAC,YAAY,IAAiB,KAAK,EAAE,KAAK,IAAvB,KAAK,CAAC,GAAG,CAAkB,CAC/C,CAAC,GACI,CACT,CAAA;AACH,CAAC;AAED,sEAAsE;AACtE,SAAS,YAAY,CAAC,EAAE,KAAK,EAA2B;IACtD,MAAM,KAAK,GAAG,kBAAkB,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAA;IAChD,MAAM,IAAI,GAAG,iBAAiB,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAA;IAC9C,OAAO,CACL,MAAC,GAAG,IACF,GAAG,EAAC,GAAG,EACP,KAAK,EAAC,OAAO;QACb,oFAAoF;QACpF,SAAS,EAAE,EAAE,CAAC,uCAAuC,EAAE,KAAK,CAAC,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC,6BACrD,KAAK,CAAC,QAAQ,EACvC,KAAK,EAAE,KAAK,CAAC,OAAO,aAEpB,KAAC,IAAI,IAAC,SAAS,EAAC,0BAA0B,wBAAe,EACzD,KAAC,IAAI,IAAC,IAAI,EAAC,IAAI,EAAC,SAAS,EAAC,sBAAsB,YAC7C,KAAK,CAAC,OAAO,GACT,IACH,CACP,CAAA;AACH,CAAC","sourcesContent":["import type { CmsValidationIssue, OrphanedCollection } from '@elytracms/core/cms-core'\nimport type { CustomizationIssue } from '@elytracms/core/studio-core'\nimport { cn } from '../lib/utils'\nimport { translate } from '../lib/i18n'\nimport { PROJECT_CONFIG_FILE } from '../lib/workspace'\nimport {\n  cmsIssueLabel,\n  cmsValidationIssueMessage,\n  customizationIssueMessage,\n} from '../lib/persona/labels'\nimport { Row, Stack, Text } from '@elytracms/studio/ui'\nimport { highestIssueSeverity, issueSeverityIcon, issueSeverityStyle } from './issue-severity'\nimport type { IssueSeverity } from './issue-severity'\n\n/**\n * What the rail foot needs to render one finding: a stable key, a message, and the\n * finding's severity. The least common shape across its contributing sources —\n * customization issues (`CustomizationIssue`) and URL-map validation\n * (`CmsValidationIssue`, EC-469) — so a new source joins by mapping to this, not by\n * pretending to be a customization issue.\n *\n * `severity` was added by EC-493: both mappers used to drop it and the widget painted\n * every finding amber, which stopped being a style nit once EC-488 re-derived\n * `shadowedMountSpaces` from `error` to `warning` ON THE REASONING that the two mean\n * different things, and EC-482 shipped one producer (`hierarchyMountConflicts`)\n * emitting both into this very list.\n */\nexport interface NavIssueItem {\n  key: string\n  message: string\n  severity: IssueSeverity\n}\n\n/**\n * Customization issues, as rail-foot items — localized (EC-478). The producers\n * (`studio-core/customization.ts`, `default-modules.tsx`, `builder/reuse.ts`) emit a\n * catalog key + identifier values rather than a sentence, because the EC-236 seam\n * lives in `packages/core` and may not import the studio catalog;\n * {@link customizationIssueMessage} resolves them here, so this list renders wholly in\n * the active locale instead of half of it.\n *\n * EC-493: `severity` rides along. It used to be dropped here, which is half of why an\n * error and a warning were indistinguishable at the foot — `CustomizationIssue` has\n * carried the field since EC-236, the mapper simply did not read it.\n */\nexport function customizationItems(issues: readonly CustomizationIssue[]): NavIssueItem[] {\n  return issues.map((issue, index) => ({\n    key: `${issue.point}:${issue.id ?? index}`,\n    message: customizationIssueMessage(issue),\n    severity: issue.severity,\n  }))\n}\n\n/**\n * URL-map validation issues (EC-469), as rail-foot items.\n *\n * Copy follows the issues-pane convention (EC-192): the localized plain-language label,\n * then the detail — both localized since EC-487, which gave `CmsValidationIssue` the\n * same catalog-reference carriage EC-478 gave `CustomizationIssue`.\n *\n * EC-493: `severity` rides along, the other half of the fix. It matters most here:\n * EC-482's `hierarchyMountConflicts` emits `error` for two mounts on the same path and\n * `warning` for a nested pair FROM ONE FUNCTION, and EC-488 re-derived\n * `shadowedMountSpaces` to `warning` precisely because the fall-through made it\n * conditional. Both land in this list.\n */\nexport function routeIssueItems(issues: readonly CmsValidationIssue[]): NavIssueItem[] {\n  return issues.map((issue, index) => ({\n    key: `route-issue:${issue.code}:${issue.path.join('/') || index}`,\n    message: `${cmsIssueLabel(issue.code, issue.severity)} — ${cmsValidationIssueMessage(issue)}`,\n    severity: issue.severity,\n  }))\n}\n\n/** The stable key of the one orphaned-collections finding (EC-606). */\nexport const ORPHANED_COLLECTIONS_ISSUE_KEY = 'orphaned-collections'\n\n/**\n * EC-606 — stored documents whose collection the project does not declare, as ONE\n * rail-foot item (or none).\n *\n * Session hydration keeps only the declared collections' documents and counts the\n * rest (`HydratedCms.orphans`, via core's `orphanedCollections`). Before EC-606 those\n * rows were dropped with no trace, so renaming a collection id in config made its\n * documents vanish from the studio. One item for the whole list: it is one condition\n * with one remedy, and N cards would crowd out the rail.\n *\n * `warning`, not `error`: nothing is lost (the rows are stored, untouched) and nothing\n * the editor does is blocked. The message names only one remedy, declaring the\n * collection again or restoring its old id (B6). `documents.clear` plus a re-seed\n * would also remove the warning, but for a renamed collection on a live site that is\n * data loss, so the message does not suggest it. A published count rides each entry\n * that has one: those rows are still on the public delivery snapshot.\n */\nexport function orphanedCollectionItems(orphans: readonly OrphanedCollection[]): NavIssueItem[] {\n  if (orphans.length === 0) return []\n  const collections = orphans\n    .map(({ collection, count, published }) =>\n      published > 0\n        ? translate('shell.nav.orphanedCollections.itemPublished', { collection, count, published })\n        : translate('shell.nav.orphanedCollections.item', { collection, count }),\n    )\n    .join(', ')\n  return [\n    {\n      key: ORPHANED_COLLECTIONS_ISSUE_KEY,\n      message: translate('shell.nav.orphanedCollections', { collections, file: PROJECT_CONFIG_FILE }),\n      severity: 'warning',\n    },\n  ]\n}\n\n/**\n * Visible project-level issues at the rail foot — the seam's \"never silent\" (EC-236,\n * extended by EC-467's reuse issues, EC-469's URL-map issues, EC-479's config\n * issues and EC-606's orphaned collections).\n *\n * EC-493: an `error` and a `warning` render distinguishably here, in the treatment the\n * document Issues pane already uses. Each finding is its own tinted card (as in the\n * pane) rather than one shared amber box, because a shared box cannot express a mixed\n * list; collapsed, the single glyph follows {@link highestIssueSeverity}. EC-507 moved\n * that treatment to `components/issue-severity.ts`, the one home all three surfaces\n * import from.\n *\n * `data-nav-issue-severity` is on each card (and on the collapsed glyph) as the\n * machine-readable form of the same distinction — what the smoke test pins, and what an\n * agent inspecting the DOM reads without decoding Tailwind classes.\n */\nexport function NavIssues({ issues, collapsed }: { issues: NavIssueItem[]; collapsed: boolean }) {\n  if (collapsed) {\n    const severity = highestIssueSeverity(issues)\n    const Icon = issueSeverityIcon(severity)\n    return (\n      <div\n        className={cn('grid h-9 place-items-center', issueSeverityStyle(severity).text)}\n        data-nav-issue-severity={severity}\n        title={issues.map((issue) => issue.message).join('\\n')}\n      >\n        <Icon\n          className=\"size-4\"\n          aria-label={translate('shell.nav.issuesCount', { count: issues.length })}\n        />\n      </div>\n    )\n  }\n  return (\n    <Stack gap=\"1\" className=\"mb-1\">\n      {issues.map((issue) => (\n        <NavIssueCard key={issue.key} issue={issue} />\n      ))}\n    </Stack>\n  )\n}\n\n/** One finding at the rail foot, tinted + glyphed by its severity. */\nfunction NavIssueCard({ issue }: { issue: NavIssueItem }) {\n  const style = issueSeverityStyle(issue.severity)\n  const Icon = issueSeverityIcon(issue.severity)\n  return (\n    <Row\n      gap=\"1\"\n      align=\"start\"\n      // `gap-1.5` (the pre-EC-493 icon/text spacing) merged over the primitive's `gap-1`.\n      className={cn('gap-1.5 rounded-md border px-2 py-1.5', style.card, style.text)}\n      data-nav-issue-severity={issue.severity}\n      title={issue.message}\n    >\n      <Icon className=\"mt-0.5 size-3.5 shrink-0\" aria-hidden />\n      <Text size=\"xs\" className=\"min-w-0 leading-snug\">\n        {issue.message}\n      </Text>\n    </Row>\n  )\n}\n"]}
+{"version":3,"file":"nav-issues.js","sourceRoot":"","sources":["../../src/components/nav-issues.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAE,SAAS,EAAE,MAAM,aAAa,CAAA;AACvC,OAAO,EAAE,mBAAmB,EAAE,oBAAoB,EAAE,MAAM,kBAAkB,CAAA;AAC5E,OAAO,EACL,aAAa,EACb,yBAAyB,EACzB,yBAAyB,GAC1B,MAAM,uBAAuB,CAAA;AAG9B,OAAO,EAAE,kBAAkB,EAAE,MAAM,8BAA8B,CAAA;AAiBjE;;;;;;;;;;GAUG;AACH,MAAM,UAAU,kBAAkB,CAAC,MAAqC;IACtE,OAAO,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,KAAK,EAAE,EAAE,CAAC,CAAC;QACnC,GAAG,EAAE,GAAG,KAAK,CAAC,KAAK,IAAI,KAAK,CAAC,EAAE,IAAI,KAAK,EAAE;QAC1C,OAAO,EAAE,yBAAyB,CAAC,KAAK,CAAC;QACzC,QAAQ,EAAE,KAAK,CAAC,QAAQ;QACxB,QAAQ,EAAE;YACR,IAAI,EAAE,QAAQ;YACd,UAAU,EAAE,KAAK,CAAC,KAAK,KAAK,oBAAoB,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,QAAQ;YACvE,GAAG,CAAC,KAAK,CAAC,EAAE,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,KAAK,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SACvD;KACF,CAAC,CAAC,CAAA;AACL,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,eAAe,CAAC,MAAqC;IACnE,OAAO,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,KAAK,EAAE,EAAE;QACjC,MAAM,QAAQ,GAAG,kBAAkB,CAAC,KAAK,CAAC,CAAA;QAC1C,OAAO;YACL,GAAG,EAAE,eAAe,KAAK,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,IAAI,KAAK,EAAE;YACjE,KAAK,EAAE,aAAa,CAAC,KAAK,CAAC,IAAI,EAAE,KAAK,CAAC,QAAQ,CAAC;YAChD,OAAO,EAAE,yBAAyB,CAAC,KAAK,CAAC;YACzC,QAAQ,EAAE,KAAK,CAAC,QAAQ;YACxB,GAAG,CAAC,QAAQ,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAChD,CAAA;IACH,CAAC,CAAC,CAAA;AACJ,CAAC;AAED,uEAAuE;AACvE,MAAM,CAAC,MAAM,8BAA8B,GAAG,sBAAsB,CAAA;AAEpE;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,uBAAuB,CAAC,OAAsC;IAC5E,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAA;IACnC,MAAM,WAAW,GAAG,OAAO;SACxB,GAAG,CAAC,CAAC,EAAE,UAAU,EAAE,KAAK,EAAE,SAAS,EAAE,EAAE,EAAE,CACxC,SAAS,GAAG,CAAC;QACX,CAAC,CAAC,SAAS,CAAC,6CAA6C,EAAE,EAAE,UAAU,EAAE,KAAK,EAAE,SAAS,EAAE,CAAC;QAC5F,CAAC,CAAC,SAAS,CAAC,oCAAoC,EAAE,EAAE,UAAU,EAAE,KAAK,EAAE,CAAC,CAC3E;SACA,IAAI,CAAC,IAAI,CAAC,CAAA;IACb,OAAO;QACL;YACE,GAAG,EAAE,8BAA8B;YACnC,OAAO,EAAE,SAAS,CAAC,+BAA+B,EAAE,EAAE,WAAW,EAAE,IAAI,EAAE,mBAAmB,EAAE,CAAC;YAC/F,QAAQ,EAAE,SAAS;YACnB,QAAQ,EAAE,EAAE,IAAI,EAAE,QAAQ,EAAE,UAAU,EAAE,SAAS,EAAE;SACpD;KACF,CAAA;AACH,CAAC","sourcesContent":["import type { CmsValidationIssue, OrphanedCollection } from '@elytracms/core/cms-core'\nimport type { CustomizationIssue } from '@elytracms/core/studio-core'\nimport { translate } from '../lib/i18n'\nimport { PROJECT_CONFIG_FILE, PROJECT_CONFIG_POINT } from '../lib/workspace'\nimport {\n  cmsIssueLabel,\n  cmsValidationIssueMessage,\n  customizationIssueMessage,\n} from '../lib/persona/labels'\nimport type { IssueSeverity } from './issue-severity'\nimport type { NavIssue } from './nav-issues-registry'\nimport { routeIssueLocation } from './notifications/notice-model'\n\n/**\n * The engine's own project-level findings, mapped to the one shape the issues tray lists\n * (EC-690; before it, the rail foot's cards). The least common shape across the sources —\n * customization issues (`CustomizationIssue`) and URL-map validation (`CmsValidationIssue`,\n * EC-469) — so a new source joins by mapping to this, not by pretending to be a\n * customization issue.\n *\n * `severity` was added by EC-493: both mappers used to drop it and the widget painted\n * every finding amber. EC-690 added `title` (the short label a row leads with) and\n * `location` (where \"Go to\" leads, or the file the row names).\n */\nexport type NavIssueItem = Required<Pick<NavIssue, 'key' | 'message'>> & {\n  severity: IssueSeverity\n} & Pick<NavIssue, 'title' | 'location'>\n\n/**\n * Customization issues, as findings — localized (EC-478). The producers\n * (`studio-core/customization.ts`, `default-modules.tsx`, `builder/reuse.ts`) emit a\n * catalog key + identifier values rather than a sentence, because the EC-236 seam\n * lives in `packages/core` and may not import the studio catalog;\n * {@link customizationIssueMessage} resolves them here.\n *\n * EC-690: located where the developer fixes them — the project config's own issues\n * (EC-479, point `project`) in `elytra.config.ts`, every other point (the rail, field\n * renderers, app views, reuse, the AI endpoint) in the studio config (`defineStudio`).\n */\nexport function customizationItems(issues: readonly CustomizationIssue[]): NavIssueItem[] {\n  return issues.map((issue, index) => ({\n    key: `${issue.point}:${issue.id ?? index}`,\n    message: customizationIssueMessage(issue),\n    severity: issue.severity,\n    location: {\n      kind: 'config',\n      declaredIn: issue.point === PROJECT_CONFIG_POINT ? 'project' : 'studio',\n      ...(issue.id !== undefined ? { entry: issue.id } : {}),\n    },\n  }))\n}\n\n/**\n * URL-map validation issues (EC-469), as findings.\n *\n * EC-690: the localized plain-language label (EC-192) is the row's `title`, the detail its\n * `message` — the two used to be joined into one sentence. A redirect finding is located at\n * its row in the redirects rail (by record kind), a route finding at `elytra.config.ts`.\n *\n * EC-493: `severity` rides along — EC-482's `hierarchyMountConflicts` emits `error` and\n * `warning` from one function, and both land here.\n */\nexport function routeIssueItems(issues: readonly CmsValidationIssue[]): NavIssueItem[] {\n  return issues.map((issue, index) => {\n    const location = routeIssueLocation(issue)\n    return {\n      key: `route-issue:${issue.code}:${issue.path.join('/') || index}`,\n      title: cmsIssueLabel(issue.code, issue.severity),\n      message: cmsValidationIssueMessage(issue),\n      severity: issue.severity,\n      ...(location !== undefined ? { location } : {}),\n    }\n  })\n}\n\n/** The stable key of the one orphaned-collections finding (EC-606). */\nexport const ORPHANED_COLLECTIONS_ISSUE_KEY = 'orphaned-collections'\n\n/**\n * EC-606 — stored documents whose collection the project does not declare, as ONE\n * finding (or none).\n *\n * Session hydration keeps only the declared collections' documents and counts the\n * rest (`HydratedCms.orphans`, via core's `orphanedCollections`). Before EC-606 those\n * rows were dropped with no trace, so renaming a collection id in config made its\n * documents vanish from the studio. One item for the whole list: it is one condition\n * with one remedy, and N rows would crowd out the rest.\n *\n * `warning`, not `error`: nothing is lost (the rows are stored, untouched) and nothing\n * the editor does is blocked. The message names only one remedy, declaring the\n * collection again or restoring its old id (B6). `documents.clear` plus a re-seed\n * would also remove the warning, but for a renamed collection on a live site that is\n * data loss, so the message does not suggest it. A published count rides each entry\n * that has one: those rows are still on the public delivery snapshot.\n */\nexport function orphanedCollectionItems(orphans: readonly OrphanedCollection[]): NavIssueItem[] {\n  if (orphans.length === 0) return []\n  const collections = orphans\n    .map(({ collection, count, published }) =>\n      published > 0\n        ? translate('shell.nav.orphanedCollections.itemPublished', { collection, count, published })\n        : translate('shell.nav.orphanedCollections.item', { collection, count }),\n    )\n    .join(', ')\n  return [\n    {\n      key: ORPHANED_COLLECTIONS_ISSUE_KEY,\n      message: translate('shell.nav.orphanedCollections', { collections, file: PROJECT_CONFIG_FILE }),\n      severity: 'warning',\n      location: { kind: 'config', declaredIn: 'project' },\n    },\n  ]\n}\n"]}

package/dist/components/notifications/notice-center.d.ts

@@ -0,0 +1,61 @@
+import type { ReactNode } from 'react';
+import type { Project } from '@elytracms/core/studio-core';
+import type { ToastItem } from '../../lib/notices/toast-store.js';
+import type { IssueSeverity } from '../issue-severity.js';
+import type { Finding, GoToTarget } from './notice-model.js';
+/**
+ * EC-690 — the studio's ONE notification-and-issue surface, in the shell header: a badge
+ * counting what needs attention by severity (EC-507's treatment), opening a tray that lists
+ * every live notice and every persistent finding with where it is ("Go to" a rail row or a
+ * document; the file or setting for code). Owner ruling (a), 2026-10-28: ONE badge, in the
+ * header — the rail foot shows none (and no finding text at all any more).
+ *
+ * The tray is a Radix popover bounded to the content area (`boundary` = `<main>`), so it can
+ * never cover the section rail at any width. Notices also PEEK in the content area's
+ * bottom-right ({@link NoticePeek}) when they are raised.
+ */
+export declare function NoticeCenter({ project, boundary }: {
+    project: Project;
+    boundary: Element | null;
+}): import("react").JSX.Element;
+/** What the badge counts: every finding, plus every live error notice (an error stays until dismissed). */
+export declare function noticeCounts(findings: readonly Finding[], notices: readonly ToastItem[]): Record<IssueSeverity, number>;
+/** "2 errors, 1 warning" — or "No issues". */
+export declare function noticeSummary(counts: Record<IssueSeverity, number>): string;
+/** The badge's face: one count per severity present, or a muted "all clear". */
+export declare function NoticeBadgeContent({ counts }: {
+    counts: Record<IssueSeverity, number>;
+}): import("react").JSX.Element;
+/**
+ * The tray's body: live notices first (newest first), then the findings in the one order.
+ * Pure over its inputs — `target` resolves a finding's location, so a test renders it without
+ * a router (a finding with no link target renders no `Link`).
+ */
+export declare function NoticeTray({ projectId, findings, notices, target, onNavigate, }: {
+    projectId: string;
+    findings: readonly Finding[];
+    notices: readonly ToastItem[];
+    target: (finding: Finding) => GoToTarget | null;
+    onNavigate?: () => void;
+}): import("react").JSX.Element;
+/**
+ * One persistent finding: EC-507's card + glyph for its severity, a bold title, the message
+ * (clamped, full text on hover; long unbreakable paths wrap — `overflow-wrap:anywhere`), and
+ * its location action. No dismiss and no collapse (owner ruling (e)): it leaves when it stops
+ * being true.
+ */
+export declare function FindingRow({ finding, action }: {
+    finding: Finding;
+    action?: ReactNode;
+}): import("react").JSX.Element;
+/** One transient notice: EC-507's palette for an error, the success tone otherwise; always dismissable. */
+export declare function NoticeRow({ notice }: {
+    notice: ToastItem;
+}): import("react").JSX.Element;
+/**
+ * New notices, peeking for 5 s in the content area's bottom-right — inside `<main>`, so they
+ * never cover the section rail (the old `Toaster` was fixed to the viewport and did, at
+ * narrow widths), and not at its top-right, where the editor's Publish button and save status
+ * sit (critic point 8). An error leaves the peek but stays in the tray until dismissed.
+ */
+export declare function NoticePeek(): import("react").JSX.Element | null;