@wildo-ai/platform-core-shared 1.1.3 → 1.1.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wildo-ai/platform-core-shared",
-  "version": "1.1.3",
+  "version": "1.1.5",
   "license": "SEE LICENSE IN LICENSE",
   "description": "Todo app specific models and types",
   "author": "Wildo AI",
@@ -30,20 +30,11 @@
     "test:watch": "vitest"
   },
   "dependencies": {
-    "@wildo-ai/saas-models": "1.1.3",
-    "@wildo-ai/presets-components-models": "1.1.3",
-    "@wildo-ai/zod-decorators": "1.1.3"
+    "@wildo-ai/saas-models": "1.1.5",
+    "@wildo-ai/presets-components-models": "1.1.5",
+    "@wildo-ai/zod-decorators": "1.1.5"
   },
   "peerDependencies": {
-    "big.js": "^6.2.2",
-    "date-fns": "^4.1.0",
-    "inversify": "^8.1.0",
-    "jsonwebtoken": "^9.0.2",
-    "lodash": "^4.17.23",
-    "mime": "^4.0.1",
-    "reflect-metadata": "^0.2.2",
-    "ufo": "^1.6.3",
-    "yaml": "^2.3.4",
     "zod": "^4.3.6"
   },
   "devDependencies": {

package/dist/esm/workbench/workbench-creation-board.custom.shared.schemas.js

@@ -1,86 +0,0 @@
-/**
- * The application-creation board's identity, shared because THREE packages must agree on it.
- *
- * - the workbench declares the composite view under {@link WORKBENCH_CREATION_BOARD_VIEW_REF} and
- *   renders one `<Section>` per {@link WorkbenchCreationBoardSection};
- * - the companion authors the labels the view resolves, keyed by exactly those refs;
- * - and neither can see the other's source.
- *
- * Three string literals in three packages compile perfectly and fail at runtime as a blank sidebar
- * row and headless sections — `tCompositeView` and `tCompositeViewSection` answer the EMPTY STRING
- * for a missing key rather than echoing it, so nothing reports the drift. That is the same failure
- * the workbench's two resource launchers shipped with, and the same reason their vocabulary lives
- * here rather than on either side.
- *
- * This carries NO React and NO Node: it is a vocabulary, which is what makes it importable by a
- * browser bundle and by a daemon at once.
- */
-/**
- * The view's `ref` — the composite-view key, the launcher target, and the `/composite/<ref>` route.
- *
- * It MUST NOT contain a dot. The label lookup path is `composite_views.<translationRef>.<key>` and
- * BOTH readers — the backend's key filter and the frontend's `t` — split that whole path on `.` and
- * walk it segment by segment. A dotted ref therefore nests its labels one level deeper than anything
- * that reads them expects, and the failure is silent: `tCompositeView` answers the empty string.
- */
-export const WORKBENCH_CREATION_BOARD_VIEW_REF = 'creation-board';
-/**
- * The label PATH the view's title and description hang off — `composite_views.<this>.title`.
- *
- * DERIVED by the engine's `buildApplicationViewTranslationRef` (`app.<ref>`), not chosen here. It is
- * restated because the companion cannot import a frontend package to compute it, and the workbench's
- * own test asserts this constant against the engine's derivation — so the copy cannot drift silently
- * from the function that actually produces it at runtime.
- *
- * A DOT PATH, not an object key. The label file nests `app` and then the ref; a single
- * `'app.creation-board'` property is unreachable from either reader. Measured 2026-08-31, after a
- * flat key made the board's title, its six section headings and its sidebar row all render empty with
- * nothing reporting it.
- */
-export const WORKBENCH_CREATION_BOARD_TRANSLATION_REF = `app.${WORKBENCH_CREATION_BOARD_VIEW_REF}`;
-/**
- * The board's sections, in the order they are read.
- *
- * The order is a decision, not a listing: a playbook run lands families, which make build-plan tasks
- * ready, which the coding lane executes, which the write register records. Reading them in that order
- * is reading the loop. The evidence section is LAST and always visible rather than behind a tab,
- * because it is the undo that sits in front of every dispatch button above it.
- *
- * The governance-facts section sits between the executions and the evidence: it is the point in the
- * loop where derivation stops and a person decides, and it belongs after everything a machine can do
- * for them rather than before it — a creator answering it first would be answering questions the
- * accepted specifications have not yet made concrete.
- */
-export var WorkbenchCreationBoardSection;
-(function (WorkbenchCreationBoardSection) {
-    /** Every compiled playbook and whether it can run right now, with the reasons it cannot. */
-    WorkbenchCreationBoardSection["PLAYBOOKS"] = "playbooks";
-    /** What is running in the companion process, and what died leaving a resumable checkpoint. */
-    WorkbenchCreationBoardSection["RUNS"] = "runs";
-    /** The next ready build-plan task and the exact paths it may and may not write. */
-    WorkbenchCreationBoardSection["BUILD_PLAN"] = "build-plan";
-    /** Whether the coding agent is registered, and whether a run holds the workspace mutation lock. */
-    WorkbenchCreationBoardSection["CODING_LANE"] = "coding-lane";
-    /** The actor and flow executions the control plane holds, and the tasks they created. */
-    WorkbenchCreationBoardSection["EXECUTIONS"] = "executions";
-    /**
-     * The governed-document facts only a PERSON may establish — a creator decision or a qualified
-     * review — and the file their answers land in (#192).
-     *
-     * Its own section rather than a page of the playbook lane, because it is the one place on this
-     * board where a HUMAN is the authority. Everything above dispatches derivation; this collects
-     * decisions no derivation may make, and its answers land in `document-facts-authored`, a family no
-     * producer writes.
-     */
-    WorkbenchCreationBoardSection["GOVERNANCE_FACTS"] = "governance-facts";
-    /** What each run wrote, with its revert, and the execution traces behind it. */
-    WorkbenchCreationBoardSection["EVIDENCE"] = "evidence";
-})(WorkbenchCreationBoardSection || (WorkbenchCreationBoardSection = {}));
-/**
- * The section refs in render order.
- *
- * `Object.values` on a string enum preserves declaration order, so this IS the enum rather than a
- * second list beside it — the shape that would let the two disagree.
- */
-export const WORKBENCH_CREATION_BOARD_SECTION_REFS = Object.values(WorkbenchCreationBoardSection);
-//# sourceMappingURL=workbench-creation-board.custom.shared.schemas.js.map