@formicoidea/labre-core 0.50.0 → 0.51.0

package/dist/_pkgs/affine-model/elements/uml/consts.js

@@ -0,0 +1,107 @@
+/**
+ * The UML element constants an interchange reader needs WITHOUT the element
+ * classes: moved out of `diagram.ts`, `fragment.ts`, `partition.ts` and `region.ts`
+ * unchanged, so the
+ * model's headless entry (`@labre/affine-model/headless`) can export them with
+ * no `@labre/std/gfx` behind it (ADR 0012, P3 as amended 2026-10-14). The
+ * package index re-exports this file, so nothing an importer reads moved.
+ */
+/**
+ * Height of the diagram frame's heading band — the strip across the top of the
+ * frame the `<kind> <name>` tag is written in, in model units.
+ *
+ * Declared HERE, in the model, and re-exported by `@labre/affine-gfx-uml`
+ * rather than the other way round, for the reason `C4_BOARD_TITLE_BAND_HEIGHT`
+ * is: the frame's own hit test needs it (a diagram is clickable by its heading
+ * band as well as by its border), and `affine-model` cannot reach into
+ * `affine-block-surface` where the declaration is resolved. One number, owned
+ * by the layer that both the declaration and the hit test can read.
+ *
+ * It is the frame's TOP MARGIN — the inset the drawing gives up so the heading
+ * has somewhere to be written — so the strip that is painted, the strip that is
+ * picked and the strip that opens the rename are one number rather than three.
+ *
+ * 44 is the height of the cut-corner tag UML 2.5.1 Annex A draws the heading
+ * in: a 20-unit label with the rest as breathing room above and below.
+ * Changing it moves the heading, so it is a visual decision and not a hit-test
+ * one.
+ */
+export const UML_FRAME_BAND_HEIGHT = 44;
+/**
+ * The word written in the heading tag, per kind.
+ *
+ * A table rather than the raw value so that a kind whose stored discriminant
+ * and whose printed tag ever diverge has one place to say so. Today they are
+ * the same four strings, and that is worth stating rather than assuming.
+ *
+ * `Partial` on purpose: a frame read off a document carries whatever string was
+ * written there, including a kind from a later phase this build has never heard
+ * of. Typing the lookup as total would make {@link
+ * UmlDiagramElementModel.heading}'s `?? this.kind` fallback look like dead
+ * defensive code, when it is the whole of the append-only promise.
+ */
+export const UML_DIAGRAM_KIND_TAG = {
+    class: 'class',
+    pkg: 'pkg',
+    obj: 'obj',
+    uc: 'uc',
+    // Both are Annex A's own abbreviations, written exactly as the Annex writes
+    // them — `cmp` for the component diagram, `dep` for the deployment diagram.
+    cmp: 'cmp',
+    dep: 'dep',
+    // Annex A's own abbreviations again — `act` for the activity diagram, `stm`
+    // for the state machine diagram. `stm` is the one tag in the table that is
+    // NOT the kind spelled out: Annex A's frame kind is the two words `state
+    // machine`, and `stm` is the abbreviation it gives in their place.
+    act: 'act',
+    stm: 'stm',
+    // Annex A's abbreviation for the interaction frame, and the third tag in the
+    // table that is not the kind spelled out: the frame kind is `interaction`.
+    sd: 'sd',
+};
+/**
+ * Height of a combined fragment's OPERATOR BAND — the strip across its top the
+ * pentagon tag is drawn in, in model units.
+ *
+ * Owned by the model for the reason {@link UML_FRAME_BAND_HEIGHT} is: the
+ * fragment's own hit test reads it (a fragment is clickable by its tag strip as
+ * well as by its border), and `affine-model` cannot reach into
+ * `affine-block-surface` where the declaration is resolved.
+ *
+ * The diagram frame's own 44, and deliberately: §17.6.4 draws the operator in
+ * the very same cut-corner pentagon Annex A draws a frame heading in — it IS a
+ * frame, nested in another one — and two numbers for one piece of furniture
+ * would drift.
+ */
+export const UML_FRAGMENT_BAND = 44;
+/**
+ * Height of a partition's NAME BAND — the strip its name is written in, in
+ * model units.
+ *
+ * Declared HERE, in the model, and re-exported by `@labre/affine-gfx-uml`, for
+ * the reason {@link UML_FRAME_BAND_HEIGHT} is: the partition's own hit test
+ * reads it (a swimlane is clickable by its header as well as by its border),
+ * and `affine-model` cannot reach into `affine-block-surface` where the
+ * declaration is resolved. One number, owned by the layer that both the
+ * declaration and the hit test can read.
+ *
+ * It is the band's THICKNESS whichever edge the band is on — the top for a
+ * vertical lane, the left for a horizontal one — because §15.6.4 draws one
+ * header strip and turns it with the lane rather than resizing it.
+ *
+ * 36 against the diagram frame's 44: a partition header is a name and not a
+ * `<kind> <name>` heading, and it is written inside a lane that already sits on
+ * a sheet, so it reads as a subdivision rather than as a second sheet.
+ */
+export const UML_PARTITION_BAND = 36;
+/**
+ * Height of a region's NAME BAND — the strip its name is written in, in model
+ * units.
+ *
+ * Owned by the model for the reason {@link UML_PARTITION_BAND} is: the region's
+ * own hit test reads it, and `affine-model` cannot reach into the package where
+ * the declaration is resolved. The same 36 the partition uses, and deliberately
+ * so — the two are the same piece of furniture, a name written in a strip along
+ * the top of a transparent frame, and two numbers would drift.
+ */
+export const UML_REGION_BAND = 36;

package/dist/_pkgs/affine-model/elements/uml/diagram.d.ts

@@ -2,85 +2,7 @@ import type { SerializedXYWH } from '../../../global/gfx/index.js';
 import type { PointTestOptions } from '../../../std/gfx/index.js';
 import type { FrameworkBackgroundProps } from '../framework-background/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
-/**
- * Height of the diagram frame's heading band — the strip across the top of the
- * frame the `<kind> <name>` tag is written in, in model units.
- *
- * Declared HERE, in the model, and re-exported by `@labre/affine-gfx-uml`
- * rather than the other way round, for the reason `C4_BOARD_TITLE_BAND_HEIGHT`
- * is: the frame's own hit test needs it (a diagram is clickable by its heading
- * band as well as by its border), and `affine-model` cannot reach into
- * `affine-block-surface` where the declaration is resolved. One number, owned
- * by the layer that both the declaration and the hit test can read.
- *
- * It is the frame's TOP MARGIN — the inset the drawing gives up so the heading
- * has somewhere to be written — so the strip that is painted, the strip that is
- * picked and the strip that opens the rename are one number rather than three.
- *
- * 44 is the height of the cut-corner tag UML 2.5.1 Annex A draws the heading
- * in: a 20-unit label with the rest as breathing room above and below.
- * Changing it moves the heading, so it is a visual decision and not a hit-test
- * one.
- */
-export declare const UML_FRAME_BAND_HEIGHT = 44;
-/**
- * Which kind of UML diagram this frame draws — the DECLARED fact, as opposed to
- * the name, which is free text and says whatever its author wants it to.
- *
- * ## Where the values come from
- *
- * UML 2.5.1 Annex A gives the normative frame kind names, each with the
- * abbreviation that may be written in its place:
- *
- *  - `activity` / `act`;
- *  - `class` — the one kind Annex A gives NO abbreviation for, so the word
- *    itself is the tag;
- *  - `component` / `cmp`;
- *  - `deployment` / `dep`;
- *  - `interaction` / `sd`;
- *  - `package` / `pkg`;
- *  - `state machine` / `stm`;
- *  - `use case` / `uc`.
- *
- * `obj` is NOT in that list. Annex A has no frame kind for the object diagram —
- * the standard treats it as a class diagram showing instances — but every tool
- * that draws one tags it `obj`, and an architect reading the sheet expects to
- * see it. So `obj` is kept as a TOOL CONVENTION, recorded as such here so that
- * nobody later "fixes" it against the spec without knowing it was a choice.
- *
- * ## Widening this union is additive
- *
- * Phase 1 shipped the first four kinds below; phase 2 APPENDED `cmp` and `dep`,
- * the two structural frames of §11.6.4 and §19.2.4, then `act` and `stm`, the
- * two behaviour frames of §15.2.4 and §14.2.4; phase 3 appends `sd`. Each
- * arrives as a new VALUE of the existing `kind`
- * string field — no new field, no schema change, no migration and no backfill.
- * The same promise `C4NodeKind` and `BpmnNodeKind` already make.
- *
- * Appended, never reordered: the union is read as a set of strings by every
- * consumer, and a document only ever stores one of them, so the ORDER below is a
- * reading aid. Keeping it chronological is what lets a reviewer see at a glance
- * which build a value arrived in.
- *
- * A value a client has never seen reads back as the string it is, and
- * {@link UmlDiagramElementModel.heading} writes it verbatim, so a document
- * created by a newer build still shows its own heading on an older one.
- */
-export type UmlDiagramKind = 'class' | 'pkg' | 'obj' | 'uc' | 'cmp' | 'dep' | 'act' | 'stm' | 'sd';
-/**
- * The word written in the heading tag, per kind.
- *
- * A table rather than the raw value so that a kind whose stored discriminant
- * and whose printed tag ever diverge has one place to say so. Today they are
- * the same four strings, and that is worth stating rather than assuming.
- *
- * `Partial` on purpose: a frame read off a document carries whatever string was
- * written there, including a kind from a later phase this build has never heard
- * of. Typing the lookup as total would make {@link
- * UmlDiagramElementModel.heading}'s `?? this.kind` fallback look like dead
- * defensive code, when it is the whole of the append-only promise.
- */
-export declare const UML_DIAGRAM_KIND_TAG: Partial<Record<UmlDiagramKind, string>>;
+import { type UmlDiagramKind } from './consts.js';
 export type UmlDiagramProps = FrameworkBackgroundProps & {
     /** The diagram name, written in the heading tag — edited inline on dblclick. */
     name?: string;

package/dist/_pkgs/affine-model/elements/uml/diagram.js

@@ -35,59 +35,7 @@ var __runInitializers = (this && this.__runInitializers) || function (thisArg, i
 import { rotatePoint } from '../../../global/gfx/index.js';
 import { field } from '../../../std/gfx/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
-/**
- * Height of the diagram frame's heading band — the strip across the top of the
- * frame the `<kind> <name>` tag is written in, in model units.
- *
- * Declared HERE, in the model, and re-exported by `@labre/affine-gfx-uml`
- * rather than the other way round, for the reason `C4_BOARD_TITLE_BAND_HEIGHT`
- * is: the frame's own hit test needs it (a diagram is clickable by its heading
- * band as well as by its border), and `affine-model` cannot reach into
- * `affine-block-surface` where the declaration is resolved. One number, owned
- * by the layer that both the declaration and the hit test can read.
- *
- * It is the frame's TOP MARGIN — the inset the drawing gives up so the heading
- * has somewhere to be written — so the strip that is painted, the strip that is
- * picked and the strip that opens the rename are one number rather than three.
- *
- * 44 is the height of the cut-corner tag UML 2.5.1 Annex A draws the heading
- * in: a 20-unit label with the rest as breathing room above and below.
- * Changing it moves the heading, so it is a visual decision and not a hit-test
- * one.
- */
-export const UML_FRAME_BAND_HEIGHT = 44;
-/**
- * The word written in the heading tag, per kind.
- *
- * A table rather than the raw value so that a kind whose stored discriminant
- * and whose printed tag ever diverge has one place to say so. Today they are
- * the same four strings, and that is worth stating rather than assuming.
- *
- * `Partial` on purpose: a frame read off a document carries whatever string was
- * written there, including a kind from a later phase this build has never heard
- * of. Typing the lookup as total would make {@link
- * UmlDiagramElementModel.heading}'s `?? this.kind` fallback look like dead
- * defensive code, when it is the whole of the append-only promise.
- */
-export const UML_DIAGRAM_KIND_TAG = {
-    class: 'class',
-    pkg: 'pkg',
-    obj: 'obj',
-    uc: 'uc',
-    // Both are Annex A's own abbreviations, written exactly as the Annex writes
-    // them — `cmp` for the component diagram, `dep` for the deployment diagram.
-    cmp: 'cmp',
-    dep: 'dep',
-    // Annex A's own abbreviations again — `act` for the activity diagram, `stm`
-    // for the state machine diagram. `stm` is the one tag in the table that is
-    // NOT the kind spelled out: Annex A's frame kind is the two words `state
-    // machine`, and `stm` is the abbreviation it gives in their place.
-    act: 'act',
-    stm: 'stm',
-    // Annex A's abbreviation for the interaction frame, and the third tag in the
-    // table that is not the kind spelled out: the frame kind is `interaction`.
-    sd: 'sd',
-};
+import { UML_DIAGRAM_KIND_TAG, UML_FRAME_BAND_HEIGHT, } from './consts.js';
 /**
  * The UML diagram frame: the sheet one diagram is drawn on — a class diagram, a
  * package diagram, an object diagram, a use case diagram, a component diagram, a

package/dist/_pkgs/affine-model/elements/uml/fragment.d.ts

@@ -2,21 +2,6 @@ import type { SerializedXYWH } from '../../../global/gfx/index.js';
 import type { PointTestOptions } from '../../../std/gfx/index.js';
 import type { FrameworkBackgroundProps } from '../framework-background/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
-/**
- * Height of a combined fragment's OPERATOR BAND — the strip across its top the
- * pentagon tag is drawn in, in model units.
- *
- * Owned by the model for the reason {@link UML_FRAME_BAND_HEIGHT} is: the
- * fragment's own hit test reads it (a fragment is clickable by its tag strip as
- * well as by its border), and `affine-model` cannot reach into
- * `affine-block-surface` where the declaration is resolved.
- *
- * The diagram frame's own 44, and deliberately: §17.6.4 draws the operator in
- * the very same cut-corner pentagon Annex A draws a frame heading in — it IS a
- * frame, nested in another one — and two numbers for one piece of furniture
- * would drift.
- */
-export declare const UML_FRAGMENT_BAND = 44;
 /**
  * The INTERACTION OPERATOR of a combined fragment — the word written in its
  * pentagon, and the whole of what the fragment says (UML 2.5.1 §17.6.4).

package/dist/_pkgs/affine-model/elements/uml/fragment.js

@@ -35,21 +35,7 @@ var __runInitializers = (this && this.__runInitializers) || function (thisArg, i
 import { field } from '../../../std/gfx/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
 import { umlInNameBand } from './band.js';
-/**
- * Height of a combined fragment's OPERATOR BAND — the strip across its top the
- * pentagon tag is drawn in, in model units.
- *
- * Owned by the model for the reason {@link UML_FRAME_BAND_HEIGHT} is: the
- * fragment's own hit test reads it (a fragment is clickable by its tag strip as
- * well as by its border), and `affine-model` cannot reach into
- * `affine-block-surface` where the declaration is resolved.
- *
- * The diagram frame's own 44, and deliberately: §17.6.4 draws the operator in
- * the very same cut-corner pentagon Annex A draws a frame heading in — it IS a
- * frame, nested in another one — and two numbers for one piece of furniture
- * would drift.
- */
-export const UML_FRAGMENT_BAND = 44;
+import { UML_FRAGMENT_BAND } from './consts.js';
 /**
  * A COMBINED FRAGMENT — the rectangle drawn round part of a sequence diagram
  * with an operator in its corner (UML 2.5.1 §17.6.4), and, under the `ref`

package/dist/_pkgs/affine-model/elements/uml/index.d.ts

@@ -1,4 +1,5 @@
 export * from './band.js';
+export * from './consts.js';
 export * from './diagram.js';
 export * from './fragment.js';
 export * from './lifeline.js';

package/dist/_pkgs/affine-model/elements/uml/index.js

@@ -1,4 +1,5 @@
 export * from './band.js';
+export * from './consts.js';
 export * from './diagram.js';
 export * from './fragment.js';
 export * from './lifeline.js';

package/dist/_pkgs/affine-model/elements/uml/partition.d.ts

@@ -2,26 +2,6 @@ import type { SerializedXYWH } from '../../../global/gfx/index.js';
 import type { PointTestOptions } from '../../../std/gfx/index.js';
 import type { FrameworkBackgroundProps } from '../framework-background/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
-/**
- * Height of a partition's NAME BAND — the strip its name is written in, in
- * model units.
- *
- * Declared HERE, in the model, and re-exported by `@labre/affine-gfx-uml`, for
- * the reason {@link UML_FRAME_BAND_HEIGHT} is: the partition's own hit test
- * reads it (a swimlane is clickable by its header as well as by its border),
- * and `affine-model` cannot reach into `affine-block-surface` where the
- * declaration is resolved. One number, owned by the layer that both the
- * declaration and the hit test can read.
- *
- * It is the band's THICKNESS whichever edge the band is on — the top for a
- * vertical lane, the left for a horizontal one — because §15.6.4 draws one
- * header strip and turns it with the lane rather than resizing it.
- *
- * 36 against the diagram frame's 44: a partition header is a name and not a
- * `<kind> <name>` heading, and it is written inside a lane that already sits on
- * a sheet, so it reads as a subdivision rather than as a second sheet.
- */
-export declare const UML_PARTITION_BAND = 36;
 /**
  * Which way a partition is sliced — the one thing §15.6.4 lets an author choose
  * about a swimlane, and the thing that decides which edge the header is on.

package/dist/_pkgs/affine-model/elements/uml/partition.js

@@ -35,26 +35,7 @@ var __runInitializers = (this && this.__runInitializers) || function (thisArg, i
 import { field } from '../../../std/gfx/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
 import { umlInNameBand } from './band.js';
-/**
- * Height of a partition's NAME BAND — the strip its name is written in, in
- * model units.
- *
- * Declared HERE, in the model, and re-exported by `@labre/affine-gfx-uml`, for
- * the reason {@link UML_FRAME_BAND_HEIGHT} is: the partition's own hit test
- * reads it (a swimlane is clickable by its header as well as by its border),
- * and `affine-model` cannot reach into `affine-block-surface` where the
- * declaration is resolved. One number, owned by the layer that both the
- * declaration and the hit test can read.
- *
- * It is the band's THICKNESS whichever edge the band is on — the top for a
- * vertical lane, the left for a horizontal one — because §15.6.4 draws one
- * header strip and turns it with the lane rather than resizing it.
- *
- * 36 against the diagram frame's 44: a partition header is a name and not a
- * `<kind> <name>` heading, and it is written inside a lane that already sits on
- * a sheet, so it reads as a subdivision rather than as a second sheet.
- */
-export const UML_PARTITION_BAND = 36;
+import { UML_PARTITION_BAND } from './consts.js';
 /**
  * An activity PARTITION — the swimlane of UML 2.5.1 §15.6.4: the strip drawn
  * across an activity diagram saying who (or what) is responsible for the

package/dist/_pkgs/affine-model/elements/uml/region.d.ts

@@ -2,17 +2,6 @@ import type { SerializedXYWH } from '../../../global/gfx/index.js';
 import type { PointTestOptions } from '../../../std/gfx/index.js';
 import type { FrameworkBackgroundProps } from '../framework-background/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
-/**
- * Height of a region's NAME BAND — the strip its name is written in, in model
- * units.
- *
- * Owned by the model for the reason {@link UML_PARTITION_BAND} is: the region's
- * own hit test reads it, and `affine-model` cannot reach into the package where
- * the declaration is resolved. The same 36 the partition uses, and deliberately
- * so — the two are the same piece of furniture, a name written in a strip along
- * the top of a transparent frame, and two numbers would drift.
- */
-export declare const UML_REGION_BAND = 36;
 export type UmlRegionProps = FrameworkBackgroundProps & {
     /** The state name, written in the band — edited inline on dblclick. */
     name?: string;

package/dist/_pkgs/affine-model/elements/uml/region.js

@@ -35,17 +35,7 @@ var __runInitializers = (this && this.__runInitializers) || function (thisArg, i
 import { field } from '../../../std/gfx/index.js';
 import { FrameworkBackgroundElementModel } from '../framework-background/index.js';
 import { umlInNameBand } from './band.js';
-/**
- * Height of a region's NAME BAND — the strip its name is written in, in model
- * units.
- *
- * Owned by the model for the reason {@link UML_PARTITION_BAND} is: the region's
- * own hit test reads it, and `affine-model` cannot reach into the package where
- * the declaration is resolved. The same 36 the partition uses, and deliberately
- * so — the two are the same piece of furniture, a name written in a strip along
- * the top of a transparent frame, and two numbers would drift.
- */
-export const UML_REGION_BAND = 36;
+import { UML_REGION_BAND } from './consts.js';
 /**
  * A COMPOSITE STATE — the region of UML 2.5.1 §14.2.4: the rounded rectangle
  * drawn round the sub-states of a state that has its own state machine inside

package/dist/_pkgs/affine-model/headless.d.ts

@@ -0,0 +1,19 @@
+/**
+ * `@labre/affine-model/headless` — the model's data with no element class
+ * behind it: the enums and constants every surface element is written with,
+ * and the pure geometry an interchange reader computes with (ADR 0012, P3 as
+ * amended 2026-10-14).
+ *
+ * The package index re-exports every one of these unchanged; this entry
+ * exists for a caller that must not load `@labre/std/gfx` (and with it Lit and
+ * the drag-and-drop adapter): the headless `./interchange` entries of the
+ * framework bundles. Held by `interchange-headless.unit.spec.ts` in
+ * `packages/affine/all`. Add only from files that import nothing but
+ * `@labre/global` and types.
+ */
+export * from './consts/index.js';
+export * from './elements/bpmn/consts.js';
+export * from './elements/connector/end-label.js';
+export { DEFAULT_POLYGON_VERTICES } from './elements/shape/api/polygon.js';
+export * from './elements/uml/consts.js';
+export * from './elements/uml/lifeline.js';

package/dist/_pkgs/affine-model/headless.js

@@ -0,0 +1,19 @@
+/**
+ * `@labre/affine-model/headless` — the model's data with no element class
+ * behind it: the enums and constants every surface element is written with,
+ * and the pure geometry an interchange reader computes with (ADR 0012, P3 as
+ * amended 2026-10-14).
+ *
+ * The package index re-exports every one of these unchanged; this entry
+ * exists for a caller that must not load `@labre/std/gfx` (and with it Lit and
+ * the drag-and-drop adapter): the headless `./interchange` entries of the
+ * framework bundles. Held by `interchange-headless.unit.spec.ts` in
+ * `packages/affine/all`. Add only from files that import nothing but
+ * `@labre/global` and types.
+ */
+export * from './consts/index.js';
+export * from './elements/bpmn/consts.js';
+export * from './elements/connector/end-label.js';
+export { DEFAULT_POLYGON_VERTICES } from './elements/shape/api/polygon.js';
+export * from './elements/uml/consts.js';
+export * from './elements/uml/lifeline.js';

package/dist/_pkgs/affine-shared/headless.d.ts

@@ -0,0 +1,10 @@
+/**
+ * `@labre/affine-shared/headless` — the few shared helpers an interchange
+ * reader or writer calls, with no editor behind them (ADR 0012, P3 as amended
+ * 2026-10-14). The barrels (`./consts`, `./services`, `./utils`) re-export the
+ * same bindings; this entry exists for the headless `./interchange` graphs,
+ * held by `interchange-headless.unit.spec.ts` in `packages/affine/all`.
+ */
+export { NOTATION_NEUTRALS } from './consts/notation.js';
+export { fillPlaceholders, type TranslationParams, } from './services/translation-service/index.js';
+export { safeFilename } from './utils/file/filesys.js';

package/dist/_pkgs/affine-shared/headless.js

@@ -0,0 +1,10 @@
+/**
+ * `@labre/affine-shared/headless` — the few shared helpers an interchange
+ * reader or writer calls, with no editor behind them (ADR 0012, P3 as amended
+ * 2026-10-14). The barrels (`./consts`, `./services`, `./utils`) re-export the
+ * same bindings; this entry exists for the headless `./interchange` graphs,
+ * held by `interchange-headless.unit.spec.ts` in `packages/affine/all`.
+ */
+export { NOTATION_NEUTRALS } from './consts/notation.js';
+export { fillPlaceholders, } from './services/translation-service/index.js';
+export { safeFilename } from './utils/file/filesys.js';

package/dist/_pkgs/affine-shared/services/asset-picker-service.d.ts

@@ -0,0 +1,63 @@
+import type { ExtensionType } from '../../store/index.js';
+/**
+ * A blob the host ALREADY stores, as the editor references it: the block it
+ * lands in stores `sourceId` and nothing else of the bytes. The library never
+ * sends the bytes again (`BlobSource.set` is not called); it may read them
+ * once through the store's blob sources to measure an image when `width` or
+ * `height` is missing.
+ */
+export interface AssetRef {
+    /** The blob's key in the store's blob sources (the Labre app: its sha256). */
+    sourceId: string;
+    /** The file name, kept by an attachment card. */
+    name: string;
+    /** The MIME type. An image request ignores a ref that is not `image/*`. */
+    type: string;
+    /** In bytes. */
+    size: number;
+    /** An image's natural size; measured from the blob when either is absent. */
+    width?: number;
+    height?: number;
+}
+/**
+ * What the editor asks for.
+ *
+ * - `kind`: `image` for an image block, `file` for an attachment card.
+ * - `mode`: `insert` adds new blocks; `replace` swaps the picture of one
+ *   existing image (one ref is used, the first).
+ * - `multiple`: whether more than one ref is welcome (the image insertions).
+ * - `docId`: the document the result lands in, so the host can attach the
+ *   asset to that page (a guest of the page must be able to read it).
+ */
+export interface AssetPickerRequest {
+    kind: 'image' | 'file';
+    mode: 'insert' | 'replace';
+    multiple?: boolean;
+    docId: string;
+}
+/**
+ * Pick an asset from the host's own library (labre P4: the asset dialog of
+ * the shell), instead of the system file chooser.
+ *
+ * `pick` resolves with the refs to use, or `null` when the viewer cancelled:
+ * then nothing is written. An empty array is a cancellation too. A rejection
+ * is logged and nothing is written: show your own error before rejecting.
+ * Upload a new file into your library inside the dialog, then resolve with
+ * its ref: the editor never receives a `File` through this seam.
+ */
+export interface AssetPickerService {
+    pick(request: AssetPickerRequest): Promise<AssetRef[] | null>;
+}
+export declare const AssetPickerProvider: import("../../global/di/types.js").ServiceIdentifier<AssetPickerService> & (<U extends AssetPickerService = AssetPickerService>(variant: import("../../global/di/types.js").ServiceVariant) => import("../../global/di/types.js").ServiceIdentifier<U>);
+/**
+ * Host seam: the asset dialog. Present, the slash menu's Image, Attachment
+ * and PDF, the mobile keyboard toolbar's Image and Attachment, and the
+ * canvas's image and file buttons open it, and the image toolbar gains
+ * "Replace". Absent, every one of those opens the system file chooser as
+ * before, and there is no "Replace". Pasting and dropping files never go
+ * through it.
+ *
+ * `di.override`, like `FrameTemplateExtension`, so a later registration
+ * always wins and registering twice never throws at boot.
+ */
+export declare function AssetPickerExtension(service: AssetPickerService): ExtensionType;

package/dist/_pkgs/affine-shared/services/asset-picker-service.js

@@ -0,0 +1,20 @@
+import { createIdentifier } from '../../global/di/index.js';
+export const AssetPickerProvider = createIdentifier('AffineAssetPicker');
+/**
+ * Host seam: the asset dialog. Present, the slash menu's Image, Attachment
+ * and PDF, the mobile keyboard toolbar's Image and Attachment, and the
+ * canvas's image and file buttons open it, and the image toolbar gains
+ * "Replace". Absent, every one of those opens the system file chooser as
+ * before, and there is no "Replace". Pasting and dropping files never go
+ * through it.
+ *
+ * `di.override`, like `FrameTemplateExtension`, so a later registration
+ * always wins and registering twice never throws at boot.
+ */
+export function AssetPickerExtension(service) {
+    return {
+        setup: di => {
+            di.override(AssetPickerProvider, () => service);
+        },
+    };
+}

package/dist/_pkgs/affine-shared/services/frame-template-service.d.ts

@@ -0,0 +1,83 @@
+import type { DocSnapshot, ExtensionType } from '../../store/index.js';
+/**
+ * What "Save as template" on a frame's toolbar hands the host: the frame and
+ * everything it holds, serialized once, at the moment of the gesture.
+ *
+ * `snapshot` is a `DocSnapshot` the canvas's own template job inserts as is
+ * (`createTemplateJob(std, 'template').insertTemplate(snapshot)`, which mints
+ * fresh ids and lands every model in the viewer's active layer): keep it
+ * verbatim and give it back through {@link FrameTemplateService.list}. It is
+ * plain JSON. It names images and attachments by their blob id (`sourceId`)
+ * and never carries the bytes: the copy references them.
+ */
+export interface FrameTemplateDraft {
+    /** The document the frame was saved from. */
+    docId: string;
+    /** The frame's block id in that document. */
+    frameId: string;
+    /** The frame's title when it was saved (may be empty). */
+    title: string;
+    snapshot: DocSnapshot;
+}
+/** One saved frame, as the canvas's Templates panel lists it. */
+export interface SavedFrameTemplate {
+    /** Your own id for it; the panel uses it as the tile's identity. */
+    id: string;
+    title: string;
+    /** The `snapshot` of the {@link FrameTemplateDraft} you were given. */
+    snapshot: unknown;
+    /** An inline `<svg…` or an image URL; the panel's generic tile otherwise. */
+    preview?: string;
+}
+/** A saved frame inserted into a document, by your id for the template. */
+export interface FrameTemplateInsertion {
+    docId: string;
+    templateId: string;
+}
+/** Ids of a frame whose life the host may follow. */
+export interface FrameTemplateFrameRef {
+    docId: string;
+    frameId: string;
+}
+/**
+ * Frames saved as templates (labre P4): the host keeps them, the library
+ * serializes, lists and inserts them.
+ *
+ * - `save` is called by the frame toolbar's "Save as template"
+ *   (`blocks/frame/src/frame-toolbar.ts`). The library tells the viewer how it
+ *   went (a success or an error notification): do not notify yourself.
+ * - `list` feeds one category of the canvas's Templates panel
+ *   (`gfx/template`, `templateManagerFor`). It is called each time the panel
+ *   shows that category or searches across categories, never before.
+ * - `frameDeleted` is called when THIS viewer deletes a frame on a writable
+ *   document, never for a deletion that arrives from another peer (that peer
+ *   reported its own), so a deletion is reported once per author. It is called
+ *   for every frame, saved or not: ignore the ids you do not know.
+ * - `frameRestored` is called when this viewer brings back a frame it had
+ *   deleted in this session (undo). Whatever `frameDeleted` did must be
+ *   undoable by it: move a template to the trash, never destroy it.
+ * - `frameInserted` is called once a saved frame from that category is on the
+ *   canvas (the template job succeeded), with the document it landed in and
+ *   your id for the template: link what the copy references (its images) to
+ *   that document. Not called when the insertion failed.
+ *
+ * Both notifications may come twice for one gesture (two editors mounted on
+ * one document): make them idempotent.
+ */
+export interface FrameTemplateService {
+    save(draft: FrameTemplateDraft): Promise<void>;
+    list(): Promise<SavedFrameTemplate[]>;
+    frameDeleted?(frame: FrameTemplateFrameRef): void;
+    frameRestored?(frame: FrameTemplateFrameRef): void;
+    frameInserted?(insertion: FrameTemplateInsertion): void;
+}
+export declare const FrameTemplateProvider: import("../../global/di/types.js").ServiceIdentifier<FrameTemplateService> & (<U extends FrameTemplateService = FrameTemplateService>(variant: import("../../global/di/types.js").ServiceVariant) => import("../../global/di/types.js").ServiceIdentifier<U>);
+/**
+ * Host seam: keep frames saved as templates. Absent, the toolbar has no
+ * "Save as template", the Templates panel has no "Saved frames" category and
+ * nothing is reported when a frame is deleted.
+ *
+ * `di.override`, like `OutlinePanelExtension`, so a later registration always
+ * wins and registering twice never throws at boot.
+ */
+export declare function FrameTemplateExtension(service: FrameTemplateService): ExtensionType;