@formicoidea/labre-framework-c4 0.33.0

package/dist/toolbar/icons.d.ts

@@ -0,0 +1,90 @@
+/**
+ * The C4 senior-button tile: a person, a dashed relationship, and the system
+ * they use — the smallest complete C4 sentence, in the stencil's own blues.
+ *
+ * The one COLOURED glyph of this file. Everything below it is a 24×24
+ * monochrome outline drawn in `currentColor`, because a command glyph sits in a
+ * menu row and takes the row's colour; the tile is the framework's face on the
+ * toolbar and is painted in the palette the pack draws with (`consts.ts`).
+ */
+export declare const c4ToolbarIcon: import("lit-html").TemplateResult<2>;
+/** Person — a head over a rounded body, the stencil's own silhouette. */
+export declare const c4PersonIcon: import("lit-html").TemplateResult<2>;
+/**
+ * Person (external) — the same silhouette, DASHED. The stencil greys an
+ * external element out; a monochrome glyph has no grey to spend, so the dash is
+ * what carries "somebody else owns this" here.
+ */
+export declare const c4PersonExtIcon: import("lit-html").TemplateResult<2>;
+/** Software system — a plain rounded rectangle, which is what C4 draws. */
+export declare const c4SystemIcon: import("lit-html").TemplateResult<2>;
+/** Software system (external) — the same rectangle, dashed. */
+export declare const c4SystemExtIcon: import("lit-html").TemplateResult<2>;
+/** Container — a box INSIDE a box: one level in from the system. */
+export declare const c4ContainerIcon: import("lit-html").TemplateResult<2>;
+/** Component — the UML component: a box with two tabs down its leading edge. */
+export declare const c4ComponentIcon: import("lit-html").TemplateResult<2>;
+/** Database — a cylinder. */
+export declare const c4DatabaseIcon: import("lit-html").TemplateResult<2>;
+/** Mobile app — a phone: a tall bezel with a speaker slot and a home bar. */
+export declare const c4MobileIcon: import("lit-html").TemplateResult<2>;
+/** Web browser — a window with a chrome band and its three dots. */
+export declare const c4BrowserIcon: import("lit-html").TemplateResult<2>;
+/** Relationship — a dashed arrow with a filled head, exactly as it is drawn. */
+export declare const c4RelationshipIcon: import("lit-html").TemplateResult<2>;
+/** C4 board — a titled card with two elements and the arrow between them. */
+export declare const c4BoardIcon: import("lit-html").TemplateResult<2>;
+/** System boundary — a dashed rectangle, and nothing inside it to see. */
+export declare const c4SystemBoundaryIcon: import("lit-html").TemplateResult<2>;
+/**
+ * Container boundary — the same dashed rectangle, one level IN: a second,
+ * smaller frame drawn inside it. The pair reads the way the two boundaries
+ * relate on the canvas, which is the only difference the notation makes between
+ * them.
+ */
+export declare const c4ContainerBoundaryIcon: import("lit-html").TemplateResult<2>;
+/**
+ * Export as mermaid — a sheet with a page-corner fold and an arrow leaving it.
+ *
+ * Deliberately the SAME drawing as `bpmnExportXmlIcon`, down to the path data:
+ * it is the same gesture (take this board away as a file), and one gesture takes
+ * one glyph across the library. What it is not is a mermaid logo — the file
+ * format is what the menu LINE says, and a brand mark in a monochrome outline
+ * row would be the one icon nobody could recolour.
+ *
+ * Redrawn here rather than imported because BPMN's icons are that package's
+ * private module: a cross-framework import for one path would tie the C4 pack's
+ * build to BPMN's, and the two are meant to ship separately.
+ */
+export declare const c4ExportMermaidIcon: import("lit-html").TemplateResult<2>;
+/**
+ * Every command glyph, keyed by its `iconKey`.
+ *
+ * Registered together with the commands themselves
+ * (`CommandExtension(c4Commands, c4CommandIcons)`), so a key a descriptor names
+ * and this record does not hold renders as nothing — which is what the icon
+ * coverage test in `__tests__/commands.unit.spec.ts` exists to catch.
+ *
+ * {@link c4ExportMermaidIcon} is deliberately NOT here and is added to
+ * `c4CommandIcons` in `commands.ts` instead: this record is the TOOLBOX — the
+ * thirteen glyphs of things C4 DRAWS — and an export draws nothing.
+ *
+ * The legend's glyph is in neither, because the legend is no longer a command at
+ * all: it is `dddLegendIcon`, referenced straight from `config.ts` by the button
+ * that is now the only way to reach it (PO arbitration, 27/08/2026).
+ */
+export declare const C4_TOOLBOX_ICONS: {
+    readonly 'c4.person': import("lit-html").TemplateResult<2>;
+    readonly 'c4.person.external': import("lit-html").TemplateResult<2>;
+    readonly 'c4.system': import("lit-html").TemplateResult<2>;
+    readonly 'c4.system.external': import("lit-html").TemplateResult<2>;
+    readonly 'c4.container': import("lit-html").TemplateResult<2>;
+    readonly 'c4.component': import("lit-html").TemplateResult<2>;
+    readonly 'c4.database': import("lit-html").TemplateResult<2>;
+    readonly 'c4.mobile': import("lit-html").TemplateResult<2>;
+    readonly 'c4.browser': import("lit-html").TemplateResult<2>;
+    readonly 'c4.relationship': import("lit-html").TemplateResult<2>;
+    readonly 'c4.board': import("lit-html").TemplateResult<2>;
+    readonly 'c4.boundary.system': import("lit-html").TemplateResult<2>;
+    readonly 'c4.boundary.container': import("lit-html").TemplateResult<2>;
+};

package/dist/toolbar/icons.js

@@ -0,0 +1,157 @@
+import { svg } from 'lit';
+/**
+ * The C4 senior-button tile: a person, a dashed relationship, and the system
+ * they use — the smallest complete C4 sentence, in the stencil's own blues.
+ *
+ * The one COLOURED glyph of this file. Everything below it is a 24×24
+ * monochrome outline drawn in `currentColor`, because a command glyph sits in a
+ * menu row and takes the row's colour; the tile is the framework's face on the
+ * toolbar and is painted in the palette the pack draws with (`consts.ts`).
+ */
+export const c4ToolbarIcon = svg `
+  <svg viewBox="0 0 56 56" width="100%" height="100%" fill="none"
+       xmlns="http://www.w3.org/2000/svg">
+    <circle cx="13" cy="10.5" r="5" fill="#08427b"/>
+    <rect x="5" y="16.5" width="16" height="11" rx="5.5" fill="#08427b"/>
+    <path d="M12.5 28.5 L19.4 33.8" stroke="#08427b" stroke-width="2"
+          stroke-dasharray="3 3" stroke-linecap="round"/>
+    <path d="M23 36.5 L18.1 35.6 L20.7 32 Z" fill="#08427b"/>
+    <rect x="24" y="22" width="27" height="28" rx="4" fill="#1168bd"/>
+    <rect x="28" y="27" width="12" height="8" rx="2" fill="#438dd5"/>
+    <rect x="42" y="27" width="5" height="8" rx="2" fill="#438dd5"/>
+    <rect x="28" y="39" width="19" height="7" rx="2" fill="#85bbf0"/>
+  </svg>
+`;
+/* ── The four levels ───────────────────────────────────────────────────── */
+/** Person — a head over a rounded body, the stencil's own silhouette. */
+export const c4PersonIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <circle cx="12" cy="7" r="3.2" stroke="currentColor" stroke-width="1.6"/>
+  <rect x="5.5" y="12" width="13" height="8" rx="4" stroke="currentColor" stroke-width="1.6"/>
+</svg>`;
+/**
+ * Person (external) — the same silhouette, DASHED. The stencil greys an
+ * external element out; a monochrome glyph has no grey to spend, so the dash is
+ * what carries "somebody else owns this" here.
+ */
+export const c4PersonExtIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <circle cx="12" cy="7" r="3.2" stroke="currentColor" stroke-width="1.6" stroke-dasharray="2.6 2"/>
+  <rect x="5.5" y="12" width="13" height="8" rx="4" stroke="currentColor" stroke-width="1.6" stroke-dasharray="2.6 2"/>
+</svg>`;
+/** Software system — a plain rounded rectangle, which is what C4 draws. */
+export const c4SystemIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="3.5" y="6" width="17" height="12" rx="2.5" stroke="currentColor" stroke-width="1.6"/>
+</svg>`;
+/** Software system (external) — the same rectangle, dashed. */
+export const c4SystemExtIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="3.5" y="6" width="17" height="12" rx="2.5" stroke="currentColor" stroke-width="1.6" stroke-dasharray="2.6 2"/>
+</svg>`;
+/** Container — a box INSIDE a box: one level in from the system. */
+export const c4ContainerIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="2.5" y="4.5" width="19" height="15" rx="2.5" stroke="currentColor" stroke-width="1.6"/>
+  <rect x="6.5" y="8.5" width="11" height="7" rx="1.8" stroke="currentColor" stroke-width="1.4"/>
+</svg>`;
+/** Component — the UML component: a box with two tabs down its leading edge. */
+export const c4ComponentIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="6" y="5.5" width="14.5" height="13" rx="1.8" stroke="currentColor" stroke-width="1.6"/>
+  <rect x="3.5" y="8" width="5" height="3" stroke="currentColor" stroke-width="1.3"/>
+  <rect x="3.5" y="13" width="5" height="3" stroke="currentColor" stroke-width="1.3"/>
+</svg>`;
+/* ── The container flavours the stencil gives a silhouette of their own ─── */
+/** Database — a cylinder. */
+export const c4DatabaseIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <path d="M4.5 7 V17 C4.5 18.4 8 19.5 12 19.5 C16 19.5 19.5 18.4 19.5 17 V7" stroke="currentColor" stroke-width="1.6" stroke-linejoin="round"/>
+  <ellipse cx="12" cy="7" rx="7.5" ry="2.5" stroke="currentColor" stroke-width="1.6"/>
+</svg>`;
+/** Mobile app — a phone: a tall bezel with a speaker slot and a home bar. */
+export const c4MobileIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="7" y="2.5" width="10" height="19" rx="2.2" stroke="currentColor" stroke-width="1.6"/>
+  <path d="M10.5 5.2 H13.5" stroke="currentColor" stroke-width="1.3" stroke-linecap="round"/>
+  <path d="M10 18.8 H14" stroke="currentColor" stroke-width="1.3" stroke-linecap="round"/>
+</svg>`;
+/** Web browser — a window with a chrome band and its three dots. */
+export const c4BrowserIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="2.5" y="4.5" width="19" height="15" rx="2.2" stroke="currentColor" stroke-width="1.6"/>
+  <path d="M2.5 9 H21.5" stroke="currentColor" stroke-width="1.4"/>
+  <circle cx="5.6" cy="6.8" r="0.85" fill="currentColor"/>
+  <circle cx="8.3" cy="6.8" r="0.85" fill="currentColor"/>
+  <circle cx="11" cy="6.8" r="0.85" fill="currentColor"/>
+</svg>`;
+/* ── The connecting object ─────────────────────────────────────────────── */
+/** Relationship — a dashed arrow with a filled head, exactly as it is drawn. */
+export const c4RelationshipIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <path d="M3 12 H15.5" stroke="currentColor" stroke-width="1.8" stroke-dasharray="3 2.6" stroke-linecap="round"/>
+  <path d="M14.5 8.2 L21 12 L14.5 15.8 Z" fill="currentColor"/>
+</svg>`;
+/* ── The two frames ────────────────────────────────────────────────────── */
+/** C4 board — a titled card with two elements and the arrow between them. */
+export const c4BoardIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="2.5" y="3.5" width="19" height="17" rx="2" stroke="currentColor" stroke-width="1.6"/>
+  <path d="M5.5 7 H12" stroke="currentColor" stroke-width="1.4" stroke-linecap="round"/>
+  <rect x="5.5" y="10" width="6" height="4" rx="1" stroke="currentColor" stroke-width="1.3"/>
+  <rect x="13" y="14" width="6" height="4" rx="1" stroke="currentColor" stroke-width="1.3"/>
+  <path d="M11.5 13 L13.5 14.6" stroke="currentColor" stroke-width="1.2" stroke-dasharray="2 1.6"/>
+</svg>`;
+/** System boundary — a dashed rectangle, and nothing inside it to see. */
+export const c4SystemBoundaryIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="2.5" y="4.5" width="19" height="15" rx="2" stroke="currentColor" stroke-width="1.6" stroke-dasharray="3.2 2.4"/>
+</svg>`;
+/**
+ * Container boundary — the same dashed rectangle, one level IN: a second,
+ * smaller frame drawn inside it. The pair reads the way the two boundaries
+ * relate on the canvas, which is the only difference the notation makes between
+ * them.
+ */
+export const c4ContainerBoundaryIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <rect x="2.5" y="4.5" width="19" height="15" rx="2" stroke="currentColor" stroke-width="1.6" stroke-dasharray="3.2 2.4"/>
+  <rect x="6.5" y="8" width="11" height="8" rx="1.6" stroke="currentColor" stroke-width="1.3" stroke-dasharray="2.4 1.8"/>
+</svg>`;
+/* ── The gesture that takes a board away ───────────────────────────────── */
+/**
+ * Export as mermaid — a sheet with a page-corner fold and an arrow leaving it.
+ *
+ * Deliberately the SAME drawing as `bpmnExportXmlIcon`, down to the path data:
+ * it is the same gesture (take this board away as a file), and one gesture takes
+ * one glyph across the library. What it is not is a mermaid logo — the file
+ * format is what the menu LINE says, and a brand mark in a monochrome outline
+ * row would be the one icon nobody could recolour.
+ *
+ * Redrawn here rather than imported because BPMN's icons are that package's
+ * private module: a cross-framework import for one path would tie the C4 pack's
+ * build to BPMN's, and the two are meant to ship separately.
+ */
+export const c4ExportMermaidIcon = svg `<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <path d="M13.5 3.5H7a1.5 1.5 0 0 0-1.5 1.5v14A1.5 1.5 0 0 0 7 20.5h3" stroke="currentColor" stroke-width="1.5" stroke-linecap="round"/>
+  <path d="M13.5 3.5 18.5 8.5V12" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
+  <path d="M16 20.5v-6M13.5 18l2.5 2.5 2.5-2.5" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
+</svg>`;
+/**
+ * Every command glyph, keyed by its `iconKey`.
+ *
+ * Registered together with the commands themselves
+ * (`CommandExtension(c4Commands, c4CommandIcons)`), so a key a descriptor names
+ * and this record does not hold renders as nothing — which is what the icon
+ * coverage test in `__tests__/commands.unit.spec.ts` exists to catch.
+ *
+ * {@link c4ExportMermaidIcon} is deliberately NOT here and is added to
+ * `c4CommandIcons` in `commands.ts` instead: this record is the TOOLBOX — the
+ * thirteen glyphs of things C4 DRAWS — and an export draws nothing.
+ *
+ * The legend's glyph is in neither, because the legend is no longer a command at
+ * all: it is `dddLegendIcon`, referenced straight from `config.ts` by the button
+ * that is now the only way to reach it (PO arbitration, 27/08/2026).
+ */
+export const C4_TOOLBOX_ICONS = {
+    'c4.person': c4PersonIcon,
+    'c4.person.external': c4PersonExtIcon,
+    'c4.system': c4SystemIcon,
+    'c4.system.external': c4SystemExtIcon,
+    'c4.container': c4ContainerIcon,
+    'c4.component': c4ComponentIcon,
+    'c4.database': c4DatabaseIcon,
+    'c4.mobile': c4MobileIcon,
+    'c4.browser': c4BrowserIcon,
+    'c4.relationship': c4RelationshipIcon,
+    'c4.board': c4BoardIcon,
+    'c4.boundary.system': c4SystemBoundaryIcon,
+    'c4.boundary.container': c4ContainerBoundaryIcon,
+};

package/dist/toolbar/senior-tool.d.ts

@@ -0,0 +1 @@
+export declare const c4SeniorTool: import("@formicoidea/labre-core/store").ExtensionType;

package/dist/toolbar/senior-tool.js

@@ -0,0 +1,11 @@
+import { SeniorToolExtension } from '@formicoidea/labre-core/widgets/edgeless-toolbar';
+import { html } from 'lit';
+export const c4SeniorTool = SeniorToolExtension('c4', ({ block }) => {
+    return {
+        name: 'C4 model',
+        labelKey: 'com.labre.framework.c4',
+        content: html `<edgeless-c4-senior-button
+      .edgeless=${block}
+    ></edgeless-c4-senior-button>`,
+    };
+});

package/dist/translations.d.ts

@@ -0,0 +1,18 @@
+import { type TranslationKeyManifestEntry } from '@formicoidea/labre-core/std';
+/**
+ * THIS framework's contribution to the translation-key manifest — every
+ * `com.labre.*` key C4 can hand to `TranslationProvider.t`, derived from the
+ * very declarations the editor registers (never restated).
+ *
+ * The contribution ships WITH the framework, exactly as BPMN's does: in the
+ * bundled distribution `@formicoidea/labre-framework-c4` carries it, and a host
+ * composes it into its catalogue the same way it already composes `c4Commands`
+ * into the command registry. See `packages/affine/all/src/translations.ts`.
+ *
+ * The two BACKGROUND declarations are walked even though neither carries a
+ * `labelKey` today: both frames write the user's own words and have no
+ * vocabulary to fall back to (`background.ts`). Walking them costs nothing and
+ * means the day one of them gains a declared label the manifest already names
+ * it — which is the whole reason these lists are derived rather than written.
+ */
+export declare const c4TranslationEntries: TranslationKeyManifestEntry[];

package/dist/translations.js

@@ -0,0 +1,42 @@
+import { collectTranslationKeys, commandTranslationEntries, mergeTranslationEntries, } from '@formicoidea/labre-core/std';
+import { C4_BOARD_BACKGROUND, C4_BOUNDARY_BACKGROUND } from './background.js';
+import { c4Commands } from './commands.js';
+import { C4_BOARD_LEVEL_MENU } from './levels.js';
+import { C4_PROFILES } from './profiles.js';
+import { C4_ROLES } from './roles.js';
+import { C4_RULES } from './rules.js';
+/**
+ * THIS framework's contribution to the translation-key manifest — every
+ * `com.labre.*` key C4 can hand to `TranslationProvider.t`, derived from the
+ * very declarations the editor registers (never restated).
+ *
+ * The contribution ships WITH the framework, exactly as BPMN's does: in the
+ * bundled distribution `@formicoidea/labre-framework-c4` carries it, and a host
+ * composes it into its catalogue the same way it already composes `c4Commands`
+ * into the command registry. See `packages/affine/all/src/translations.ts`.
+ *
+ * The two BACKGROUND declarations are walked even though neither carries a
+ * `labelKey` today: both frames write the user's own words and have no
+ * vocabulary to fall back to (`background.ts`). Walking them costs nothing and
+ * means the day one of them gains a declared label the manifest already names
+ * it — which is the whole reason these lists are derived rather than written.
+ */
+export const c4TranslationEntries = mergeTranslationEntries(commandTranslationEntries(c4Commands), collectTranslationKeys('role', C4_ROLES), collectTranslationKeys('background', [
+    C4_BOARD_BACKGROUND,
+    C4_BOUNDARY_BACKGROUND,
+    // The LEVEL a board declares, and the words the picker offers it under.
+    //
+    // Filed under `background` with the two declarations above, and it is the
+    // honest bucket rather than a convenient one: `level` is a prop of the
+    // board BACKGROUND, these are the names of the values it can take, and
+    // the table is walked exactly as the two declarations beside it are —
+    // nothing is restated in `affine/all`, so a key added to the picker
+    // reaches a host's catalogue by construction.
+    C4_BOARD_LEVEL_MENU,
+]), 
+// AFTER the two above, and the order is load-bearing: a rule carries its
+// framework's `roles` and, for `c4.person-in-boundary`, the boundary's own
+// declaration, so walking the rules reaches keys those two lists already
+// named. `mergeTranslationEntries` keeps the FIRST occurrence, which is what
+// makes each key report the source it actually comes from.
+collectTranslationKeys('rule', C4_RULES), collectTranslationKeys('profile', C4_PROFILES));

package/dist/type-line.d.ts

@@ -0,0 +1,175 @@
+import type { C4NodeKind } from '@formicoidea/labre-core/model';
+/**
+ * The middle tier of a C4 element's label — `[Person]`, `[Software System]`,
+ * `[Container: Java]` — SEMI-DERIVED: the word comes from the kind, the
+ * technology from the author.
+ *
+ * ## Semi-derived, and where the line actually lives
+ *
+ * The line is a real canvas TEXT element now (PO recette, 28/08/2026): a C4
+ * component is the shape and its own words, grouped, and every tier is edited in
+ * place like any other text on the canvas rather than typed into a form. So the
+ * string IS stored — but only half of it is the author's. The bracketed word is
+ * the notation's and comes from `kind`, which is what the renderer paints and
+ * what the exporter maps; letting an author retype it would be letting the words
+ * disagree with the picture.
+ *
+ * {@link normalizeC4TypeLine} is what keeps the halves apart. It runs when an
+ * edit COMMITS, reads whatever was typed for the one thing the notation leaves
+ * to the author — the technology — and writes the canonical line back. Type
+ * `Java` and the line becomes `[Container: Java]`; type `[Database: Java]` on a
+ * cylinder and it becomes `[Container: Java]`, because a database IS a container
+ * and the stencil says so.
+ */
+/**
+ * The base word each kind is announced by, verbatim from the stencil's own
+ * `<desc>` strings (`C4Model_default.svg`, the PO's reference model).
+ *
+ * Two readings are worth spelling out, because both look like mistakes:
+ *
+ * - `database` says **Container**, not "Database". The stencil labels the
+ *   cylinder `[Container: technology]` exactly as it labels the plain box: a
+ *   database is a CONTAINER, and the cylinder is a picture of one, not a fourth
+ *   level. (The mermaid export still emits `ContainerDb` — that is the one
+ *   specialisation mermaid's own grammar draws, and it is a different question
+ *   from what the box says on the canvas.)
+ * - an `-ext` variant says the same word as the kind it is external to. What
+ *   "external" changes is the COLOUR — grey — and the stencil's gray sheet
+ *   carries the identical `[Person]` / `[Software System]` wording.
+ *
+ * `Record<C4NodeKind, …>` and therefore compile-total: a kind added to the model
+ * without a word to announce it fails the build here.
+ */
+export declare const C4_TYPE_WORD: Record<C4NodeKind, string>;
+/**
+ * The type line as it is drawn, brackets included.
+ *
+ * The technology is appended only when the author actually set one — an empty
+ * box, or one holding nothing but spaces, is not a technology and must not
+ * produce a dangling `[Container: ]`. Whitespace runs collapse for the same
+ * reason they do in the mermaid sanitizer: the line is one line.
+ *
+ * Pure, total and `std`-free, so the renderer, the exporter and a test can all
+ * ask the same question and get the same answer.
+ */
+export declare function c4TypeLine(kind: C4NodeKind, technology?: string): string;
+/**
+ * The technology an author stated in a type line, whatever shape they left it
+ * in — `''` when they stated none.
+ *
+ * Total over every string, which is what it has to be: this reads a canvas TEXT
+ * element somebody edited in place, so its input is not a field with a grammar,
+ * it is whatever was typed. Every one of these is a line this has met:
+ *
+ * ```
+ * [Container: Java]  →  Java      the canonical form
+ * Container: Java    →  Java      brackets deleted while editing
+ * Java               →  Java      the whole line selected and retyped
+ * [Container]        →  ''        the word alone: no technology stated
+ * [Container: ]      →  ''        the technology deleted, brackets kept
+ * https://x/docs     →  https://x/docs   a colon that is NOT a prefix
+ * ```
+ *
+ * Pure and `std`-free, so the commit hook, the exporter and a test all read the
+ * same line the same way.
+ *
+ * It deliberately does NOT know about the creation placeholder: a node created
+ * and never touched carries `[Container: technology]`, and reading that as "no
+ * technology" here would make a focus-and-blur silently rewrite it to
+ * `[Container]` — the normalizer would eat the stencil's own prompt. The
+ * placeholder is a question for whoever asks what the element STATES, which is
+ * the exporter, and it is answered there.
+ */
+export declare function technologyOfTypeLine(text: string | null | undefined): string;
+/**
+ * A type line as it must be STORED, whatever was typed into it.
+ *
+ * The semi-derived rule of the PO's recette, in one function: read the one half
+ * the author owns, write the whole line back from the kind. `[Person: Java]`
+ * typed on a container becomes `[Container: Java]`, a bare `Java` becomes
+ * `[Container: Java]`, and an emptied line becomes `[Container]`.
+ *
+ * Idempotent by construction — `normalize(normalize(x)) === normalize(x)` —
+ * which is what lets it run on every commit without a guard.
+ */
+export declare function normalizeC4TypeLine(kind: C4NodeKind, rawText: string | null | undefined): string;
+/**
+ * The word a fresh type line prompts the author with, in the technology's slot.
+ *
+ * The stencil's own: its container reads `[Container: technology]` before
+ * anybody fills it in. A prompt rather than a value — see
+ * {@link C4_TYPE_PLACEHOLDER}.
+ */
+export declare const TYPE_TECHNOLOGY_PLACEHOLDER = "technology";
+/**
+ * Which kinds announce a technology in their type line AT ALL.
+ *
+ * The notation's own division and not mermaid's, though the two agree: a person
+ * is not built with a technology and a software system's is a level down, so
+ * both are written `[Person]` / `[Software System]` full stop. Every container
+ * — the cylinder, the phone and the browser window included — and every
+ * component carries `[Word: technology]`, because at those two levels "what is
+ * it built with" is the question the diagram exists to answer.
+ *
+ * This decides the PLACEHOLDER only. An author who types a technology onto a
+ * person gets it drawn, exactly as `c4TypeLine` has always drawn it: the
+ * notation is a prompt here, not a validator.
+ */
+export declare const C4_TYPE_TAKES_TECHNOLOGY: Record<C4NodeKind, boolean>;
+/**
+ * The type line a freshly created element is born carrying, per kind.
+ *
+ * Every tier of a C4 component exists from the moment it is drawn (PO
+ * arbitration, 28/08/2026), so the author meets three lines of stencil rather
+ * than a box and two invisible slots they have to be told about. What they meet
+ * is what the official stencil shows: `[Person]`, `[Software System]`,
+ * `[Container: technology]`, `[Component: technology]`.
+ *
+ * A PROMPT, not a value: {@link C4_TYPE_PLACEHOLDER} is what the exporter
+ * compares against to decide the author has stated nothing yet, so an untouched
+ * element exports as `Container(alias, "Container")` rather than as one built
+ * with a technology literally called "technology".
+ */
+export declare const C4_TYPE_PLACEHOLDER: Record<C4NodeKind, string>;
+/**
+ * The type line a component should carry once its shape has morphed from `from`
+ * to `to` — or `null` when the line is the AUTHOR's and must not be touched.
+ *
+ * ## Why a morph has to ask this at all
+ *
+ * The bracketed word is derived from `kind` (see the head of this file), so a
+ * shape that becomes a component while its caption still reads `[Container]` is
+ * a picture contradicting its own words. But the caption is a canvas TEXT
+ * element an architect may have typed anything into, and rewriting that would
+ * be the morph taking away something nobody asked it to touch. So the rule is
+ * the narrowest one that fixes the contradiction:
+ *
+ * - the SOURCE kind's untouched prompt (`[Container: technology]`) becomes the
+ *   TARGET's own prompt — `[Person]` on the way to a person, not `[Person:
+ *   technology]`, because a person is not built with a technology
+ *   ({@link C4_TYPE_TAKES_TECHNOLOGY});
+ * - a line that is exactly what the source kind DERIVES — `[Container: React]`,
+ *   the form {@link normalizeC4TypeLine} leaves behind after every edit — is
+ *   re-derived for the target, technology and all: `[Component: React]`;
+ * - anything else is the author's and comes back `null`. A line reading
+ *   `see ADR 0042`, or one mid-edit, survives the morph verbatim.
+ *
+ * The placeholder is tested FIRST and not folded into the second branch, which
+ * would find it too: `technologyOfTypeLine('[Container: technology]')` is the
+ * literal word `technology`, and carrying it across would hand a person the
+ * `[Person: technology]` no stencil ever draws.
+ *
+ * ## Inert on today's families, and kept anyway
+ *
+ * Every family declared in `./morph.ts` shares one {@link C4_TYPE_WORD} — all
+ * four containers say `Container`, both people say `Person`, both systems say
+ * `Software System` — and shares its {@link C4_TYPE_TAKES_TECHNOLOGY} answer
+ * too, so on the shipped table this function returns the line it was given and
+ * nothing visibly happens. That is a property of the FAMILIES, which are data
+ * and grow by declaration, not of the notation: the moment a family gains a
+ * member that announces itself differently, the caption follows the shape
+ * without anyone being prompted to remember it should.
+ *
+ * Pure, total and `std`-free, like everything else in this file.
+ */
+export declare function c4MorphedTypeLine(from: C4NodeKind, to: C4NodeKind, rawText: string | null | undefined): string | null;