@owlmeans/planning 0.1.18-rc.27 → 0.1.18-rc.28

package/README.md

@@ -9,7 +9,7 @@ the executor with `@owlmeans/server-planning` and reads remotely with `@owlmeans
 ## Installation
 
 ```sh
-bun add @owlmeans/planning@^0.1.18-rc.27 ajv ajv-formats
+bun add @owlmeans/planning@^0.1.18-rc.28 ajv ajv-formats
 ```
 
 ## Concepts

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/planning",
-  "version": "0.1.18-rc.27",
-  "generatedAt": "2026-10-15T10:20:01.299Z",
+  "version": "0.1.18-rc.28",
+  "generatedAt": "2026-10-16T18:05:19.005Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/planning/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/planning
 
 **Layer:** Cross-cutting domain
-**Install:** `"@owlmeans/planning": "^0.1.18-rc.27"` in `dependencies` (`ajv` and `ajv-formats` are peers)
+**Install:** `"@owlmeans/planning": "^0.1.18-rc.28"` in `dependencies` (`ajv` and `ajv-formats` are peers)
 
 The contracts of project planning: record shapes, schemas, refusals, the protocol tree, the pure
 fold and the models. No database, no fastify, no React. The executor, the plugin registry, the
@@ -144,10 +144,15 @@ excess-property check catches it — keep the literal typed.
 - A project type lists `cardTypes` (and `projectTypes` for nesting) its children may have;
   `scopedCardTypes: true` also admits card types defined as data (below).
 - `overridable: true` on a code type or flow opens it to a data-defined override.
-- `tone` / `icon` (type, flow) and `tone` (status) — PRESENTATION hints, free text of at most 64
-  characters: the colour family and the icon name an application marks the type's cards, the flow
-  or the status with. The package neither validates nor renders them; an application maps them
-  onto its own closed palette and icon set and falls back for an unknown value.
+- `tone` / `icon` (type, flow) and `tone` (status) — PRESENTATION hints the package stores as free
+  text of at most 64 characters, neither validating nor rendering them. Their standard values and
+  their standard editor and renderer are `@owlmeans/web-panel/picker`: `tone` a palette key
+  (`PICKER_COLOR_KEYS` — red … graphite, 24) or a lowercase `#rrggbb` when the editor allows custom
+  colours, `icon` a kebab-case lucide name of its catalogue (`PICKER_ICON_NAMES`). A person edits a
+  type's or a flow's mark with `IconColorPicker` and shows it with `IconTile` / `ColorDot`; a
+  status's `tone` usually names a meaning the application's own palette maps (`ColorPicker` with
+  `colors`). An unknown value renders the picker's fallback (`slate`, `circle`); server code and
+  seeds read the data React-free from `@owlmeans/web-panel/picker/vocabulary`.
 
 ## Data-defined types and flows
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/planning",
-  "version": "0.1.18-rc.27",
+  "version": "0.1.18-rc.28",
   "license": "MIT",
   "description": "Runtime-free project-planning contracts — the workcard super type, projects, specifications, typed relationships, status flows with three intrinsic states, the transition event and its pure fold, the schema registry, the models and the protocol tree.",
   "type": "module",