@open-mercato/cli 0.10.1-develop.7783.1.e04ffd226c → 0.10.1-develop.7784.1.80225b38e4

package/dist/agentic/guides/modules/staff/index.md

@@ -1,5 +1,5 @@
 # staff — module facts (generated, do not edit)
-<!-- generated from @open-mercato/core 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/core 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/core/src/modules/staff
 
 ## Sections

package/dist/agentic/guides/modules/storage_s3/index.md

@@ -1,5 +1,5 @@
 # storage_s3 — module facts (generated, do not edit)
-<!-- generated from @open-mercato/storage-s3 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/storage-s3 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/storage-s3/src/modules/storage_s3
 
 ## Sections

package/dist/agentic/guides/modules/sync_akeneo/index.md

@@ -1,5 +1,5 @@
 # sync_akeneo — module facts (generated, do not edit)
-<!-- generated from @open-mercato/sync-akeneo 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/sync-akeneo 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/sync-akeneo/src/modules/sync_akeneo
 
 ## Sections

package/dist/agentic/guides/modules/sync_excel/index.md

@@ -1,5 +1,5 @@
 # sync_excel — module facts (generated, do not edit)
-<!-- generated from @open-mercato/core 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/core 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/core/src/modules/sync_excel
 
 ## Sections

package/dist/agentic/guides/modules/system_status_overlays/index.md

@@ -1,5 +1,5 @@
 # system_status_overlays — module facts (generated, do not edit)
-<!-- generated from @open-mercato/enterprise 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/enterprise 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/enterprise/src/modules/system_status_overlays
 
 ## Sections

package/dist/agentic/guides/modules/telemetry/index.md

@@ -1,5 +1,5 @@
 # telemetry — module facts (generated, do not edit)
-<!-- generated from @open-mercato/telemetry 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/telemetry 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/telemetry/src/modules/telemetry
 
 ## Sections

package/dist/agentic/guides/modules/tillio/index.md

@@ -1,5 +1,5 @@
 # tillio — module facts (generated, do not edit)
-<!-- generated from @open-mercato/tillio 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/tillio 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/tillio/src/modules/tillio
 
 ## Sections

package/dist/agentic/guides/modules/translations/index.md

@@ -1,5 +1,5 @@
 # translations — module facts (generated, do not edit)
-<!-- generated from @open-mercato/core 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/core 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/core/src/modules/translations
 
 ## Sections

package/dist/agentic/guides/modules/warranty_claims/index.md

@@ -1,5 +1,5 @@
 # warranty_claims — module facts (generated, do not edit)
-<!-- generated from @open-mercato/core 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/core 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/core/src/modules/warranty_claims
 
 ## Sections

package/dist/agentic/guides/modules/webhooks/index.md

@@ -1,5 +1,5 @@
 # webhooks — module facts (generated, do not edit)
-<!-- generated from @open-mercato/webhooks 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/webhooks 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/webhooks/src/modules/webhooks
 
 ## Sections

package/dist/agentic/guides/modules/wms/index.md

@@ -1,5 +1,5 @@
 # wms — module facts (generated, do not edit)
-<!-- generated from @open-mercato/core 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/core 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/core/src/modules/wms
 
 ## Sections

package/dist/agentic/guides/modules/workflows/index.md

@@ -1,5 +1,5 @@
 # workflows — module facts (generated, do not edit)
-<!-- generated from @open-mercato/core 0.10.1-develop.7783.1.e04ffd226c; core 0.10.1-develop.7783.1.e04ffd226c — R1 staleness stamp -->
+<!-- generated from @open-mercato/core 0.10.1-develop.7784.1.80225b38e4; core 0.10.1-develop.7784.1.80225b38e4 — R1 staleness stamp -->
 Source root: node_modules/@open-mercato/core/src/modules/workflows
 
 ## Sections

package/dist/agentic/guides/reference-module-facts.json

@@ -1185,7 +1185,7 @@
     "facts": {
       "title": "Example Module",
       "description": "Demonstrates pages, APIs, entities and DI.",
-      "coreVersion": "0.10.1-develop.7783.1.e04ffd226c",
+      "coreVersion": "0.10.1-develop.7784.1.80225b38e4",
       "sourcePackage": null,
       "sourceVersion": null,
       "sourceRoot": "src/modules/example",

package/dist/agentic/guides/upstream/BACKWARD_COMPATIBILITY.md

@@ -492,9 +492,9 @@ Spec: [`.ai/specs/2026-09-08-error-reporting-policy.md`](.ai/specs/2026-09-08-er
 |`queue` failure paths, `data_sync` engine|Existing `logger.error` lines keep their text and gain a `reportError` call with a `code`|✓ ADDITIVE|
 |`reportError`'s `code`|A value that is not shaped `module.reason` is dropped rather than published, so it cannot become an unbounded, unredacted metric label. No in-repo caller passes one; a caller that did reported exactly as one passing no `code`, which is the pre-PR behaviour|✓ ADDITIVE|
 |`integration_logs` message text for the payment status poller and the Stripe webhook processor|The failure cause moves from `payload` **into** the message (`Payment status polling failed: {cause}`), because the payload is deliberately never reported. `payload` keeps the same fields|✓ ADDITIVE (row content, no schema or field change)|
-| `integration_logs.code` for the payment status poller | Previously `null`, now `payment_gateways.status_poll_failed`, so it groups apart from the `integrations.log_error` catch-all. The column and its API field already existed | ✓ ADDITIVE (a value where there was none) |
-| `IntegrationLogError` (`core:integrations`), `SyncRunPartialFailureError` (`core:data_sync`) | New exported error classes | ✓ ADDITIVE |
-| API route URLs, response schemas, database schema, event IDs, ACL features, DI names, CLI commands, env vars | No change — the policy adds no configuration | ✓ n/a |
+|`integration_logs.code` for the payment status poller|Previously `null`, now `payment_gateways.status_poll_failed`, so it groups apart from the `integrations.log_error` catch-all. The column and its API field already existed|✓ ADDITIVE (a value where there was none)|
+|`IntegrationLogError` (`core:integrations`), `SyncRunPartialFailureError` (`core:data_sync`)|New exported error classes|✓ ADDITIVE|
+|API route URLs, response schemas, database schema, event IDs, ACL features, DI names, CLI commands, env vars|No change — the policy adds no configuration|✓ n/a|
 
 **Operator note — terminal queue failures.** Not a contract break, but visible in an alert rule: on the **local** strategy a job's final attempt previously emitted both `queue.job_failed` and `queue.job_exhausted`; it now emits only `queue.job_exhausted`, matching the `async` strategy. An alert thresholding on `queue.job_failed` alone stops seeing terminal failures — page on `queue.job_exhausted`.
 
@@ -504,13 +504,13 @@ Spec: [`.ai/specs/2026-09-08-error-reporting-policy.md`](.ai/specs/2026-09-08-er
 
 [`.ai/specs/2026-09-16-data-sync-retry-resume-actions.md`](.ai/specs/2026-09-16-data-sync-retry-resume-actions.md) splits the Data Sync dashboard's single overloaded "Retry" button into three named operator actions — **Retry** (labelled **Resume** on a cancelled run), **Retry from the beginning**, and **Run again** — and states, on the run detail page, where a retry would resume. **All changes are additive** and pass the contract-surface checks above:
 
-| Surface | Change | Classification |
+|Surface|Change|Classification|
 |---|---|---|
-| Type definitions (§2) | New exported types `ResumePoint` (a discriminated union of `none` / `noCommittedBatch` / `resumes`) and `ResumePointRun` | ✓ ADDITIVE (new types, nothing renamed — same shape as the `StartControlMap` addition before it) |
-| Import paths (§4) | New module `data_sync/lib/resume-point.ts` exporting `resolveResumePoint`, `isRetryableRunStatus`, `ResumePoint`, `ResumePointRun` | ✓ ADDITIVE (new path; nothing moved or re-exported) |
-| API route URLs (§7) | **No change.** `POST /api/data_sync/runs/[id]/retry` and `POST /api/data_sync/run` are untouched — no new request field, no new response field, no new status code and no new error code. The UI starts sending the already-accepted `fromBeginning: true` for the first time, and reads `cursor` / `initialCursor` / `batchesCompleted`, all of which `GET /api/data_sync/runs` and `GET /api/data_sync/runs/[id]` have returned since 2026-08-12 | ✓ n/a |
-| Database schema (§8) | No change. No entity, column, migration or `.snapshot-open-mercato.json` update; no new run status — the vestigial `paused` status is left exactly as it was | ✓ n/a |
-| Auto-discovery, function signatures, event IDs, widget spot IDs, DI names, ACL features, notification IDs, CLI commands, generated files | No change | ✓ n/a |
+|Type definitions (§2)|New exported types `ResumePoint` (a discriminated union of `none` / `noCommittedBatch` / `resumes`) and `ResumePointRun`|✓ ADDITIVE (new types, nothing renamed — same shape as the `StartControlMap` addition before it)|
+|Import paths (§4)|New module `data_sync/lib/resume-point.ts` exporting `resolveResumePoint`, `isRetryableRunStatus`, `ResumePoint`, `ResumePointRun`|✓ ADDITIVE (new path; nothing moved or re-exported)|
+|API route URLs (§7)|**No change.** `POST /api/data_sync/runs/[id]/retry` and `POST /api/data_sync/run` are untouched — no new request field, no new response field, no new status code and no new error code. The UI starts sending the already-accepted `fromBeginning: true` for the first time, and reads `cursor` / `initialCursor` / `batchesCompleted`, all of which `GET /api/data_sync/runs` and `GET /api/data_sync/runs/[id]` have returned since 2026-08-12|✓ n/a|
+|Database schema (§8)|No change. No entity, column, migration or `.snapshot-open-mercato.json` update; no new run status — the vestigial `paused` status is left exactly as it was|✓ n/a|
+|Auto-discovery, function signatures, event IDs, widget spot IDs, DI names, ACL features, notification IDs, CLI commands, generated files|No change|✓ n/a|
 
 **Contract commitments**: the retry endpoint deliberately does **not** enforce `supportsStartControl('fullSync', entityType)` before honouring `fromBeginning: true`. [§ Data Sync Start Control Applicability (2026-09-02)](#data-sync-start-control-applicability-2026-09-02) already commits that the declaration "governs what the dashboard **offers**, never what the run API **accepts**", and `fromBeginning: true` on `retry` requests the identical thing as `fullSync: true` on `run` — a `null` start cursor — so the two siblings MUST answer identically. An adapter-declared restriction hides the from-the-beginning action in the UI and nothing more; a scripted or API client keeps the documented escape hatch. Making either endpoint strict is a breaking change under §7 and needs the deprecation protocol, not a UI spec.
 
@@ -522,12 +522,12 @@ Spec: [`.ai/specs/2026-09-08-error-reporting-policy.md`](.ai/specs/2026-09-08-er
 
 [`.ai/specs/2026-09-16-customers-quick-create-injection-spot-bridge.md`](.ai/specs/2026-09-16-customers-quick-create-injection-spot-bridge.md) binds the sales document form's Person/Company quick-create dialogs to the customers module's declared `crud-form:customers.person` / `…company` hosts. The dialogs previously had no `injectionSpotId`, so `CrudForm` auto-derived `crud-form:customers.customer_entity` (§6, FROZEN) there instead.
 
-| Surface | Change | Classification |
+|Surface|Change|Classification|
 |---|---|---|
-| Widget Injection Spot IDs (§6) | `CrudForm` gains an additive `legacyInjectionSpotId?: string` prop. When set, its header/body/field widgets are dual-published alongside the primary `injectionSpotId`'s — `crud-form:customers.customer_entity` stays live on these two dialogs via the bridge, so nothing that already targets it stops rendering | ✓ ADDITIVE (bridge, not a removal — see Deprecation Protocol steps 1–3) |
-| Widget Injection Spot IDs (§6) | The two dialogs now also publish `crud-form:customers.person` / `…company` (previously published only by the person/company detail pages) | ✓ ADDITIVE ("MAY add new spot IDs to new or existing pages") |
-| Context passed to widgets at `crud-form:customers.person` / `…company` | These hosts' widgets now also mount with `operation: 'create'` and no `recordId` on the two quick-create dialogs, for the first time — previously always `operation: 'update'` with a concrete `recordId` | Disclosed in [`UPGRADE_NOTES.md`](UPGRADE_NOTES.md) "Action for module authors"; not itself a contract surface change (§6 permits "new optional context fields", and `operation`/`recordId` were always part of the injection context shape) |
-| Type definitions (§2) | New optional `CrudForm` prop `legacyInjectionSpotId?: string` | ✓ ADDITIVE |
+|Widget Injection Spot IDs (§6)|`CrudForm` gains an additive `legacyInjectionSpotId?: string` prop. When set, its header/body/field widgets are dual-published alongside the primary `injectionSpotId`'s — `crud-form:customers.customer_entity` stays live on these two dialogs via the bridge, so nothing that already targets it stops rendering|✓ ADDITIVE (bridge, not a removal — see Deprecation Protocol steps 1–3)|
+|Widget Injection Spot IDs (§6)|The two dialogs now also publish `crud-form:customers.person` / `…company` (previously published only by the person/company detail pages)|✓ ADDITIVE ("MAY add new spot IDs to new or existing pages")|
+|Context passed to widgets at `crud-form:customers.person` / `…company`|These hosts' widgets now also mount with `operation: 'create'` and no `recordId` on the two quick-create dialogs, for the first time — previously always `operation: 'update'` with a concrete `recordId`|Disclosed in [`UPGRADE_NOTES.md`](UPGRADE_NOTES.md) "Action for module authors"; not itself a contract surface change (§6 permits "new optional context fields", and `operation`/`recordId` were always part of the injection context shape)|
+|Type definitions (§2)|New optional `CrudForm` prop `legacyInjectionSpotId?: string`|✓ ADDITIVE|
 
 **Deprecation window.** `legacyInjectionSpotId` is scoped to these two call sites and intended for removal after at least one minor version (Deprecation Protocol step 1), tracked in the spec's Changelog and in `UPGRADE_NOTES.md`. No maintainer waiver was needed — nothing is removed by this change.
 
@@ -541,11 +541,11 @@ Clients use WebAuthn; operators audit key provenance, re-enroll with recovery. [
 
 [`.ai/specs/2026-07-28-protected-roles-and-audit-seam.md`](.ai/specs/2026-07-28-protected-roles-and-audit-seam.md) closes the auth undo/redo transaction, authorization, and membership-phantom gaps without changing existing command handlers by default.
 
-| Surface | Change | Classification |
+|Surface|Change|Classification|
 |---|---|---|
-| Type definitions (`CommandHandler`, `CommandRuntimeContext`, `CommandExecuteResult`) | New optional `atomicReplay?: boolean` and `stabilizeReplay(...)` handler capabilities, optional `replayTransactionGuard` request guard, optional caller-owned `transactionLifetime`, and optional `replaySourceFinalized?: boolean` result signal. `TransactionLifetime` plus its observation/completion-registration helpers are new exports; lifetime creation/completion remains owned by `withAtomicFlush` | ✓ ADDITIVE (optional fields and exports; omitted handlers and contexts keep the prior flow) |
-| `ActionLogService` method signatures | `log`, `claimForUndo`, `releaseUndoClaim`, and `markUndone` accept an optional trailing transactional `EntityManager`; new `claimForRedo` method | ✓ ADDITIVE (optional parameters appended and a new method; existing calls retain behavior) |
-| `RbacService` | New `loadAclWithEntityManager`, `userHasAllFeaturesWithEntityManager`, and `getGrantedFeaturesWithEntityManager` methods bypass caches and bind every query to the supplied transaction | ✓ ADDITIVE (new methods; existing cache-backed methods are unchanged) |
+|Type definitions (`CommandHandler`, `CommandRuntimeContext`, `CommandExecuteResult`)|New optional `atomicReplay?: boolean` and `stabilizeReplay(...)` handler capabilities, optional `replayTransactionGuard` request guard, optional caller-owned `transactionLifetime`, and optional `replaySourceFinalized?: boolean` result signal. `TransactionLifetime` plus its observation/completion-registration helpers are new exports; lifetime creation/completion remains owned by `withAtomicFlush`|✓ ADDITIVE (optional fields and exports; omitted handlers and contexts keep the prior flow)|
+|`ActionLogService` method signatures|`log`, `claimForUndo`, `releaseUndoClaim`, and `markUndone` accept an optional trailing transactional `EntityManager`; new `claimForRedo` method|✓ ADDITIVE (optional parameters appended and a new method; existing calls retain behavior)|
+|`RbacService`|New `loadAclWithEntityManager`, `userHasAllFeaturesWithEntityManager`, and `getGrantedFeaturesWithEntityManager` methods bypass caches and bind every query to the supplied transaction|✓ ADDITIVE (new methods; existing cache-backed methods are unchanged)|
 | Auth command replay behavior | Auth user/role handlers opt in so source-log state, domain changes, undo trace or new redo log, and redo source finalization commit or roll back together. Before the request guard or feature interceptors run, `stabilizeReplay` discovers and seals one actor/target/destination footprint and locks API keys, users, roles, tenant/organization hierarchy, and authorization children in a total order using the same transaction | ⚠️ Intentional security hardening. A race that previously could deadlock or replay with stale authority is rejected with the existing domain `409`; successful, authorized replay keeps the same response shape |
 | Action-log actor persistence and self replay | `actor_user_id` remains a UUID; new entries also store the canonical user or `api_key:<uuid>` subject in `context.actorSubject`. API-key list ownership, undo/redo ownership, exact-EM RBAC, locks, and latest replay queries use the canonical subject. Canonical history is selected before the legacy bare-UUID fallback, which additionally requires a coherent live `isApiKey`/`keyId`/`sub` tuple | ✓ Database-compatible additive context metadata; same-UUID user, malformed, or ambiguous ownership cannot shadow canonical key history and fails closed |
 | Auth authorization-state writers | First-party `UserRole`, `UserAcl`, and `RoleAcl` writers in commands, setup, CLI, execution principals, SSO, and agent orchestration now share the canonical parent-lock protocol; SSO membership and grant rows commit together | ⚠️ Intentional concurrency hardening; no request, response, schema, import-path, event, feature, or CLI contract changes |

package/dist/agentic/guides/upstream/manifest.json

@@ -1,8 +1,8 @@
 {
   "version": 1,
-  "generator": "@open-mercato/cli@0.10.1-develop.7783.1.e04ffd226c",
+  "generator": "@open-mercato/cli@0.10.1-develop.7784.1.80225b38e4",
   "files": {
     "AGENTS.md": "b27342ee5f61e805ba52703fdb7ec822b030490f734b4d80f48dfd1e05fa4cf5",
-    "BACKWARD_COMPATIBILITY.md": "11bb1cf9883e04577239b2a336e7ee022de2cbd8894c1f469fa8ea9468921451"
+    "BACKWARD_COMPATIBILITY.md": "e4b53767506d7ff4628c6cc7e38956792b32eb606749f8f4ba3f67dd2c9e86da"
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-mercato/cli",
-  "version": "0.10.1-develop.7783.1.e04ffd226c",
+  "version": "0.10.1-develop.7784.1.80225b38e4",
   "license": "MIT",
   "type": "module",
   "main": "./dist/index.js",
@@ -60,10 +60,10 @@
     "@mikro-orm/decorators": "^7.1.14",
     "@mikro-orm/migrations": "^7.1.14",
     "@mikro-orm/postgresql": "^7.1.14",
-    "@open-mercato/events": "0.10.1-develop.7783.1.e04ffd226c",
-    "@open-mercato/queue": "0.10.1-develop.7783.1.e04ffd226c",
-    "@open-mercato/shared": "0.10.1-develop.7783.1.e04ffd226c",
-    "@open-mercato/telemetry": "0.10.1-develop.7783.1.e04ffd226c",
+    "@open-mercato/events": "0.10.1-develop.7784.1.80225b38e4",
+    "@open-mercato/queue": "0.10.1-develop.7784.1.80225b38e4",
+    "@open-mercato/shared": "0.10.1-develop.7784.1.80225b38e4",
+    "@open-mercato/telemetry": "0.10.1-develop.7784.1.80225b38e4",
     "cross-spawn": "^7.0.6",
     "minisearch": "7.2.0",
     "pg": "8.23.0",
@@ -75,10 +75,10 @@
     "typescript-js": "npm:typescript@6.0.3"
   },
   "peerDependencies": {
-    "@open-mercato/shared": "0.10.1-develop.7783.1.e04ffd226c"
+    "@open-mercato/shared": "0.10.1-develop.7784.1.80225b38e4"
   },
   "devDependencies": {
-    "@open-mercato/shared": "0.10.1-develop.7783.1.e04ffd226c",
+    "@open-mercato/shared": "0.10.1-develop.7784.1.80225b38e4",
     "@types/jest": "^30.0.0",
     "jest": "^30.4.2",
     "ts-jest": "^29.4.12"