@formicoidea/labre-framework-edgy 0.41.0 → 0.42.0

package/LICENSE

@@ -0,0 +1,384 @@
+# Mozilla Public License Version 2.0
+
+Copyright (c) TOEVERYTHING PTE. LTD. and its affiliates.
+
+1. Definitions
+
+---
+
+1.1. "Contributor"
+means each individual or legal entity that creates, contributes to
+the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+means the combination of the Contributions of others (if any) used
+by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+means Source Code Form to which the initial Contributor has attached
+the notice in Exhibit A, the Executable Form of such Source Code
+Form, and Modifications of such Source Code Form, in each case
+including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+means a work that combines Covered Software with other material, in
+a separate file or files, that is not Covered Software.
+
+1.8. "License"
+means this document.
+
+1.9. "Licensable"
+means having the right to grant, to the maximum extent possible,
+whether at the time of the initial grant or subsequently, any and
+all of the rights conveyed by this License.
+
+1.10. "Modifications"
+means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+means any patent claim(s), including without limitation, method,
+process, and apparatus claims, in any patent Licensable by such
+Contributor that would be infringed, but for the grant of the
+License, by the making, using, selling, offering for sale, having
+made, import, or transfer of either its Contributions or its
+Contributor Version.
+
+1.12. "Secondary License"
+means either the GNU General Public License, Version 2.0, the GNU
+Lesser General Public License, Version 2.1, the GNU Affero General
+Public License, Version 3.0, or any later versions of those
+licenses.
+
+1.13. "Source Code Form"
+means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+means an individual or a legal entity exercising rights under this
+License. For legal entities, "You" includes any entity that
+controls, is controlled by, or is under common control with You. For
+purposes of this definition, "control" means (a) the power, direct
+or indirect, to cause the direction or management of such entity,
+whether by contract or otherwise, or (b) ownership of more than
+fifty percent (50%) of the outstanding shares or beneficial
+ownership of such entity.
+
+2. License Grants and Conditions
+
+---
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+Licensable by such Contributor to use, reproduce, make available,
+modify, display, perform, distribute, and otherwise exploit its
+Contributions, either on an unmodified basis, with Modifications, or
+as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+for sale, have made, import, and otherwise transfer either its
+Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+or
+
+(b) for infringements caused by: (i) Your and any other third party's
+modifications of Covered Software, or (ii) the combination of its
+Contributions with other software (except as part of its Contributor
+Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+
+---
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+Form, as described in Section 3.1, and You must inform recipients of
+the Executable Form how they can obtain a copy of such Source Code
+Form by reasonable means in a timely manner, at a charge no more
+than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+License, or sublicense it under different terms, provided that the
+license for the Executable Form does not attempt to limit or alter
+the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+
+---
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+
+---
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+---
+
+-                                                                      *
+- 6.  Disclaimer of Warranty \*
+- ------------------------- \*
+-                                                                      *
+- Covered Software is provided under this License on an "as is" \*
+- basis, without warranty of any kind, either expressed, implied, or \*
+- statutory, including, without limitation, warranties that the \*
+- Covered Software is free of defects, merchantable, fit for a \*
+- particular purpose or non-infringing. The entire risk as to the \*
+- quality and performance of the Covered Software is with You. \*
+- Should any Covered Software prove defective in any respect, You \*
+- (not any Contributor) assume the cost of any necessary servicing, \*
+- repair, or correction. This disclaimer of warranty constitutes an \*
+- essential part of this License. No use of any Covered Software is \*
+- authorized under this License except under this disclaimer. \*
+-                                                                      *
+
+---
+
+---
+
+-                                                                      *
+- 7.  Limitation of Liability \*
+- -------------------------- \*
+-                                                                      *
+- Under no circumstances and under no legal theory, whether tort \*
+- (including negligence), contract, or otherwise, shall any \*
+- Contributor, or anyone who distributes Covered Software as \*
+- permitted above, be liable to You for any direct, indirect, \*
+- special, incidental, or consequential damages of any character \*
+- including, without limitation, damages for lost profits, loss of \*
+- goodwill, work stoppage, computer failure or malfunction, or any \*
+- and all other commercial damages or losses, even if such party \*
+- shall have been informed of the possibility of such damages. This \*
+- limitation of liability shall not apply to liability for death or \*
+- personal injury resulting from such party's negligence to the \*
+- extent applicable law prohibits such limitation. Some \*
+- jurisdictions do not allow the exclusion or limitation of \*
+- incidental or consequential damages, so this exclusion and \*
+- limitation may not apply to You. \*
+-                                                                      *
+
+---
+
+8. Litigation
+
+---
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+
+---
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+
+---
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+## Exhibit A - Source Code Form License Notice
+
+This Source Code Form is subject to the terms of the Mozilla Public
+License, v. 2.0. If a copy of the MPL was not distributed with this
+file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+## Exhibit B - "Incompatible With Secondary Licenses" Notice
+
+This Source Code Form is "Incompatible With Secondary Licenses", as
+defined by the Mozilla Public License, v. 2.0.

package/dist/commands.d.ts

@@ -1,4 +1,7 @@
+import type { ChromeWording } from '@formicoidea/labre-core/shared/services';
 import type { CommandDescriptor } from '@formicoidea/labre-core/std';
 import type { TemplateResult } from 'lit';
+/** For `translations.ts`'s manifest. */
+export declare const EDGY_LEGEND_CHROME_WORDINGS: readonly ChromeWording[];
 export declare const edgyCommands: CommandDescriptor[];
 export declare const edgyCommandIcons: Record<string, TemplateResult>;

package/dist/commands.js

@@ -1,6 +1,99 @@
 import { GfxControllerIdentifier } from '@formicoidea/labre-core/std/gfx';
 import { activateEdgyRelation, createEdgyBoard, createEdgyBox, createEdgyDynamic, createEdgyFacets, createEdgyPeople, } from './actions.js';
-import { edgyActivityIcon, edgyBoardIcon, edgyDynamicIcon, edgyFacetsIcon, edgyObjectIcon, edgyOutcomeIcon, edgyPeopleIcon, edgyRelationIcon, } from './toolbar/icons.js';
+import { EDGY_DYNAMIC_NODES, EDGY_ZONE_FILL, EDGY_ZONES, edgyElementLabel, edgyElementLabelKey, } from './metamodel.js';
+import { NODE_FILL, NODE_STROKE } from './node/consts.js';
+import { EDGY_ROLE } from './roles.js';
+import { edgyActivityIcon, edgyBoardIcon, edgyDynamicIcon, edgyFacetsIcon, edgyObjectIcon, edgyOutcomeIcon, edgyPeopleIcon, edgyRelationIcon, edgyToolbarIcon, } from './toolbar/icons.js';
+/**
+ * The EDGY toolbox as commands. Before PF3 these seven artefacts existed ONLY
+ * as hard-coded buttons, so EDGY was entirely invisible to Settings ›
+ * Shortcuts; they are all bindable now, all keyless by default (`docs/adr/0008`).
+ *
+ * An eighth entry joined them on the PO recette of 26/08/2026, and it is the
+ * first EDGY command that arms a TOOL rather than dropping an artefact:
+ * `addRelation`. Until it landed the 24 typed relations of the metamodel could
+ * only be born of the "EDGY dynamic" template, so a practitioner drawing their
+ * own board had no way of saying "this Process requires that Asset" — see
+ * `../relation.ts` for why there is one entry and not twenty-two.
+ */
+/* ── The legend, SUBSCRIBED rather than tabulated (`docs/adr/0026`) ────── */
+/**
+ * The three intersection elements share ONE section: Organisation, Product and
+ * Brand are not three facets, they are the three lenses between them, and the
+ * diagram says so by drawing them in the overlaps. The key is the one the
+ * facets seed already carries.
+ */
+const SECTION_INTERSECTIONS = [
+    'com.labre.edgy.seed.intersections-title',
+    'Intersections',
+];
+/**
+ * The two section titles that name a GROUPING of roles rather than a role —
+ * "Base elements" and "Relations" — so each mints a key of its own where the
+ * facets and the intersections reuse the metamodel's seeds.
+ */
+const SECTION_BASE = [
+    'com.labre.edgy.legend.section.base-elements',
+    'Base elements',
+];
+const SECTION_RELATIONS = [
+    'com.labre.edgy.legend.section.relations',
+    'Relations',
+];
+/** For `translations.ts`'s manifest. */
+export const EDGY_LEGEND_CHROME_WORDINGS = [
+    SECTION_BASE,
+    SECTION_RELATIONS,
+];
+/**
+ * One row per official element of `zone`, in the metamodel's own order, in the
+ * fill the diagram PAINTS that zone with — derived, never restated, so a
+ * thirteenth element gets its row the same way it gets its role.
+ */
+function zoneEntries(zone, section) {
+    return Object.entries(EDGY_DYNAMIC_NODES)
+        .filter(([, node]) => node.zone === zone)
+        .map(([name]) => ({
+        role: EDGY_ROLE[name],
+        row: { swatch: 'square', color: EDGY_ZONE_FILL[zone] },
+        section,
+    }));
+}
+/**
+ * The twelve official elements, all twelve subscribed by ONE command.
+ *
+ * They are stamped in exactly one place — the "EDGY dynamic" template
+ * (`templates/dynamic.ts`) — and there is no "add a Content" gesture to hang
+ * them off individually: twelve more catalogue entries for gestures the
+ * framework does not offer would blow the senior sub-menu's cap for nothing.
+ * So this is the case `CommandDescriptor.legend` is a LIST for, and the case
+ * `CommandLegendEntry.section` exists for: one command, twelve rows, four
+ * sub-titles.
+ *
+ * A facet's section says the facet's own name, so it reuses the key the
+ * metamodel's seeds already carry: the legend and the facets diagram say
+ * "Identity" with one key, not two.
+ */
+const DYNAMIC_LEGEND = EDGY_ZONES.flatMap(zone => zoneEntries(zone.id, zone.group === 'facet'
+    ? [edgyElementLabelKey(zone.id), edgyElementLabel(zone.id)]
+    : SECTION_INTERSECTIONS));
+/**
+ * One of the four base elements, listed only when one is on the board BARE.
+ *
+ * `exact` is what makes "bare" true. Detection is otherwise an ancestor walk,
+ * and the twelve official elements specialise these four — Content is an
+ * object, Story an activity — so an "Object" row would appear on a board
+ * carrying nothing but Contents, keyed to a white swatch that is drawn nowhere
+ * on it. White because that is the fill the palette gives them.
+ */
+function baseEntry(kind) {
+    return {
+        role: EDGY_ROLE[kind],
+        exact: true,
+        row: { swatch: 'square', color: NODE_FILL },
+        section: SECTION_BASE,
+    };
+}
 const SPECS = [
     {
         id: 'addFacets',
@@ -16,6 +109,7 @@ const SPECS = [
         iconKey: 'edgy.dynamic',
         category: 'diagrams',
         element: 'template:dynamic',
+        legend: DYNAMIC_LEGEND,
         run: createEdgyDynamic,
     },
     {
@@ -33,6 +127,7 @@ const SPECS = [
         iconKey: 'edgy.people',
         category: 'elements',
         element: 'node:people',
+        legend: baseEntry('people'),
         run: createEdgyPeople,
     },
     {
@@ -41,6 +136,7 @@ const SPECS = [
         iconKey: 'edgy.outcome',
         category: 'elements',
         element: 'node:outcome',
+        legend: baseEntry('outcome'),
         run: std => createEdgyBox(std, 'outcome'),
     },
     {
@@ -49,6 +145,7 @@ const SPECS = [
         iconKey: 'edgy.object',
         category: 'elements',
         element: 'node:object',
+        legend: baseEntry('object'),
         run: std => createEdgyBox(std, 'object'),
     },
     {
@@ -57,6 +154,7 @@ const SPECS = [
         iconKey: 'edgy.activity',
         category: 'elements',
         element: 'node:activity',
+        legend: baseEntry('activity'),
         run: std => createEdgyBox(std, 'activity'),
     },
     {
@@ -67,6 +165,17 @@ const SPECS = [
         category: 'relations',
         kind: 'tool',
         element: 'connector:relation',
+        // ONE row for the whole relation family, keyed on the PARENT role: a board
+        // carrying "content expresses purpose" carries `edgy:expresses`, which IS a
+        // relation, and that is all the legend has to say. Twenty-two rows naming
+        // the verbs would restate the metamodel rather than document the drawing —
+        // and the verb travels on the link itself, visible, where it belongs.
+        legend: {
+            role: EDGY_ROLE.relation,
+            // The stroke `activateEdgyRelation` arms the connector tool with.
+            row: { swatch: 'line', color: NODE_STROKE },
+            section: SECTION_RELATIONS,
+        },
         run: std => activateEdgyRelation(std.get(GfxControllerIdentifier)),
     },
 ];
@@ -91,6 +200,7 @@ export const edgyCommands = SPECS.map((spec, order) => ({
     availability: 'always',
     run: spec.run,
     telemetry: { framework: 'edgy', element: spec.element, board: spec.board },
+    ...(spec.legend ? { legend: spec.legend } : {}),
 }));
 export const edgyCommandIcons = {
     'edgy.facets': edgyFacetsIcon,
@@ -101,4 +211,7 @@ export const edgyCommandIcons = {
     'edgy.object': edgyObjectIcon,
     'edgy.activity': edgyActivityIcon,
     'edgy.relation': edgyRelationIcon,
+    // The senior button's 56×56 glyph, so `FrameworkDescriptor.iconKey` resolves
+    // through `getCommandIcon`.
+    'edgy.toolbar': edgyToolbarIcon,
 };

package/dist/element-view.d.ts

@@ -1,29 +1,27 @@
+import type { EditableBackgroundLabel } from '@formicoidea/labre-core/blocks/surface';
+import { FrameworkBackgroundView } from '@formicoidea/labre-core/blocks/surface';
 import type { EdgyFacetsElementModel } from '@formicoidea/labre-core/model';
-import type { EditorHost } from '@formicoidea/labre-core/std';
-import type { PointTestOptions } from '@formicoidea/labre-core/std/gfx';
-import { GfxElementModelView } from '@formicoidea/labre-core/std/gfx';
-export declare class EdgyView extends GfxElementModelView<EdgyFacetsElementModel> {
+/**
+ * The EDGY facets diagram's view: the shared background gesture, aimed by this
+ * framework's own label layout.
+ *
+ * The three facet names are NOT declared in a `FrameworkBackgroundDef` — the
+ * diagram is a Venn figure fitted into a reference space, and its labels hang
+ * off the circles rather than off a plot — so the hit test stays here, mapped
+ * with the SAME fit the renderer used. Everything above it (where a
+ * double-click is allowed to land, the in-place `<input>`, the commit that
+ * refuses to write an untouched value) comes from
+ * {@link FrameworkBackgroundView}, which is where this diagram's own copy of it
+ * went — see issue #355.
+ */
+export declare class EdgyView extends FrameworkBackgroundView<EdgyFacetsElementModel> {
     static type: string;
-    /** The in-place `<input>` used to edit a label, or null when idle. */
-    private _labelEditor;
-    onCreated(): void;
-    onDestroyed(): void;
-    /** The editable facet label under a MODEL-space point, or null. */
-    private _labelAt;
     /**
-     * The diagram is SELECTED by its border (`EdgyFacetsElementModel`), but its
-     * three facet labels must still receive the double-click that renames them.
-     *
-     * Same seam Wardley uses, for the same reason: the pointer router asks the
-     * VIEW, so a framework declares its own gesture zones next to the code that
-     * draws them, and the model layer keeps a hit test that only says what a
-     * click SELECTS.
+     * A diagram is SELECTED by its border (`EdgyFacetsElementModel`), and the
+     * three facet labels widen that for the pointer — the base class' doing; this
+     * method only says where they are.
      */
-    includesPoint(x: number, y: number, options: PointTestOptions, host: EditorHost): boolean;
-    /** Double-click on a label → edit its text in place. */
-    private _onDblClick;
-    private _openLabelEditor;
-    private _closeLabelEditor;
+    protected labelAt(lx: number, ly: number, w: number, h: number): EditableBackgroundLabel | null;
 }
 /**
  * Resize gating: the resize handles are hidden unless `model.resizeEnabled` is

package/dist/element-view.js

@@ -1,40 +1,31 @@
-import { EdgelessCRUDIdentifier } from '@formicoidea/labre-core/blocks/surface';
-import { rotatePoint } from '@formicoidea/labre-core/global/gfx';
-import { GfxElementModelView, GfxViewInteractionExtension, } from '@formicoidea/labre-core/std/gfx';
+import { FrameworkBackgroundView } from '@formicoidea/labre-core/blocks/surface';
+import { GfxViewInteractionExtension } from '@formicoidea/labre-core/std/gfx';
 import { cropLabeledScale, refScale } from './consts.js';
-import { getEdgyLabelHits, hitTestEdgyLabel, } from './label-layout.js';
-export class EdgyView extends GfxElementModelView {
-    constructor() {
-        super(...arguments);
-        /** The in-place `<input>` used to edit a label, or null when idle. */
-        this._labelEditor = null;
-    }
+import { getEdgyLabelHits, hitTestEdgyLabel } from './label-layout.js';
+/**
+ * The EDGY facets diagram's view: the shared background gesture, aimed by this
+ * framework's own label layout.
+ *
+ * The three facet names are NOT declared in a `FrameworkBackgroundDef` — the
+ * diagram is a Venn figure fitted into a reference space, and its labels hang
+ * off the circles rather than off a plot — so the hit test stays here, mapped
+ * with the SAME fit the renderer used. Everything above it (where a
+ * double-click is allowed to land, the in-place `<input>`, the commit that
+ * refuses to write an untouched value) comes from
+ * {@link FrameworkBackgroundView}, which is where this diagram's own copy of it
+ * went — see issue #355.
+ */
+export class EdgyView extends FrameworkBackgroundView {
     static { this.type = 'edgy'; }
-    onCreated() {
-        super.onCreated();
-        this.on('dblclick', e => this._onDblClick(e));
-    }
-    onDestroyed() {
-        this._closeLabelEditor();
-        super.onDestroyed();
-    }
-    /** The editable facet label under a MODEL-space point, or null. */
-    _labelAt(mx, my) {
+    /**
+     * A diagram is SELECTED by its border (`EdgyFacetsElementModel`), and the
+     * three facet labels widen that for the pointer — the base class' doing; this
+     * method only says where they are.
+     */
+    labelAt(lx, ly, w, h) {
         // No labels shown → nothing to edit (and the cropped mapping differs).
         if (!this.model.showLabels)
             return null;
-        const [bx, by, w, h] = this.model.deserializedXYWH;
-        // Convert the model-space point into element-local coordinates, undoing the
-        // element rotation around its center.
-        let lx = mx - bx;
-        let ly = my - by;
-        const rot = this.model.rotate ?? 0;
-        if (rot) {
-            const center = [bx + w / 2, by + h / 2];
-            const [ux, uy] = rotatePoint([mx, my], center, -rot);
-            lx = ux - bx;
-            ly = uy - by;
-        }
         // Map element-local coords into the fixed reference space the labels live
         // in — with the SAME fit the renderer used (cropped or letterboxed).
         const { s, ox, oy } = this.model.cropToCircles
@@ -42,91 +33,11 @@ export class EdgyView extends GfxElementModelView {
             : refScale(w, h);
         const rx = (lx - ox) / s;
         const ry = (ly - oy) / s;
-        return hitTestEdgyLabel(getEdgyLabelHits(this.model), rx, ry);
-    }
-    /**
-     * The diagram is SELECTED by its border (`EdgyFacetsElementModel`), but its
-     * three facet labels must still receive the double-click that renames them.
-     *
-     * Same seam Wardley uses, for the same reason: the pointer router asks the
-     * VIEW, so a framework declares its own gesture zones next to the code that
-     * draws them, and the model layer keeps a hit test that only says what a
-     * click SELECTS.
-     */
-    includesPoint(x, y, options, host) {
-        if (super.includesPoint(x, y, options, host))
-            return true;
-        return this._labelAt(x, y) !== null;
-    }
-    /** Double-click on a label → edit its text in place. */
-    _onDblClick(e) {
-        if (this.model.isLocked())
-            return;
-        const [mx, my] = this.gfx.viewport.toModelCoord(e.x, e.y);
-        const hit = this._labelAt(mx, my);
+        const hit = hitTestEdgyLabel(getEdgyLabelHits(this.model), rx, ry);
         if (!hit)
-            return;
-        this._openLabelEditor(hit.field, e);
-    }
-    _openLabelEditor(field, e) {
-        this._closeLabelEditor();
-        const input = document.createElement('input');
-        input.value = String(this.model[field] ?? '');
-        Object.assign(input.style, {
-            position: 'fixed',
-            left: `${e.raw.clientX}px`,
-            top: `${e.raw.clientY}px`,
-            transform: 'translate(-50%, -50%)',
-            zIndex: '10000',
-            minWidth: '140px',
-            padding: '3px 8px',
-            font: '14px Inter, sans-serif',
-            color: 'var(--affine-text-primary-color, #1f2328)',
-            background: 'var(--affine-background-overlay-panel-color, #ffffff)',
-            border: '1px solid var(--affine-primary-color, #1e96eb)',
-            borderRadius: '6px',
-            boxShadow: 'var(--affine-shadow-2, 0 2px 8px rgba(0,0,0,0.18))',
-            outline: 'none',
-        });
-        document.body.append(input);
-        this._labelEditor = input;
-        // Mark the element as "editing" so the global edgeless key handlers
-        // (delete, escape, etc.) don't act on it while the user types.
-        this.gfx.selection.set({ elements: [this.model.id], editing: true });
-        input.focus();
-        input.select();
-        const commit = () => {
-            if (this._labelEditor !== input)
-                return;
-            const value = input.value;
-            this._closeLabelEditor();
-            this.gfx.std.store.captureSync();
-            this.gfx.std
-                .get(EdgelessCRUDIdentifier)
-                .updateElement(this.model.id, { [field]: value });
-        };
-        input.addEventListener('keydown', ev => {
-            ev.stopPropagation();
-            if (ev.key === 'Enter') {
-                ev.preventDefault();
-                commit();
-            }
-            else if (ev.key === 'Escape') {
-                ev.preventDefault();
-                this._closeLabelEditor();
-            }
-        });
-        input.addEventListener('blur', commit);
-    }
-    _closeLabelEditor() {
-        if (!this._labelEditor)
-            return;
-        const input = this._labelEditor;
-        this._labelEditor = null;
-        input.remove();
-        if (this.isConnected) {
-            this.gfx.selection.set({ elements: [this.model.id], editing: false });
-        }
+            return null;
+        // The facet names carry a hard default, so the drawn words ARE the prop.
+        return { prop: hit.field, text: String(this.model[hit.field] ?? '') };
     }
 }
 /**

package/dist/node/node-renderer.js

@@ -1,4 +1,4 @@
-import { ElementRendererExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { ElementRendererExtension, taggedPath2D, } from '@formicoidea/labre-core/blocks/surface';
 import { shape as shapeRenderer } from '@formicoidea/labre-core/gfx/shape';
 import { DefaultTheme } from '@formicoidea/labre-core/model';
 import { PERSON_GLYPH_PATHS, PERSON_GLYPH_VIEWBOX } from './consts.js';
@@ -33,7 +33,7 @@ export const edgyNode = (model, ctx, matrix, renderer, rc, bound) => {
     ctx.translate(-PERSON_GLYPH_VIEWBOX / 2, -PERSON_GLYPH_VIEWBOX / 2);
     ctx.fillStyle = color;
     for (const d of PERSON_GLYPH_PATHS) {
-        ctx.fill(new Path2D(d));
+        ctx.fill(taggedPath2D(d));
     }
 };
 export const EdgyNodeRendererExtension = ElementRendererExtension('edgyNode', edgyNode);

package/dist/templates/index.js

@@ -518,7 +518,7 @@ const ATTRS = 'width="100%" height="100%" viewBox="0 0 135 80" xmlns="http://www
  * `build` takes the OPTIONAL inserting editor: called with none, at module
  * load, for the English `content`; called again with the real `std` as
  * {@link Template.localize}, so the two builds read the very same layout and
- * differ only in the words a seed resolves to (`docs/adr/0016`).
+ * differ only in the words a seed resolves to (`docs/adr/0023`).
  */
 function tpl(name, preview, build, nameKey) {
     return {

package/dist/toolbar/config.d.ts

@@ -1,4 +1,4 @@
-import { type ChromeWording, type ToolbarContext } from '@formicoidea/labre-core/shared/services';
+import { type ChromeWording, type ToolbarContext, type ToolbarModuleConfig } from '@formicoidea/labre-core/shared/services';
 import { type TemplateResult } from 'lit';
 /** Every wording above, for `translations.ts`'s manifest contribution. */
 export declare const EDGY_TOOLBAR_WORDINGS: readonly ChromeWording[];
@@ -17,11 +17,6 @@ export declare const edgyToolbarConfig: {
         icon: TemplateResult;
         active(ctx: ToolbarContext): boolean;
         run(ctx: ToolbarContext): void;
-    }, {
-        id: string;
-        tooltipWording: ChromeWording;
-        icon: TemplateResult<1>;
-        run(ctx: ToolbarContext): void;
     }];
     readonly when: (ctx: ToolbarContext) => boolean;
 };
@@ -41,12 +36,11 @@ export declare const edgyBoardToolbarConfig: {
         icon: TemplateResult;
         active(ctx: ToolbarContext): boolean;
         run(ctx: ToolbarContext): void;
-    }, {
-        id: string;
-        tooltipWording: ChromeWording;
-        icon: TemplateResult<1>;
-        run(ctx: ToolbarContext): void;
     }];
     readonly when: (ctx: ToolbarContext) => boolean;
 };
 export declare const edgyBoardToolbarExtension: import("@formicoidea/labre-core/store").ExtensionType;
+export declare const edgyToolingToolbarConfig: ToolbarModuleConfig;
+export declare const edgyBoardToolingToolbarConfig: ToolbarModuleConfig;
+export declare const edgyToolingToolbarExtension: import("@formicoidea/labre-core/store").ExtensionType;
+export declare const edgyBoardToolingToolbarExtension: import("@formicoidea/labre-core/store").ExtensionType;

package/dist/toolbar/config.js

@@ -1,10 +1,8 @@
-import { EdgelessCRUDIdentifier } from '@formicoidea/labre-core/blocks/surface';
-import { createAutoLegend, dddLegendIcon } from '@formicoidea/labre-ddd-shared';
+import { EdgelessCRUDIdentifier, legendToolbarAction, validationToolbarConfig, } from '@formicoidea/labre-core/blocks/surface';
 import { EdgyBoardElementModel, EdgyFacetsElementModel, } from '@formicoidea/labre-core/model';
-import { BOARD_LEGEND_NOTATION, BOARD_RESIZE_TOGGLE, TelemetryProvider, ToolbarModuleExtension, } from '@formicoidea/labre-core/shared/services';
+import { BOARD_RESIZE_TOGGLE, ToolbarModuleExtension, } from '@formicoidea/labre-core/shared/services';
 import { BlockFlavourIdentifier } from '@formicoidea/labre-core/std';
 import { html } from 'lit';
-import { EDGY_AUTO_LEGEND } from '../legend.js';
 /** The two toolbar tooltips this file used to hard-code as English literals. */
 const FACET_LABELS_TOGGLE = [
     'com.labre.edgy.toolbar.facet-labels',
@@ -96,46 +94,12 @@ function booleanToggle(Model, id, tooltip, icon, prop) {
         },
     };
 }
-/**
- * The legend action, shared by the two EDGY backgrounds: both frame the same
- * notation, so both answer the same question — "what is actually drawn here" —
- * with the same table ({@link EDGY_AUTO_LEGEND}) and the same box.
- *
- * Registered ALWAYS-ON (`EdgyRenderViewExtension`) with the toggles it sits
- * next to: a legend is real, editable elements written into the document, so
- * generating one is authoring, not tooling a flag may take away
- * (`docs/adr/0009`).
- */
-function legendAction(Model, id) {
-    return {
-        id,
-        tooltipWording: BOARD_LEGEND_NOTATION,
-        icon: dddLegendIcon,
-        run(ctx) {
-            const background = ctx.getSurfaceModelsByType(Model)[0];
-            if (!background)
-                return;
-            createAutoLegend(ctx.std, background, EDGY_AUTO_LEGEND);
-            ctx.std.getOptional(TelemetryProvider)?.track('FrameworkLegendCreated', {
-                // The WIRE value from `frameworks.ts` (`telemetryKey`), which for EDGY
-                // happens to be the module id itself. Same field set as Wardley's and
-                // the three DDD legend buttons, so the four are comparable.
-                framework: 'edgy',
-                element: 'legend',
-                page: 'whiteboard editor',
-                segment: 'element toolbar',
-                module: 'edgy toolbar',
-            });
-        },
-    };
-}
 export const edgyToolbarConfig = {
     actions: [
         booleanToggle(EdgyFacetsElementModel, 'a.toggle-resize', BOARD_RESIZE_TOGGLE, ResizeIcon, 'resizeEnabled'),
         booleanToggle(EdgyFacetsElementModel, 'b.toggle-labels', FACET_LABELS_TOGGLE, LabelsIcon, 'showLabels'),
         // No spotlight toggle here: the hover spotlight is BOARD logic and lives on
         // the EDGY board toolbar below. The Venn only carries APPEARANCE (#195).
-        legendAction(EdgyFacetsElementModel, 'c.legend'),
     ],
     when: ctx => ctx.getSurfaceModelsByType(EdgyFacetsElementModel).length > 0,
 };
@@ -147,7 +111,6 @@ export const edgyBoardToolbarConfig = {
     actions: [
         booleanToggle(EdgyBoardElementModel, 'a.toggle-resize', BOARD_RESIZE_TOGGLE, ResizeIcon, 'resizeEnabled'),
         booleanToggle(EdgyBoardElementModel, 'b.toggle-spotlight', HOVER_SPOTLIGHT_TOGGLE, SpotlightIcon, 'spotlightEnabled'),
-        legendAction(EdgyBoardElementModel, 'c.legend'),
     ],
     when: ctx => ctx.getSurfaceModelsByType(EdgyBoardElementModel).length > 0,
 };
@@ -155,3 +118,55 @@ export const edgyBoardToolbarExtension = ToolbarModuleExtension({
     id: BlockFlavourIdentifier('affine:surface:edgyBoard'),
     config: edgyBoardToolbarConfig,
 });
+/**
+ * A background's flag-gated row, WHOLE: the legend button and the Validation
+ * dropdown, in ONE module — registered by `EdgyViewExtension` on the `custom:`
+ * flavour slot of each of the two frames.
+ *
+ * ## Why one module and not two
+ *
+ * `renderToolbar` merges exactly four slots per element and
+ * `ToolbarModuleExtension` binds by DI variant, so a second module claiming
+ * `custom:affine:surface:edgy` throws `DuplicateServiceDefinitionError` before
+ * the editor finishes setting up. The always-on module above holds the
+ * APPEARANCE toggles a stored board must keep; these two entries are gated by
+ * the same flag and appear together or not at all.
+ *
+ * ## Why the legend moved out of the always-on half
+ *
+ * It used to sit with the toggles, argued as authoring. `docs/adr/0026` (which
+ * amends `docs/adr/0009`) reverses that reading: GENERATING a legend is
+ * tooling — it is the framework telling you what its notation means — while the
+ * legend it wrote is content, made of plain shapes, text and this pack's own
+ * always-on renderers, and keeps being painted with the flag off.
+ *
+ * `c.legend` and not the factory's default `b.`: the sort is lexicographic and
+ * both frames already spend `a.` and `b.` on their toggles.
+ */
+function toolingConfig(Model) {
+    return {
+        actions: [
+            legendToolbarAction({
+                id: 'c.legend',
+                Model,
+                owner: 'edgy',
+                framework: 'edgy',
+            }),
+            // The generic dropdown, not an EDGY variant of it: the config names no
+            // framework — it reads the registered rules and profiles — so this is the
+            // very same object wardley, bpmn, the context map and C4 register.
+            ...validationToolbarConfig.actions,
+        ],
+        when: (ctx) => ctx.getSurfaceModelsByType(Model).length > 0,
+    };
+}
+export const edgyToolingToolbarConfig = toolingConfig(EdgyFacetsElementModel);
+export const edgyBoardToolingToolbarConfig = toolingConfig(EdgyBoardElementModel);
+export const edgyToolingToolbarExtension = ToolbarModuleExtension({
+    id: BlockFlavourIdentifier('custom:affine:surface:edgy'),
+    config: edgyToolingToolbarConfig,
+});
+export const edgyBoardToolingToolbarExtension = ToolbarModuleExtension({
+    id: BlockFlavourIdentifier('custom:affine:surface:edgyBoard'),
+    config: edgyBoardToolingToolbarConfig,
+});

package/dist/toolbar/edgy-senior-button.d.ts

@@ -10,6 +10,8 @@ export declare class EdgelessEdgySeniorButton extends EdgelessEdgySeniorButton_b
     enableActiveBackground: boolean;
     type: typeof EmptyTool;
     private _toggleMenu;
+    /** Lit while one of THIS framework's artefacts is armed. See the Wardley one. */
+    private get _armed();
     render(): import("lit-html").TemplateResult<1>;
 }
 export {};

package/dist/toolbar/edgy-senior-button.js

@@ -1,7 +1,7 @@
 import { DefaultTool } from '@formicoidea/labre-core/blocks/surface';
 import { EmptyTool } from '@formicoidea/labre-core/gfx/pointer';
 import { translateKey } from '@formicoidea/labre-core/shared/services';
-import { EdgelessToolbarToolMixin } from '@formicoidea/labre-core/widgets/edgeless-toolbar';
+import { armedArtefact, EdgelessToolbarToolMixin, } from '@formicoidea/labre-core/widgets/edgeless-toolbar';
 import { SignalWatcher } from '@formicoidea/labre-core/global/lit';
 import { css, html, LitElement } from 'lit';
 import { edgyToolbarIcon } from './icons.js';
@@ -72,6 +72,10 @@ export class EdgelessEdgySeniorButton extends EdgelessToolbarToolMixin(SignalWat
         const menu = this.createPopper('edgeless-edgy-menu', this);
         menu.element.edgeless = this.edgeless;
     }
+    /** Lit while one of THIS framework's artefacts is armed. See the Wardley one. */
+    get _armed() {
+        return armedArtefact(this.gfx)?.owner === 'edgy';
+    }
     render() {
         return html `<edgeless-toolbar-button
       class="edgy-button"
@@ -79,7 +83,7 @@ export class EdgelessEdgySeniorButton extends EdgelessToolbarToolMixin(SignalWat
             ? ''
             : translateKey(this.edgeless.std, 'com.labre.framework.edgy', 'EDGY')}
       .tooltipOffset=${4}
-      .active=${!!this.popper}
+      .active=${!!this.popper || this._armed}
       @click=${this._toggleMenu}
     >
       <div class="edgy-root">

package/dist/toolbar/node-config.d.ts

@@ -1,3 +1,4 @@
+import type { FrameworkPalette, NamedPalette } from '@formicoidea/labre-core/components/color-picker';
 import { type ChromeWording } from '@formicoidea/labre-core/shared/services';
 /**
  * The twelve EDGY swatches' own names, resolved by `resolvePaletteLabel`
@@ -23,4 +24,17 @@ export declare const EDGY_PALETTE_WORDING_ORGANISATION_LIGHT: ChromeWording;
 export declare const EDGY_PALETTE_WORDING_BRAND_LIGHT: ChromeWording;
 export declare const EDGY_PALETTE_WORDING_PRODUCT_LIGHT: ChromeWording;
 export declare const EDGY_PALETTE_WORDINGS: readonly ChromeWording[];
+/**
+ * From the default editor palette we keep ONLY the neutrals (greys, white,
+ * black, transparent) — the historical colours are dropped in favour of the
+ * EDGY swatches above.
+ */
+export declare const EDGY_PALETTE_LIST: NamedPalette[];
+/**
+ * EDGY's page of the colour pickers' carousel (`docs/adr/0027`) — the same
+ * list its node picker is seeded with, offered on every other picker too.
+ * Registered from the FLAG-GATED view extension: offering hues is tooling
+ * (`docs/adr/0009`).
+ */
+export declare const EDGY_FRAMEWORK_PALETTE: FrameworkPalette;
 export declare const edgyNodeToolbarExtension: import("@formicoidea/labre-core/store").ExtensionType;

package/dist/toolbar/node-config.js

@@ -142,10 +142,21 @@ const EDGY_PALETTES = [
  * black, transparent) — the historical colours are dropped in favour of the
  * EDGY swatches above.
  */
-const EDGY_PALETTE_LIST = [
+export const EDGY_PALETTE_LIST = [
     ...EDGY_PALETTES,
     ...neutralPalettes(),
 ];
+/**
+ * EDGY's page of the colour pickers' carousel (`docs/adr/0027`) — the same
+ * list its node picker is seeded with, offered on every other picker too.
+ * Registered from the FLAG-GATED view extension: offering hues is tooling
+ * (`docs/adr/0009`).
+ */
+export const EDGY_FRAMEWORK_PALETTE = {
+    framework: 'edgy',
+    labelWording: ['com.labre.framework.edgy', 'EDGY'],
+    palettes: EDGY_PALETTE_LIST,
+};
 /**
  * EDGY fill / stroke colour picker — identical to the shape one but seeded with
  * the EDGY palette swatches (`.palettes`).

package/dist/translations.js

@@ -1,6 +1,5 @@
 import { collectTranslationKeys, commandCategoryTranslationEntries, commandTranslationEntries, mergeTranslationEntries, } from '@formicoidea/labre-core/std';
-import { edgyCommands } from './commands.js';
-import { EDGY_LEGEND_CHROME_WORDINGS } from './legend.js';
+import { edgyCommands, EDGY_LEGEND_CHROME_WORDINGS } from './commands.js';
 import { EDGY_DYNAMIC_NODES, EDGY_DYNAMIC_VERBS, EDGY_ZONES, edgyElementLabel, edgyElementLabelKey, edgyVerbSeedKey, } from './metamodel.js';
 import { NODE_LABEL, nodeLabelKey } from './node/consts.js';
 import { EDGY_NUDGES } from './nudges.js';

package/dist/view.js

@@ -1,8 +1,8 @@
-import { QualityNudgeExtension, ReadingProfileExtension, SpotlightHostExtension, ValidationProfileExtension, ValidationRuleExtension, validationToolbarConfig, } from '@formicoidea/labre-core/blocks/surface';
-import { ToolbarModuleExtension } from '@formicoidea/labre-core/shared/services';
+import { QualityNudgeExtension, ReadingProfileExtension, SpotlightHostExtension, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { FrameworkPaletteExtension } from '@formicoidea/labre-core/components/color-picker';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { TemplateCategoryExtension } from '@formicoidea/labre-core/gfx/template';
-import { BlockFlavourIdentifier, CommandExtension } from '@formicoidea/labre-core/std';
+import { CommandExtension } from '@formicoidea/labre-core/std';
 import { RoleVocabularyExtension } from '@formicoidea/labre-core/std/gfx';
 import { edgyCommandIcons, edgyCommands } from './commands.js';
 import { effects } from './effects.js';
@@ -19,8 +19,8 @@ import { EdgyFacetsRendererExtension } from './element-renderer.js';
 import { EdgyInteraction, EdgyView } from './element-view.js';
 import { EdgyNodeRendererExtension } from './node/node-renderer.js';
 import { EdgyNodeView } from './node/node-view.js';
-import { edgyBoardToolbarExtension, edgyToolbarExtension, } from './toolbar/config.js';
-import { edgyNodeToolbarExtension } from './toolbar/node-config.js';
+import { edgyBoardToolbarExtension, edgyBoardToolingToolbarExtension, edgyToolbarExtension, edgyToolingToolbarExtension, } from './toolbar/config.js';
+import { EDGY_FRAMEWORK_PALETTE, edgyNodeToolbarExtension, } from './toolbar/node-config.js';
 import { edgySeniorTool } from './toolbar/senior-tool.js';
 /**
  * EDGY rendering — ALWAYS registered, independent of any flag. Disabling `edgy`
@@ -88,22 +88,17 @@ export class EdgyViewExtension extends ViewExtensionProvider {
             // including the two the PO deliberately kept out of `rules.ts` on
             // 26/08/2026 (see `./nudges.ts`).
             context.register(QualityNudgeExtension(EDGY_NUDGES));
-            // The Validation dropdown on a selected background's contextual toolbar.
-            // A SECOND module on the same element, through the `custom:` flavour slot
-            // (the pattern `gfx/wardley` uses on its map): the rendering toolbars are
-            // registered always-on because a stored board must keep its toggles,
-            // while choosing how hard to check it is tooling and belongs here. The
-            // config itself names no framework — it reads roles and profiles — so
-            // BOTH EDGY frames register the very same object.
-            for (const flavour of [
-                'custom:affine:surface:edgy',
-                'custom:affine:surface:edgyBoard',
-            ]) {
-                context.register(ToolbarModuleExtension({
-                    id: BlockFlavourIdentifier(flavour),
-                    config: validationToolbarConfig,
-                }));
-            }
+            // The LEGEND button and the Validation dropdown on a selected
+            // background's contextual toolbar. A SECOND module on the same element,
+            // through the `custom:` flavour slot (the pattern `gfx/wardley` uses on
+            // its map): the rendering toolbars are registered always-on because a
+            // stored board must keep its appearance toggles, while asking the
+            // framework what its notation means, and choosing how hard to check the
+            // board, are both tooling and belong here (`docs/adr/0026`). One module
+            // per frame and not one shared object, because the button has to know
+            // WHICH background it is documenting.
+            context.register(edgyToolingToolbarExtension);
+            context.register(edgyBoardToolingToolbarExtension);
             // The resolver that turns a hand-drawn `edgy:relation` into the verb the
             // metamodel gives its two ends. It belongs HERE and not in the always-on
             // extension above, and the test is the one `docs/adr/0009` asks: does it
@@ -122,6 +117,11 @@ export class EdgyViewExtension extends ViewExtensionProvider {
             // profile, so it goes with the flag without either side naming the other.
             context.register(ReadingProfileExtension(EDGY_READING));
             context.register(edgySeniorTool);
+            // EDGY's page of the colour pickers' carousel (`docs/adr/0027`). Here,
+            // beside the senior tool, because offering hues is TOOLING — the colours
+            // already painted on a stored board are content and do not move
+            // (`docs/adr/0009`).
+            context.register(FrameworkPaletteExtension(EDGY_FRAMEWORK_PALETTE));
             // The Templates-panel category — tooling, so it goes with the flag (#244).
             context.register(TemplateCategoryExtension(edgyTemplateCategory));
             // The eight EDGY commands: the sub-menu renders them, Settings ›

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-edgy",
   "description": "Labre edgy framework for @formicoidea/labre-core.",
-  "version": "0.41.0",
+  "version": "0.42.0",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -31,8 +31,7 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.41.0",
-    "@formicoidea/labre-ddd-shared": "0.41.0",
+    "@formicoidea/labre-core": "0.42.0",
     "@preact/signals-core": "^1.8.0",
     "lit": "^3.2.0",
     "yjs": "^13.6.21"

package/dist/legend.d.ts

@@ -1,11 +0,0 @@
-import { type AutoLegendSpec } from '@formicoidea/labre-ddd-shared';
-import { type ChromeWording } from '@formicoidea/labre-core/shared/services';
-/**
- * The two section titles above that are this framework's OWN word rather than
- * a role's — `titleKey` reuses a role's key where the section says a role's
- * name (the facets, the intersections), but "Base elements" and "Relations"
- * name a GROUPING of roles, so each mints a key of its own. For
- * `translations.ts`'s manifest.
- */
-export declare const EDGY_LEGEND_CHROME_WORDINGS: readonly ChromeWording[];
-export declare const EDGY_AUTO_LEGEND: AutoLegendSpec;

package/dist/legend.js

@@ -1,133 +0,0 @@
-import { roleLabel, } from '@formicoidea/labre-ddd-shared';
-import { BOARD_LEGEND_TITLE, } from '@formicoidea/labre-core/shared/services';
-import { EDGY_DYNAMIC_NODES, EDGY_ZONE_FILL, EDGY_ZONES, edgyElementLabel, edgyElementLabelKey, } from './metamodel.js';
-import { NODE_FILL, NODE_STROKE } from './node/consts.js';
-import { EDGY_ROLE, EDGY_ROLES } from './roles.js';
-/**
- * What an EDGY background's automatic legend can say — a TABLE, and nothing
- * else: the scan, the placement and the box are `createAutoLegend`'s job, the
- * same generic the three DDD backgrounds were given
- * (`@labre/affine-gfx-ddd-shared`, `shared/legend-auto.ts`). EDGY takes a
- * dependency on that package for the generic and the box prefab alone; moving
- * them to a neutral home would be the tidier answer and is not worth the churn
- * of this fix.
- *
- * Every row is DERIVED — from the metamodel (`./metamodel.ts`: which elements
- * exist, which zone each belongs to, what colour that zone is drawn in) and
- * from the role vocabulary's own labels (`./roles.ts`). Nothing here is
- * restated: a thirteenth element added to the metamodel gets its legend row the
- * same way it gets its role, with no edit to this file.
- *
- * ## The order
- *
- * By ZONE, and the order of the table carries it: the three facets first
- * (Identity, Architecture, Experience), then the three intersections in one
- * section, then the four base elements, then the relations — which is the
- * reading order of {@link EDGY_ZONES} and, before it, of the Venn itself.
- */
-/** One row per official element of `zone`, in the metamodel's own order. */
-function zoneEntries(zone) {
-    return Object.entries(EDGY_DYNAMIC_NODES)
-        .filter(([, node]) => node.zone === zone)
-        .map(([name]) => ({
-        role: EDGY_ROLE[name],
-        row: {
-            swatch: 'square',
-            // The zone's fill, which IS what the diagram paints the element with.
-            color: EDGY_ZONE_FILL[zone],
-            label: roleLabel(EDGY_ROLES, EDGY_ROLE[name]),
-        },
-    }));
-}
-/**
- * A facet's section title says the facet's own name, so it reuses the key the
- * metamodel's seeds already carry (`edgyElementLabelKey`): the legend and the
- * facets diagram say "Identity" with one key, not two.
- */
-const FACET_SECTIONS = EDGY_ZONES.filter(zone => zone.group === 'facet').map(zone => ({
-    title: edgyElementLabel(zone.id),
-    titleKey: edgyElementLabelKey(zone.id),
-    entries: zoneEntries(zone.id),
-}));
-/**
- * The three intersection elements in ONE section: Organisation, Product and
- * Brand are not three facets, they are the three lenses between them, and the
- * diagram says so by drawing them in the overlaps. Each keeps its own colour.
- */
-const INTERSECTIONS_SECTION = {
-    title: 'Intersections',
-    titleKey: 'com.labre.edgy.seed.intersections-title',
-    entries: EDGY_ZONES.filter(zone => zone.group === 'intersection').flatMap(zone => zoneEntries(zone.id)),
-};
-/**
- * The four base elements, listed only when one is on the board BARE — an
- * element the user dropped from the toolbox and left as a People, an Outcome,
- * an Object or an Activity, without saying which of the twelve it is. White,
- * because that is the fill the palette gives them (`node/consts.ts`).
- *
- * `exact` is what makes "bare" true. Detection is otherwise an ancestor walk,
- * and the twelve official elements specialise these four — Content is an
- * object, Story an activity — so an "Object" row would appear on a board
- * carrying nothing but Contents, keyed to a white swatch that is drawn nowhere
- * on it. The relation entry below keeps the walk, because there the parent row
- * IS the fair summary: a board carrying `edgy:expresses` carries a relation.
- */
-const BASE_SECTION = {
-    title: 'Base elements',
-    titleKey: 'com.labre.edgy.legend.section.base-elements',
-    entries: ['people', 'outcome', 'object', 'activity'].map(kind => ({
-        role: EDGY_ROLE[kind],
-        exact: true,
-        row: {
-            swatch: 'square',
-            color: NODE_FILL,
-            label: roleLabel(EDGY_ROLES, EDGY_ROLE[kind]),
-        },
-    })),
-};
-/**
- * ONE row for the whole relation family, keyed on the PARENT role: a board
- * carrying "content expresses purpose" carries `edgy:expresses`, which is a
- * relation, and that is all the legend has to say. Twenty-two rows naming the
- * verbs would restate the metamodel rather than document the drawing — and the
- * verb travels on the link itself, visible, where it belongs.
- */
-const RELATIONS_SECTION = {
-    title: 'Relations',
-    titleKey: 'com.labre.edgy.legend.section.relations',
-    entries: [
-        {
-            role: EDGY_ROLE.relation,
-            row: {
-                swatch: 'line',
-                // The stroke `activateEdgyRelation` arms the connector tool with.
-                color: NODE_STROKE,
-                label: roleLabel(EDGY_ROLES, EDGY_ROLE.relation),
-            },
-        },
-    ],
-};
-/**
- * The two section titles above that are this framework's OWN word rather than
- * a role's — `titleKey` reuses a role's key where the section says a role's
- * name (the facets, the intersections), but "Base elements" and "Relations"
- * name a GROUPING of roles, so each mints a key of its own. For
- * `translations.ts`'s manifest.
- */
-export const EDGY_LEGEND_CHROME_WORDINGS = [
-    ['com.labre.edgy.legend.section.base-elements', 'Base elements'],
-    ['com.labre.edgy.legend.section.relations', 'Relations'],
-];
-export const EDGY_AUTO_LEGEND = {
-    // The shared DDD auto-legend box's own generic chrome, resolved through
-    // the same key every board that has one reuses — see `AutoLegendSpec.title`.
-    title: BOARD_LEGEND_TITLE[1],
-    titleKey: BOARD_LEGEND_TITLE[0],
-    roles: EDGY_ROLES,
-    sections: [
-        ...FACET_SECTIONS,
-        INTERSECTIONS_SECTION,
-        BASE_SECTION,
-        RELATIONS_SECTION,
-    ],
-};