@signal9/era-ui 12.1.2 → 13.0.0

package/dist/apps/llm-shell/llm-swarm.svelte

@@ -1,79 +0,0 @@
-<script lang="ts">
-	/**
-	 * The `swarm` block: a delegated run, inline in the turn that started it.
-	 *
-	 * Its own component rather than a branch of llm-shell's blockView, because it
-	 * needs one thing a snippet cannot hold — a $derived index of artifacts by
-	 * agent. Inline, the lookup was a `{@const}` arrow re-created on every render
-	 * and called once per node by the tree's expandable predicate, again by the
-	 * keyboard walk, and again by the detail body: O(agents x artifacts) per event,
-	 * three times over. Here it is one pass per artifact change.
-	 */
-	import * as AI from '../../ai/index.js';
-	import type { LlmSwarm } from './types.js';
-
-	let {
-		swarm,
-		view = 'tree',
-		now = Date.now(),
-		onOpenAgent,
-		onCancelAgent,
-		renderers
-	}: {
-		swarm: LlmSwarm;
-		/** `tree` keeps the delegation shape; `grid` is the console layout. */
-		view?: 'tree' | 'grid';
-		now?: number;
-		onOpenAgent?: (agent: AI.Swarm.SwarmAgent) => void;
-		onCancelAgent?: (agent: AI.Swarm.SwarmAgent) => void;
-		/** Host renderers for artifact payloads — handed to `Swarm.Root`'s registry. */
-		renderers?: AI.Swarm.SwarmContentRenderers;
-	} = $props();
-
-	// A plain record, not a Map: it is rebuilt whole by the derived, so it never
-	// needs reactivity of its own (and SvelteMap here would only add proxy cost).
-	// NONE is shared so a miss doesn't allocate a fresh array per lookup per render.
-	const NONE: AI.Swarm.SwarmArtifact[] = [];
-	const byAgent = $derived.by(() => {
-		const index: Record<string, AI.Swarm.SwarmArtifact[]> = {};
-		for (const artifact of swarm.artifacts ?? []) {
-			if (artifact.agentId == null) continue;
-			(index[artifact.agentId] ??= []).push(artifact);
-		}
-		return index;
-	});
-	const artifactsFor = (agent: AI.Swarm.SwarmAgent) => byAgent[agent.id] ?? NONE;
-</script>
-
-<AI.Swarm.Root {now} onOpen={onOpenAgent} onCancel={onCancelAgent} {renderers}>
-	<AI.Swarm.Header title={swarm.plan?.title} status={swarm.plan?.status}>
-		<AI.Swarm.Counts agents={swarm.agents} />
-	</AI.Swarm.Header>
-
-	{#if view === 'grid'}
-		<AI.Swarm.Grid agents={swarm.agents} />
-		<!-- The console view was dropping artifacts on the floor — cards show the
-		     agents, and nothing showed what they PRODUCED. The tree hangs them off
-		     each agent's detail chip; the grid gets them as one labelled section. -->
-		<AI.Swarm.Artifacts artifacts={swarm.artifacts ?? []} />
-	{:else}
-		<!-- The chip names what it opens, so the section heading inside would say it
-		     twice — the detail is just the cards. -->
-		<AI.Swarm.Tree
-			agents={swarm.agents}
-			detailLabel={(agent) => {
-				const n = artifactsFor(agent).length;
-				return n === 0 ? undefined : `${n} artifact${n === 1 ? '' : 's'}`;
-			}}
-		>
-			{#snippet detail(agent)}
-				<AI.Swarm.Artifacts artifacts={artifactsFor(agent)} label={undefined} />
-			{/snippet}
-		</AI.Swarm.Tree>
-	{/if}
-
-	<!-- Fan-in gates last: they are what the branches above are waiting on. -->
-	<AI.Swarm.Barriers barriers={swarm.barriers ?? []} agents={swarm.agents} />
-
-	<AI.Swarm.Footer connection={swarm.connection} seq={swarm.seq} error={swarm.error} />
-</AI.Swarm.Root>

package/dist/apps/llm-shell/llm-swarm.svelte.d.ts

@@ -1,25 +0,0 @@
-/**
-     * The `swarm` block: a delegated run, inline in the turn that started it.
-     *
-     * Its own component rather than a branch of llm-shell's blockView, because it
-     * needs one thing a snippet cannot hold — a $derived index of artifacts by
-     * agent. Inline, the lookup was a `{@const}` arrow re-created on every render
-     * and called once per node by the tree's expandable predicate, again by the
-     * keyboard walk, and again by the detail body: O(agents x artifacts) per event,
-     * three times over. Here it is one pass per artifact change.
-     */
-import * as AI from '../../ai/index.js';
-import type { LlmSwarm } from './types.js';
-type $$ComponentProps = {
-    swarm: LlmSwarm;
-    /** `tree` keeps the delegation shape; `grid` is the console layout. */
-    view?: 'tree' | 'grid';
-    now?: number;
-    onOpenAgent?: (agent: AI.Swarm.SwarmAgent) => void;
-    onCancelAgent?: (agent: AI.Swarm.SwarmAgent) => void;
-    /** Host renderers for artifact payloads — handed to `Swarm.Root`'s registry. */
-    renderers?: AI.Swarm.SwarmContentRenderers;
-};
-declare const LlmSwarm: import("svelte").Component<$$ComponentProps, {}, "">;
-type LlmSwarm = ReturnType<typeof LlmSwarm>;
-export default LlmSwarm;

package/dist/apps/llm-shell/types.d.ts

@@ -1,103 +0,0 @@
-import type { Component } from 'svelte';
-import type { IconProps } from '@lucide/svelte';
-import type { ChatStatus, ConversationStatus, RunState, ToolState, UsageBreakdown } from '../../ai/index.js';
-import type { ApprovalController } from '../../ai/confirmation/index.js';
-import type { RuntimeFeedItemData } from '../../ai/runtime-feed/index.js';
-import type { SwarmAgent, SwarmArtifact, SwarmBarrier, SwarmConnection, SwarmPlan } from '../../ai/swarm/index.js';
-/** Per-turn cost footer under a finished answer. */
-export type LlmUsage = {
-    tokensIn: number;
-    tokensOut: number;
-    model: string;
-    cost: number;
-    breakdown?: UsageBreakdown;
-};
-/** One tool in a compact chip row — the projectMessages "tool burst" shape. */
-export type LlmToolChip = {
-    id: string;
-    name: string;
-    state: ToolState;
-    icon?: Component<IconProps>;
-    input?: unknown;
-    output?: unknown;
-};
-/**
- * Where a swarm block reads its state.
- *
- * Deliberately structural rather than a class: a `SwarmController` satisfies it
- * as-is (so a live, streaming swarm is `{ kind: 'swarm', swarm: controller }`
- * and stays reactive), and a host with static state passes a plain object with
- * the same fields. Neither has to know about the other.
- */
-export type LlmSwarm = {
-    agents: SwarmAgent[];
-    plan?: SwarmPlan | null;
-    barriers?: SwarmBarrier[];
-    artifacts?: SwarmArtifact[];
-    connection?: SwarmConnection;
-    seq?: number;
-    /** Last transport error. A `SwarmController` exposes this under the same name. */
-    error?: string | null;
-};
-/**
- * Everything an assistant turn can contain.
- *
- * The union is the app's contract: it covers every presentation the AI suite
- * has, so a host maps its own stream into these and never renders AI parts by
- * hand. `tool-row` is the compact chips view (one shared expansion area);
- * `tool` is the full expanded step with input, trace and output.
- */
-export type LlmBlock = {
-    kind: 'reasoning';
-    text: string;
-    duration: number;
-    streaming: boolean;
-} | {
-    kind: 'tool';
-    name: string;
-    input: unknown;
-    output?: unknown;
-    state: ToolState;
-    feed?: RuntimeFeedItemData[];
-} | {
-    kind: 'tool-row';
-    tools: LlmToolChip[];
-} | {
-    kind: 'exec';
-    command: string;
-    stdout?: string;
-    stderr?: string;
-    exitCode?: number;
-} | {
-    kind: 'swarm';
-    swarm: LlmSwarm;
-    /** `tree` (default) keeps the delegation shape; `grid` is the console view. */
-    view?: 'tree' | 'grid';
-} | {
-    kind: 'approval';
-    toolName: string;
-    controller: ApprovalController;
-} | {
-    kind: 'error';
-    error: unknown;
-} | {
-    kind: 'answer';
-    text: string;
-    streaming: boolean;
-    usage?: LlmUsage;
-};
-export type LlmMessage = {
-    id: number | string;
-    role: 'user' | 'assistant';
-    text?: string;
-    blocks?: LlmBlock[];
-};
-export type LlmConversation = {
-    id: string;
-    title: string;
-    updatedAt: number;
-    starred?: boolean;
-    status?: ConversationStatus;
-    messages: LlmMessage[];
-};
-export type { ChatStatus, RunState };

package/dist/apps/llm-shell/types.js

@@ -1 +0,0 @@
-export {};

package/dist/apps/notes/editor/bubble-menu.svelte.d.ts

@@ -1,11 +0,0 @@
-/**
- * The selection ("bubble") toolbar.
- *
- * A plain ProseMirror plugin view rather than `@tiptap/extension-bubble-menu`:
- * the official extension brings its own positioning engine and its own DOM, and
- * both would have to be re-skinned anyway. This mounts an era `Bar` of `Button`s
- * with `mount()` and drives it from `update()` — the same approach the slash
- * menu takes, so both overlays share one placement helper and one set of tokens.
- */
-import { Extension } from '@tiptap/core';
-export declare const BubbleMenu: Extension<any, any>;

package/dist/apps/notes/editor/bubble-menu.svelte.js

@@ -1,165 +0,0 @@
-/**
- * The selection ("bubble") toolbar.
- *
- * A plain ProseMirror plugin view rather than `@tiptap/extension-bubble-menu`:
- * the official extension brings its own positioning engine and its own DOM, and
- * both would have to be re-skinned anyway. This mounts an era `Bar` of `Button`s
- * with `mount()` and drives it from `update()` — the same approach the slash
- * menu takes, so both overlays share one placement helper and one set of tokens.
- */
-import { Extension } from '@tiptap/core';
-import { Plugin, PluginKey } from '@tiptap/pm/state';
-import { flushSync, mount, unmount } from 'svelte';
-import Bold from '@lucide/svelte/icons/bold';
-import Italic from '@lucide/svelte/icons/italic';
-import Strikethrough from '@lucide/svelte/icons/strikethrough';
-import Code from '@lucide/svelte/icons/code';
-import Highlighter from '@lucide/svelte/icons/highlighter';
-import LinkIcon from '@lucide/svelte/icons/link';
-import BubbleToolbar from './bubble-toolbar.svelte';
-import { createOverlayHost, placeOverSelection } from './floating.js';
-import { toggleLink } from './link.js';
-const buttons = [
-    {
-        mark: 'bold',
-        label: 'Bold',
-        icon: Bold,
-        command: (ed) => ed.chain().focus().toggleBold().run()
-    },
-    {
-        mark: 'italic',
-        label: 'Italic',
-        icon: Italic,
-        command: (ed) => ed.chain().focus().toggleItalic().run()
-    },
-    {
-        mark: 'strike',
-        label: 'Strikethrough',
-        icon: Strikethrough,
-        command: (ed) => ed.chain().focus().toggleStrike().run()
-    },
-    {
-        mark: 'code',
-        label: 'Code',
-        icon: Code,
-        command: (ed) => ed.chain().focus().toggleCode().run()
-    },
-    {
-        mark: 'highlight',
-        label: 'Highlight',
-        icon: Highlighter,
-        command: (ed) => ed.chain().focus().toggleHighlight().run()
-    },
-    { mark: 'link', label: 'Link', icon: LinkIcon, command: toggleLink }
-];
-const items = buttons.map(({ mark, label, icon }) => ({ mark, label, icon }));
-class BubbleMenuView {
-    #host;
-    #toolbar;
-    #editor;
-    /**
-     * The DOCUMENT range the toolbar is currently parked over, or null while it is
-     * hidden. This is what the toolbar is anchored to — see update().
-     */
-    #anchor = null;
-    #view = $state({
-        items,
-        active: {},
-        onCommand: (_mark) => { }
-    });
-    constructor(editor) {
-        this.#editor = editor;
-        this.#view.onCommand = (mark) => buttons.find((b) => b.mark === mark)?.command(editor);
-        this.#host = createOverlayHost();
-        this.#host.style.display = 'none';
-        document.body.append(this.#host);
-        this.#toolbar = mount(BubbleToolbar, { target: this.#host, props: this.#view });
-    }
-    update(view) {
-        const { state } = view;
-        const { selection } = state;
-        // Hide for a caret, an unfocused editor, a selection with no text (an image
-        // or table node), and inside a code block where marks do not apply.
-        if (selection.empty ||
-            !view.hasFocus() ||
-            !state.doc.textBetween(selection.from, selection.to).length ||
-            this.#editor.isActive('codeBlock')) {
-            this.#host.style.display = 'none';
-            this.#anchor = null;
-            return;
-        }
-        this.#view.active = Object.fromEntries(buttons.map((b) => [b.mark, this.#editor.isActive(b.mark)]));
-        const wasHidden = this.#host.style.display === 'none';
-        this.#host.style.display = 'block';
-        /*
-         * The toolbar is anchored to the SELECTION RANGE, not to its pixel box.
-         *
-         * Those are not the same thing, and the difference is the whole bug:
-         * applying a mark re-renders the selected text — code sets it monospace, a
-         * link adds an underline — so its rect moves while the selection itself
-         * does not change by a single character. Re-centring on the new rect slides
-         * the toolbar out from under the pointer that just clicked it, and the next
-         * click lands on nothing. The user has to chase the menu to keep using it.
-         *
-         * So: reposition only when the range actually changes (or when the toolbar
-         * is appearing fresh). While `from`/`to` hold steady the toolbar is pinned,
-         * and a whole run of formatting happens under a motionless pointer.
-         *
-         * The trade is deliberate: if a format reflows the text far enough, the
-         * toolbar can end up slightly off its selection until the selection next
-         * changes. Being a few pixels stale beats moving while it is being used —
-         * a toolbar is a target first and an indicator second.
-         */
-        const { from, to } = selection;
-        const movedRange = !this.#anchor || this.#anchor.from !== from || this.#anchor.to !== to;
-        if (wasHidden || movedRange) {
-            // flushSync applies the `active` change above BEFORE measuring — reading
-            // a Svelte component's box before its pending render lands gives the
-            // previous frame's, the same trap the slash menu documents. Only needed
-            // on the frames that actually measure.
-            flushSync();
-            placeOverSelection(this.#host, selectionRect(view));
-            this.#anchor = { from, to };
-        }
-    }
-    destroy() {
-        unmount(this.#toolbar);
-        this.#host.remove();
-    }
-}
-/**
- * The selection's bounding box in viewport coordinates.
- *
- * Prefers the live DOM selection, whose rect already unions every line of a
- * multi-line selection. ProseMirror's coordsAtPos only describes ONE position,
- * so reconstructing a tall selection's box from its two endpoints is what put
- * the toolbar 305px off centre. The endpoint union is kept as a fallback for the
- * case where the DOM selection is unavailable or collapsed to a zero rect (it
- * still beats nothing, and it is exactly right on a single line).
- */
-function selectionRect(view) {
-    const dom = window.getSelection();
-    if (dom && dom.rangeCount > 0) {
-        const rect = dom.getRangeAt(0).getBoundingClientRect();
-        if (rect.width > 0 || rect.height > 0)
-            return rect;
-    }
-    const { from, to } = view.state.selection;
-    const a = view.coordsAtPos(from);
-    const b = view.coordsAtPos(to);
-    const left = Math.min(a.left, b.left);
-    const top = Math.min(a.top, b.top);
-    return new DOMRect(left, top, Math.max(a.right, b.right) - left, Math.max(a.bottom, b.bottom) - top);
-}
-export const BubbleMenu = Extension.create({
-    name: 'notesBubbleMenu',
-    addProseMirrorPlugins() {
-        const editor = this.editor;
-        return [
-            new Plugin({
-                key: new PluginKey('notesBubbleMenu'),
-                view: () => new BubbleMenuView(editor)
-            })
-        ];
-    }
-});

package/dist/apps/notes/editor/bubble-toolbar.svelte

@@ -1,55 +0,0 @@
-<script lang="ts">
-	/**
-	 * The selection toolbar — an era `Bar` of latched icon `Button`s.
-	 *
-	 * `active` is Button's latched state (it emits `data-state="on"`), so a mark
-	 * that is on reads as a held-down key on every surface, including bevel where
-	 * the whole affordance is depth rather than tone.
-	 */
-	import type { Component } from 'svelte';
-	import type { IconProps } from '@lucide/svelte';
-	import { Bar } from '../../../ui/bar/index.js';
-	import { Button } from '../../../ui/button/index.js';
-
-	interface Props {
-		items: Array<{ mark: string; label: string; icon: Component<IconProps> }>;
-		/** Which marks are active at the current selection. */
-		active: Record<string, boolean>;
-		onCommand: (mark: string) => void;
-	}
-
-	let { items, active, onCommand }: Props = $props();
-</script>
-
-<!-- md with xxs buttons, matching the app's other bars. It was sm + size="icon"
-     — a 22px bar of 14px buttons around 10px glyphs, the smallest combination in
-     the ladder, which is why the formatting controls read as unhittable.
-
-     The border is a deliberate exception to "shadow, not border" (design rule 7):
-     this panel floats over the DOCUMENT, not over chrome, so on a light theme its
-     elevated fill sits on a page of nearly the same value and the shadow alone
-     leaves no discernible edge. border-divider-faded is the token'd hairline, so
-     it still tracks the surface rather than being a drawn-on line. -->
-<Bar
-	size="control"
-	content="pill"
-	class="w-max border border-divider-faded bg-elevated shadow-lg glass-blur"
->
-	{#each items as item (item.mark)}
-		{@const Icon = item.icon}
-		<Button
-			icon
-			size="pill"
-			active={active[item.mark] ?? false}
-			aria-label={item.label}
-			title={item.label}
-			onmousedown={(e: MouseEvent) => {
-				// Taking focus would collapse the very selection the command formats.
-				e.preventDefault();
-				onCommand(item.mark);
-			}}
-		>
-			<Icon />
-		</Button>
-	{/each}
-</Bar>

package/dist/apps/notes/editor/bubble-toolbar.svelte.d.ts

@@ -1,22 +0,0 @@
-/**
-     * The selection toolbar — an era `Bar` of latched icon `Button`s.
-     *
-     * `active` is Button's latched state (it emits `data-state="on"`), so a mark
-     * that is on reads as a held-down key on every surface, including bevel where
-     * the whole affordance is depth rather than tone.
-     */
-import type { Component } from 'svelte';
-import type { IconProps } from '@lucide/svelte';
-interface Props {
-    items: Array<{
-        mark: string;
-        label: string;
-        icon: Component<IconProps>;
-    }>;
-    /** Which marks are active at the current selection. */
-    active: Record<string, boolean>;
-    onCommand: (mark: string) => void;
-}
-declare const BubbleToolbar: Component<Props, {}, "">;
-type BubbleToolbar = ReturnType<typeof BubbleToolbar>;
-export default BubbleToolbar;

package/dist/apps/notes/editor/extensions.d.ts

@@ -1,18 +0,0 @@
-/**
- * The Notes editor's extension set.
- *
- * Ported from the term/web notes app with two deliberate changes:
- *
- * - The slash menu and bubble toolbar are era components (see the sibling
- *   `.svelte.ts` files) instead of hand-built DOM, so the editor chrome tracks
- *   the density / surface / corners / motion / font axes like the rest of the
- *   library.
- * - `@tiptap/extension-mathematics` is NOT included. It needs KaTeX's stylesheet
- *   and font files to render anything but raw markup, and that is a large,
- *   single-feature dependency to force on every consumer of this subpath. Add it
- *   in your own extension list (and import `katex/dist/katex.min.css`) if you
- *   want it — `noteExtensions` is a plain array, so spreading and extending it
- *   is the supported path.
- */
-import { type Extensions } from '@tiptap/core';
-export declare const noteExtensions: Extensions;

package/dist/apps/notes/editor/extensions.js

@@ -1,88 +0,0 @@
-/**
- * The Notes editor's extension set.
- *
- * Ported from the term/web notes app with two deliberate changes:
- *
- * - The slash menu and bubble toolbar are era components (see the sibling
- *   `.svelte.ts` files) instead of hand-built DOM, so the editor chrome tracks
- *   the density / surface / corners / motion / font axes like the rest of the
- *   library.
- * - `@tiptap/extension-mathematics` is NOT included. It needs KaTeX's stylesheet
- *   and font files to render anything but raw markup, and that is a large,
- *   single-feature dependency to force on every consumer of this subpath. Add it
- *   in your own extension list (and import `katex/dist/katex.min.css`) if you
- *   want it — `noteExtensions` is a plain array, so spreading and extending it
- *   is the supported path.
- */
-import { Extension } from '@tiptap/core';
-import StarterKit from '@tiptap/starter-kit';
-import { TaskList } from '@tiptap/extension-task-list';
-import { TaskItem } from '@tiptap/extension-task-item';
-import CodeBlockLowlight from '@tiptap/extension-code-block-lowlight';
-import Placeholder from '@tiptap/extension-placeholder';
-import Typography from '@tiptap/extension-typography';
-import { Table, TableRow, TableCell, TableHeader } from '@tiptap/extension-table';
-import { Highlight } from '@tiptap/extension-highlight';
-import { Details, DetailsSummary, DetailsContent } from '@tiptap/extension-details';
-import Image from '@tiptap/extension-image';
-import { UniqueID } from '@tiptap/extension-unique-id';
-import { Markdown } from 'tiptap-markdown';
-import { common, createLowlight } from 'lowlight';
-import { ListCleanupRule } from './list-cleanup-rule.js';
-import { SlashCommand } from './slash-command.svelte.js';
-import { BubbleMenu } from './bubble-menu.svelte.js';
-import { toggleLink } from './link.js';
-const LinkShortcut = Extension.create({
-    name: 'linkShortcut',
-    addKeyboardShortcuts() {
-        return {
-            'Mod-k': ({ editor }) => {
-                toggleLink(editor);
-                return true;
-            }
-        };
-    }
-});
-const lowlight = createLowlight(common);
-export const noteExtensions = [
-    StarterKit.configure({
-        heading: { levels: [1, 2, 3] },
-        // Replaced by the lowlight variant below.
-        codeBlock: false,
-        dropcursor: { color: 'var(--color-8)', width: 2 }
-    }),
-    CodeBlockLowlight.configure({ lowlight }),
-    TaskList.configure({
-        HTMLAttributes: { class: 'task-list' }
-    }),
-    TaskItem.configure({
-        nested: true,
-        HTMLAttributes: { class: 'task-item' },
-        a11y: {
-            checkboxLabel: (_node, checked) => (checked ? 'Task completed' : 'Task not completed')
-        }
-    }),
-    // Tables
-    Table.configure({ resizable: false, HTMLAttributes: { class: 'note-table' } }),
-    TableRow,
-    TableCell,
-    TableHeader,
-    // Inline formatting
-    Highlight.configure({ multicolor: false }),
-    // Block types
-    Details,
-    DetailsSummary,
-    DetailsContent,
-    Image.configure({ inline: true, allowBase64: true }),
-    // Utility
-    Placeholder.configure({ placeholder: 'Type / for commands…' }),
-    Typography,
-    // Stable ids on headings are what `tree.ts` addresses sections by, so
-    // section retrieval survives edits above the heading.
-    UniqueID.configure({ types: ['heading', 'paragraph', 'listItem', 'taskItem'] }),
-    Markdown.configure({ html: false }),
-    ListCleanupRule,
-    SlashCommand,
-    LinkShortcut,
-    BubbleMenu
-];

package/dist/apps/notes/editor/floating.d.ts

@@ -1,25 +0,0 @@
-/**
- * Placement for the two editor overlays (slash menu, bubble toolbar).
- *
- * They are mounted at the document root rather than inside the editor so a
- * scrolling or `overflow: hidden` editor pane can never clip them — which means
- * they are positioned in viewport coordinates and have to keep themselves on
- * screen. ProseMirror hands out viewport rects already, so `position: fixed` is
- * the natural fit and no scroll-offset bookkeeping is needed.
- */
-/** Create the fixed, root-level host element an overlay component mounts into. */
-export declare function createOverlayHost(): HTMLDivElement;
-/** Anchor below `rect`, flipping above when the bottom edge would run off. */
-export declare function placeBelow(host: HTMLElement, rect: DOMRect, gap?: number): void;
-/**
- * Centre over a selection's BOUNDING BOX, flipping below when there is no room
- * above.
- *
- * Takes the whole rect on purpose. This used to take the two endpoint coords and
- * centre on `(start.left + end.right) / 2`, which is only correct while the
- * selection sits on one line: across several lines it averages an x from the
- * FIRST line with an x from the LAST, and the result points at neither. Measured
- * on a 7-line selection, the toolbar landed 305px from the selection's centre —
- * one line was 0px, two lines 4px, so it looked fine until a selection got tall.
- */
-export declare function placeOverSelection(host: HTMLElement, rect: DOMRect, gap?: number): void;

package/dist/apps/notes/editor/floating.js

@@ -1,54 +0,0 @@
-/**
- * Placement for the two editor overlays (slash menu, bubble toolbar).
- *
- * They are mounted at the document root rather than inside the editor so a
- * scrolling or `overflow: hidden` editor pane can never clip them — which means
- * they are positioned in viewport coordinates and have to keep themselves on
- * screen. ProseMirror hands out viewport rects already, so `position: fixed` is
- * the natural fit and no scroll-offset bookkeeping is needed.
- */
-const EDGE = 4;
-/** Create the fixed, root-level host element an overlay component mounts into. */
-export function createOverlayHost() {
-    const host = document.createElement('div');
-    // z-50 is the bits-ui portal band — the same layer menus and dialogs use, so
-    // editor chrome stacks consistently with the rest of the library.
-    host.style.cssText = 'position:fixed;top:0;left:0;z-index:50;';
-    return host;
-}
-/** Anchor below `rect`, flipping above when the bottom edge would run off. */
-export function placeBelow(host, rect, gap = EDGE) {
-    const box = host.getBoundingClientRect();
-    const left = clamp(rect.left, EDGE, window.innerWidth - box.width - EDGE);
-    let top = rect.bottom + gap;
-    if (top + box.height > window.innerHeight - EDGE) {
-        const above = rect.top - box.height - gap;
-        top = above >= EDGE ? above : window.innerHeight - box.height - EDGE;
-    }
-    host.style.left = `${Math.max(EDGE, left)}px`;
-    host.style.top = `${Math.max(EDGE, top)}px`;
-}
-/**
- * Centre over a selection's BOUNDING BOX, flipping below when there is no room
- * above.
- *
- * Takes the whole rect on purpose. This used to take the two endpoint coords and
- * centre on `(start.left + end.right) / 2`, which is only correct while the
- * selection sits on one line: across several lines it averages an x from the
- * FIRST line with an x from the LAST, and the result points at neither. Measured
- * on a 7-line selection, the toolbar landed 305px from the selection's centre —
- * one line was 0px, two lines 4px, so it looked fine until a selection got tall.
- */
-export function placeOverSelection(host, rect, gap = 6) {
-    const box = host.getBoundingClientRect();
-    const centerX = rect.left + rect.width / 2;
-    const left = clamp(centerX - box.width / 2, EDGE, window.innerWidth - box.width - EDGE);
-    let top = rect.top - box.height - gap;
-    if (top < EDGE)
-        top = rect.bottom + gap;
-    host.style.left = `${Math.max(EDGE, left)}px`;
-    host.style.top = `${Math.max(EDGE, top)}px`;
-}
-function clamp(value, min, max) {
-    return Math.min(Math.max(value, min), Math.max(min, max));
-}

package/dist/apps/notes/editor/link.d.ts

@@ -1,9 +0,0 @@
-import type { Editor } from '@tiptap/core';
-/**
- * The one link behaviour, shared by the bubble toolbar and Mod-K.
- *
- * Three cases, in order: an existing link is removed; a selection that is
- * already a bare URL links to itself (the common paste-then-select gesture);
- * anything else asks for a target.
- */
-export declare function toggleLink(editor: Editor): void;