@formicoidea/labre-framework-ddd-core-domain 0.41.0 → 0.43.1

package/dist/view.js

@@ -1,4 +1,5 @@
-import { morphToolbarConfig, QualityNudgeExtension, ReadingProfileExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { morphToolbarConfig, QualityNudgeExtension, ReadingProfileExtension, 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 { ToolbarModuleExtension, toolbarModuleKey, } from '@formicoidea/labre-core/shared/services';
 import { TemplateCategoryExtension } from '@formicoidea/labre-core/gfx/template';
@@ -8,7 +9,7 @@ import { coreDomainCommandIcons, coreDomainCommands } from './commands.js';
 import { coreDomainTemplateCategory } from './templates.js';
 import { CoreDomainRendererExtension } from './core-domain/element-renderer.js';
 import { CoreDomainInteraction, CoreDomainView, } from './core-domain/element-view.js';
-import { coreDomainToolbarExtension } from './core-domain/toolbar-config.js';
+import { coreDomainChartToolingToolbarConfig } from './core-domain/toolbar-config.js';
 import { coreDomainEffects } from './effects.js';
 import { CORE_DOMAIN_MORPH_SPEC } from './morph.js';
 import { CORE_DOMAIN_NUDGES } from './nudges.js';
@@ -16,13 +17,17 @@ import { CORE_DOMAIN_PROFILES } from './profiles.js';
 import { CORE_DOMAIN_READINGS } from './reading.js';
 import { CORE_DOMAIN_ROLES } from './roles.js';
 import { CORE_DOMAIN_RULES } from './rules.js';
+import { CORE_DOMAIN_FRAMEWORK_PALETTE } from './toolbar/palette.js';
 import { coreDomainSeniorTool } from './toolbar/senior-tool.js';
 /**
  * Core Domain Chart rendering — ALWAYS registered, independent of any flag.
- * Disabling `ddd-core-domain` hides only the senior toolbar button (see
+ * Disabling `ddd-core-domain` hides only the tooling (see
  * {@link DddCoreDomainViewExtension}); placed `coreDomain` elements must still
- * paint, stay selectable, and keep their contextual toolbar, and Templates-
- * panel insertion must still render them.
+ * paint, stay selectable and stay movable, and Templates-panel insertion must
+ * still render them.
+ *
+ * The chart claims no always-on toolbar module: the legend button was its only
+ * contextual entry and it moved to the gated half (`docs/adr/0026`).
  */
 export class DddCoreDomainRenderViewExtension extends ViewExtensionProvider {
     constructor() {
@@ -42,7 +47,6 @@ export class DddCoreDomainRenderViewExtension extends ViewExtensionProvider {
         context.register(RoleVocabularyExtension(CORE_DOMAIN_ROLES));
         if (this.isEdgeless(context.scope)) {
             context.register(CoreDomainInteraction);
-            context.register(coreDomainToolbarExtension);
         }
     }
 }
@@ -68,16 +72,13 @@ export class DddCoreDomainViewExtension extends ViewExtensionProvider {
             context.register(ValidationRuleExtension(CORE_DOMAIN_RULES));
             context.register(ValidationProfileExtension(CORE_DOMAIN_PROFILES));
             context.register(QualityNudgeExtension(CORE_DOMAIN_NUDGES));
-            // The Validation dropdown on a selected chart's contextual toolbar. A
-            // SECOND module on the same element, through the `custom:` flavour slot:
-            // `coreDomainToolbarExtension` is registered always-on because a stored
-            // chart must keep its legend action, while choosing how hard to check it
-            // is tooling and belongs here. The config itself names no framework — it
-            // reads roles and profiles — so it is the very same object Wardley
-            // registers on its own flavour.
+            // The chart's WHOLE contextual row — the Legend button and the Validation
+            // dropdown, merged into ONE module because a flavour may carry exactly one
+            // (`core-domain/toolbar-config.ts`). Both are tooling: with the flag off a
+            // stored chart keeps everything drawn on it and simply offers no button.
             context.register(ToolbarModuleExtension({
                 id: BlockFlavourIdentifier('custom:affine:surface:coreDomain'),
-                config: validationToolbarConfig,
+                config: coreDomainChartToolingToolbarConfig,
             }));
             // The reversed reading (MF3): what the chart says about an artefact, on
             // demand. Two profiles, because the vocabulary has two disjoint node
@@ -88,6 +89,11 @@ export class DddCoreDomainViewExtension extends ViewExtensionProvider {
                 context.register(ReadingProfileExtension(reading));
             }
             context.register(coreDomainSeniorTool);
+            // The Core Domain Chart'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 chart are content
+            // and do not move (`docs/adr/0009`).
+            context.register(FrameworkPaletteExtension(CORE_DOMAIN_FRAMEWORK_PALETTE));
             // The Templates-panel category, gated by this framework's own flag like
             // every other framework's: a template is tooling (`docs/adr/0009`), and it
             // is DERIVED from this package's commands, so it registers where they do.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-ddd-core-domain",
   "description": "Labre ddd-core-domain framework for @formicoidea/labre-core.",
-  "version": "0.41.0",
+  "version": "0.43.1",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -31,8 +31,8 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.41.0",
-    "@formicoidea/labre-ddd-shared": "0.41.0",
+    "@formicoidea/labre-core": "0.43.1",
+    "@formicoidea/labre-ddd-shared": "0.43.1",
     "lit": "^3.2.0"
   }
 }

package/dist/core-domain/legend.d.ts

@@ -1,29 +0,0 @@
-import { type AutoLegendSpec } from '@formicoidea/labre-ddd-shared';
-/**
- * What the Core Domain Chart's automatic legend can say — a TABLE, and nothing
- * else: the scan, the placement and the box are `createAutoLegend`'s job.
- *
- * Every row is DERIVED from the presets the palette draws its dots with
- * ({@link CD_SUBDOMAINS}) and from the role vocabulary's own labels, never
- * restated — which also keeps this table and `core-domain.off-legend-colour`
- * naming the same five colours by construction.
- *
- * ## What changed
- *
- * The chart's legend button predates roles: until now it scanned the perimeter
- * for FILL COLOURS, which is why it fell back to the full notation when it
- * recognised nothing. Detection is now by role, like every other reader of the
- * board, with one consequence worth stating: a chart on which nothing is
- * recognised yields a legend box with a title and no rows, rather than the whole
- * notation. That is Wardley's behaviour and the honest one — a legend lists what
- * is drawn, not what could have been.
- *
- * The **Team Topologies markers** were the casualty of that change for one
- * release: `addMarker` stamped no role, so a chart covered in them produced a
- * legend that mentioned none (PO recette, 26/08/2026). They now carry
- * `core-domain:marker-*` and their section is here, derived from
- * `TEAM_TOPOLOGIES` like everything else — swatch, letter and colour from the
- * preset the palette draws with, wording from the vocabulary that names the
- * role.
- */
-export declare const CORE_DOMAIN_AUTO_LEGEND: AutoLegendSpec;

package/dist/core-domain/legend.js

@@ -1,84 +0,0 @@
-import { CD_SUBDOMAINS, MOVEMENT_COLOR, roleLabel, TEAM_TOPOLOGIES, } from '@formicoidea/labre-ddd-shared';
-import { BOARD_LEGEND_TITLE } from '@formicoidea/labre-core/shared/services';
-import { CORE_DOMAIN_ROLE, CORE_DOMAIN_ROLES } from '../roles.js';
-import { CORE_DOMAIN_SEED_LEGEND_MOVEMENT, CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS, CORE_DOMAIN_SEED_LEGEND_TEAM_MODES, } from '../translations.js';
-/**
- * What the Core Domain Chart's automatic legend can say — a TABLE, and nothing
- * else: the scan, the placement and the box are `createAutoLegend`'s job.
- *
- * Every row is DERIVED from the presets the palette draws its dots with
- * ({@link CD_SUBDOMAINS}) and from the role vocabulary's own labels, never
- * restated — which also keeps this table and `core-domain.off-legend-colour`
- * naming the same five colours by construction.
- *
- * ## What changed
- *
- * The chart's legend button predates roles: until now it scanned the perimeter
- * for FILL COLOURS, which is why it fell back to the full notation when it
- * recognised nothing. Detection is now by role, like every other reader of the
- * board, with one consequence worth stating: a chart on which nothing is
- * recognised yields a legend box with a title and no rows, rather than the whole
- * notation. That is Wardley's behaviour and the honest one — a legend lists what
- * is drawn, not what could have been.
- *
- * The **Team Topologies markers** were the casualty of that change for one
- * release: `addMarker` stamped no role, so a chart covered in them produced a
- * legend that mentioned none (PO recette, 26/08/2026). They now carry
- * `core-domain:marker-*` and their section is here, derived from
- * `TEAM_TOPOLOGIES` like everything else — swatch, letter and colour from the
- * preset the palette draws with, wording from the vocabulary that names the
- * role.
- */
-export const CORE_DOMAIN_AUTO_LEGEND = {
-    title: BOARD_LEGEND_TITLE[1],
-    titleKey: BOARD_LEGEND_TITLE[0],
-    roles: CORE_DOMAIN_ROLES,
-    sections: [
-        {
-            title: CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS[1],
-            titleKey: CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS[0],
-            entries: CD_SUBDOMAINS.map(preset => ({
-                role: CORE_DOMAIN_ROLE[preset.kind],
-                row: {
-                    swatch: 'dot',
-                    color: preset.fill,
-                    label: preset.label,
-                },
-            })),
-        },
-        {
-            // The letter is what identifies a marker on the chart — the squares are
-            // three colours a reader has no key to — so the legend shows the same
-            // square with the same letter in it, which is what `LegendRow.letter`
-            // exists for.
-            title: CORE_DOMAIN_SEED_LEGEND_TEAM_MODES[1],
-            titleKey: CORE_DOMAIN_SEED_LEGEND_TEAM_MODES[0],
-            entries: TEAM_TOPOLOGIES.map(preset => ({
-                role: CORE_DOMAIN_ROLE[preset.kind],
-                row: {
-                    swatch: 'square',
-                    color: preset.fill,
-                    letter: preset.letter,
-                    label: roleLabel(CORE_DOMAIN_ROLES, CORE_DOMAIN_ROLE[preset.kind]),
-                },
-            })),
-        },
-        {
-            title: CORE_DOMAIN_SEED_LEGEND_MOVEMENT[1],
-            titleKey: CORE_DOMAIN_SEED_LEGEND_MOVEMENT[0],
-            entries: [
-                {
-                    role: CORE_DOMAIN_ROLE.movement,
-                    row: {
-                        swatch: 'line',
-                        // The style `activateMovement` arms the connector tool with: a red
-                        // dashed line.
-                        color: MOVEMENT_COLOR,
-                        dashed: true,
-                        label: roleLabel(CORE_DOMAIN_ROLES, CORE_DOMAIN_ROLE.movement),
-                    },
-                },
-            ],
-        },
-    ],
-};