@odla-ai/cli 0.25.1 → 0.25.2

package/dist/index.js

@@ -49,7 +49,7 @@ import {
   startHostedSecurityJob,
   surfacePaths,
   validateInvocation
-} from "./chunk-M4XST3OX.js";
+} from "./chunk-MX6FSJUN.js";
 export {
   AGENT_HARNESSES,
   CAPABILITIES,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/cli",
-  "version": "0.25.1",
+  "version": "0.25.2",
   "description": "Agent-operable CLI for odla provisioning, calendar consent and sync lifecycle, System AI administration, Worker secrets, security jobs, and smoke checks.",
   "license": "MIT",
   "homepage": "https://odla.ai/docs/packages/cli",

package/skills/odla-migrate/references/phase-2-chapter.md

@@ -39,19 +39,69 @@ hand-author only the namespaces it does not.
    hands each the same context (`ctx.verifyUser`, `ctx.makeDb`, `ctx.roleFor`,
    `ctx.isAdmin`), so you never verify a JWT twice. Do NOT hand routes over to
    chapter in the same change as the framework swap.
-5. **Adopt the host-independent console shell.** Import
-   `@odla-ai/ui/themes/salt/app.css` once, then render
-   `<ChapterAdmin chapter={chapter}/>` at the existing `/admin/` mount. The
-   config supplies brand tokens and the standard sections. Navigation uses
-   `?tab=` by default, so do not add `/admin/*` SPA rewrites to an ordinary
-   static site. Legacy path links remain readable.
+5. **Adopt the host-independent console shell without replacing product
+   behavior.** Import the scoped theme, `@odla-ai/ui/index.css`, and
+   `@odla-ai/crm/ui.css`, then render `ChapterAdmin` at the existing `/admin/`
+   mount. A greenfield site may accept the default workspaces after reviewing
+   them against its product requirements. An operating site must preserve each
+   validated workspace through the `workspaces` transform until the
+   feature-level UI gate below proves the packaged composition equivalent.
+   Chapter's default navigation uses fragments such as
+   `/admin/#people/person/record-id/profile`; keep legacy query/path links only
+   as inbound compatibility URLs.
 6. **Override rather than inherit wherever local behavior was a decision.**
 7. `npx @odla-ai/cli doctor` → `provision --dry-run` (show the human) → provision.
 
-The same parity-before-deletion pattern works for UI: render the packaged
-component beside yours, assert byte-identical markup, then delete yours and keep
-the test as an integration guard — the CSS class contract is the site's, not the
-package's.
+### Existing admin workspace gate
+
+Labels and route ids are inventory keys, not parity evidence. A legacy
+workspace named "People" and Chapter's default `people` workspace can use the
+same CRM rows while exposing different summaries, search and filtering,
+selection behavior, role signals, mutations, and error states.
+
+For every existing workspace, inventory and test:
+
+- summaries and operational counts;
+- search, filters, sort, pagination, saved views, and responsive list/detail
+  geometry;
+- role, permission, lifecycle, billing, and identity signals;
+- record tabs, deep links, and every mutation or provider side effect;
+- loading, empty, error, unauthorized, keyboard, and narrow-screen states.
+
+Classify each item as packaged-equivalent, composed through a documented
+Chapter/CRM seam, an explicit PM-approved product change, or blocked. A matching
+top-level label, a populated table, or a green schema/API test proves none of
+those classifications.
+
+The safe first cutover is to preserve the existing workspace first and let
+Chapter own the surrounding auth, routing, chrome, and other reviewed defaults:
+
+```tsx
+const workspaces = (defaults) => {
+  if (!defaults.some((workspace) => workspace.id === "people")) {
+    throw new Error("expected ChapterAdmin people workspace");
+  }
+  return defaults.map((workspace) =>
+    workspace.id === "people"
+      ? { ...workspace, render: (ctx) => <ExistingPeople context={ctx} /> }
+      : workspace
+  );
+};
+
+<ChapterAdmin chapter={chapter} workspaces={workspaces} />;
+```
+
+Match the exact id and fail closed if Chapter changes its catalog. Spread the
+default workspace so its reviewed routing metadata survives. Keep an
+integration test that asserts the host component renders and that representative
+summary, exploration, role, and operation affordances are present.
+
+Only then migrate pieces into `collectionSection`/`peopleSection` using
+`renderSummary`, `renderMaster`, `renderDetailHeader`, `renderEmptyDetail`,
+`hrefForRecord`, `extendRecordTabs`, and an application-authoritative
+`lifecycleAdapter`. Delete the old workspace only after the complete behavioral
+matrix and deployed viewport journey pass. For a greenfield site, build the same
+matrix from requirements; there is no legacy component to preserve.
 
 ## Behavior deltas to audit