@eintrek/erp-shell 0.1.67 → 0.1.69

package/README.md

@@ -170,10 +170,43 @@ progress API: `API.md` next to it.
 - New dependency: `@floating-ui/dom` (external in the bundle; Radix already
   installs it in every app).
 - Code: `src/guide/` — `types.ts` (definitions), `machine.ts` (pure state
-  machine), `patterns.ts`, `progress.ts` / `progress-client.ts` (API),
-  `dom.ts`, `guide-host.tsx`, `guide-ui.tsx`, `guide-styles.ts`. Tests:
+  machine), `patterns.ts`, `progress.ts` / `progress-sync.ts` (rules, 409
+  merge) / `progress-client.ts` (platform-api), `dom.ts`,
+  `guide-runtime.tsx` (the engine, adapters in), `guide-host.tsx` (the
+  shell's adapters), `guide-ui.tsx`, `guide-styles.ts`. Tests:
   `src/guide/*.test.ts`.
 
+### 0.1.69
+
+- A step can point at a Radix trigger that is shut (a collapsed sidebar
+  group header, a dialog's open button). Such triggers carry
+  `data-state="closed"` and used to count as absent, so the step waited
+  forever. Closed content still counts as absent.
+
+### 0.1.68: `@eintrek/erp-shell/guide-core`
+
+- A second entry (`exports` map: `"."`, `"./guide-core"`, `"./package.json"`)
+  with the engine alone: React, react-dom and `@floating-ui/dom`, no React
+  Query, axios, zustand, next-auth, next-themes, Next or sidebar. Every peer
+  but react/react-dom is now optional (`peerDependenciesMeta`). The CommonJS
+  build is `dist/*.cjs` (`main`); bundlers read the ESM build as before. Both
+  entries share one chunk, so the tour's state is one instance.
+- `GuideRuntime` takes adapters: `routing` (pathname, search, navigate),
+  `isBusy()`, `progress` (`fetchProgress` / `saveProgress` returning the API's
+  own shapes; parsing and the 409 merge stay in the engine), `menu` (or
+  null), `hidden`, `bottomOffset`. `GuideHost` is now a thin wrapper that
+  builds them from the shell: Peoplx behaves as before.
+- `reportApiCall({ method, url, status, data })`: the API bus for a plain
+  `fetch` client.
+- `GuideMission.visible?(ctx)`: a hidden mission is not drawn, not counted in
+  n/N, never "next". `GuideMission.completeOn?`: `{ api }` / `{ event }`
+  marks it done outside the tour (the ordinary save) and celebrates at the
+  next idle moment.
+- CSS variable `--erp-guide-bottom-offset` for the chip and the bottom card.
+- `GuideAppId` gains `"liff"`; route patterns accept `[[x]]` (a segment that
+  may be absent: `/me/[[code]]/attendance`).
+- Authors: `_claude-work/guides-r2/GUIDE-CORE.md`.
+
 ## Roadmap
 
 | Phase | Scope                                                                 | Files to move from each app                                      |