@eintrek/erp-shell 0.1.73 → 0.1.75

package/README.md

@@ -176,6 +176,69 @@ progress API: `API.md` next to it.
   shell's adapters), `guide-ui.tsx`, `guide-styles.ts`. Tests:
   `src/guide/*.test.ts`.
 
+### 0.1.75
+
+Section guides ("อธิบายส่วนนี้"; authors: `_claude-work/guides-r4/GUIDE-PAGES.md` §10).
+
+- `GuideSuite.sections?: GuideSection[]`: explains one section of a page
+  (a number-heavy card or table) row by row. View steps only (the default
+  kind here); a step may point at a row or cell (`targetId`). Tied to a
+  route and a root anchor: there only while the root is on screen, and it
+  ends when the root goes or the page is left.
+- Live values: the app hands its computed numbers to the guide with
+  `useSectionGuideValues(key, values)` or `<SectionGuideButton guideKey
+  values />`; step `title`/`why` read `ctx.values`. The latest render wins,
+  so a page that re-renders mid-guide never leaves an old number. A step
+  lists what it uses in `needs` and is skipped while one is missing (also
+  when its title comes out empty). `formatBaht`, `thaiMonth`,
+  `thaiMonthYear` for the copy.
+- Entry points: `<SectionGuideButton guideKey />` (a small "?" for the
+  section header, drawn only while the guide is there for this person) and
+  "?" → "อธิบายส่วนนี้ · <title>" for every section guide on screen. Never
+  offered by itself, in any mode; not in the panel's list.
+- Progress: one row per section guide per person, `<app>.section.<key>`,
+  written once, as page rows. Same switch and audience as page guides.
+- Fix: "ขั้นที่ x/y" no longer counts a click step that passes by itself
+  (its outcome already on screen): Plannex's overview said 1/9, then 3/9.
+
+### 0.1.74
+
+Page guides ("คู่มือหน้านี้", guides round 4; authors:
+`_claude-work/guides-r4/GUIDE-PAGES.md`).
+
+- `GuideSuite.pages?: GuidePage[]`: a read-only walk through one page,
+  `view` and `click` steps only (a page guide with a `commit`, `input` or
+  `select` step is dropped, with a warning in development). It runs as a
+  replay of a synthetic mission `page:<key>`, so it never writes tour
+  progress. `when` names an anchor that must be on screen (sub-screens on
+  one URL); the most specific match wins (`when`, then `?k=v` constraints,
+  then static segments), and only if it is this person's (`visible`,
+  `requires`).
+- Progress: one row per page per user, `<app>.page.<key>`, written once —
+  when the first-visit offer is answered or ignored, or when the guide
+  ends (finished: completed; not now, exited, left: skipped). Opened again
+  from "?", it writes nothing. Read from the same `GET …/guides/me` answer.
+- Switch: platform-api's `pages_mode` (`guides.<app>.pages` = off | menu |
+  offer, default off) and `page_audience` (every member while not off). In
+  `menu` mode nothing is offered by itself; in `offer` mode a small card
+  ("คู่มือหน้านี้ · <title> · n ขั้น", เริ่ม / ไม่ตอนนี้) appears once on a
+  first visit, when nothing else is up and the welcome is not due there. An
+  API without the fields means off.
+- The "?" menu: "คู่มือหน้านี้", "ไกด์เริ่มต้น n/N", "คู่มือทุกหน้า",
+  "ติดต่อทีมช่วยเหลือ", each only when it has something
+  (`guideMenuItems`). The panel gains a second section, "คู่มือแต่ละหน้า"
+  (ดูแล้ว / ใหม่), and shows it alone when the person has no missions.
+- A page guide's bubble: "คู่มือหน้านี้ · <title>", ย้อนกลับ on read steps,
+  "เสร็จ" on the last, "ปิดคู่มือ" to leave (silently, as leaving the page
+  does). Finishing says "จบคู่มือหน้านี้".
+- Missions keep precedence: a mission start ends a page guide, the welcome
+  replaces an offer (unrecorded), a page guide never starts over a step.
+- `config.pagesReady` holds page guides apart from the missions' `ready`.
+- For apps with their own "?" (LIFF): `usePageGuideEntry()` →
+  `{ title, open } | null`, `openPageGuide()`, `openPagesPanel()`,
+  `usePageGuides()`, from both entries.
+- `guideMenuShown(entry, pages?)` is no longer a type guard.
+
 ### 0.1.73
 
 - `GuideStep.status`: a short status line in the bubble while it returns