wenay-react2 1.0.40 → 1.0.41

package/doc/PROJECT_FUNCTIONALITY.md

@@ -0,0 +1,401 @@
+# wenay-react2 Project Functionality
+
+This document describes what this project provides and why each area exists.
+It is not a README and not a full API reference.
+
+Read this together with:
+
+- `doc/wenay-react2.md` for everyday signatures.
+- `doc/wenay-react2-rare.md` for low-level details and edge cases.
+- `doc/EXAMPLE_USAGE.md` for usage standards and examples.
+- `src/common/testUseReact/qa.tsx` for the live QA stand.
+
+## Project Role
+
+`wenay-react2` is a shared React UI/controller package for wenay apps.
+Its main job is to package recurring UI infrastructure so products do not keep
+rebuilding table buffers, floating windows, context menus, settings editors,
+toolbar persistence, React subscriptions, and replay/store adapters.
+
+The package should stay generic. It may know lifecycle, rendering,
+persistence mechanics, and UI contracts. It must not know product business
+terms such as exchange names, portfolio rules, strategy policy, domain column
+groups, account behavior, or screen-specific layout decisions.
+
+## Core Design Contract
+
+New shared functionality should follow these rules:
+
+- A primitive owns one generic problem.
+- App policy belongs in an app wrapper above the primitive.
+- Shared behavior starts as a headless hook/controller whenever it has lifecycle, state, persistence, subscription, selection, or user interaction rules.
+- React hooks own subscription/lifecycle wiring and may return a small API, not only plain X/Y data.
+- Controllers expose a small imperative API when state must outlive a render.
+- Serializable UI config is stored through `memoryGetOrCreate` and announced
+  through `memoryCache`, but the app decides when to write storage.
+- Visual components and QA stand layers should be thin renderers over the hook/controller surface.
+- Demos should prove the primitive's contract, not hide product policy inside
+  the library.
+
+Canonical controller vocabulary:
+
+```ts
+open / close / set / replace       // modal-like state
+update / remove / clean / sync     // buffered data state
+fit / flush                        // ag-grid lifecycle
+props / bind                       // spreadable DOM props
+get / set / reset / cancel         // local controller state
+on -> off                          // subscriptions
+```
+
+## Public Entry
+
+Consumers import from the package root:
+
+```ts
+import { createToolbar, useAgGrid, createColumnState } from "wenay-react2"
+```
+
+`src/common/api.tsx` is the root export aggregator. It also exports `kit` for
+large files that prefer grouped namespaces:
+
+```ts
+import { kit } from "wenay-react2"
+
+kit.grid
+kit.modal
+kit.menu
+kit.logs
+kit.updateBy
+```
+
+## Compatibility Policy
+
+New hook/controller surfaces should prefer migration without breaking old public APIs, but compatibility is not absolute. An aggressive migration is allowed only as an explicit migration cut: separate task, changelog, migration notes, and a clear list of changed imports/behavior. Default visual styles have a stricter rule: do not remove a default class/style contract unless the replacement class/token path already exists and is documented.
+
+For diagnostics, the library may expose local counters/listeners, but it must not send hidden analytics. Apps decide whether to read, persist, or report those counters.
+
+## Functional Areas
+
+### Render Memory
+
+Purpose: bridge external mutable objects into React renders.
+
+Main APIs:
+
+- `updateBy`, `useUpdateBy`, `renderBy`, `renderByRevers`, `renderByLast`
+- `createUpdateApi`, `useUpdateByApi`
+- `memoryGetOrCreate`, `memoryUpdate`, `memoryMarkDirty`, `memoryCache`
+
+Use this when a module-level controller or persisted config needs React views
+to refresh without moving all state into component-local `useState`.
+
+Do not use this as a default replacement for normal React state. If a state is
+local to one component and has no external lifecycle, `useState` is simpler.
+
+### Persistence And Memory Cache
+
+Purpose: centralize process/browser memory maps used by shared UI surfaces.
+
+Shared primitives can mark config as dirty. They do not choose a write policy.
+The application should call `memoryCache.load()` on startup and decide whether
+to save on debounce, route leave, visibility change, pagehide, or explicit user
+action.
+
+This matters because toolbar layout, UI slot placement, column state, floating
+window geometry, and resize maps are all user-facing preferences. The library
+should not silently write storage at surprising times.
+
+### Outside Click, Buttons, And Floating UI
+
+Purpose: reusable interaction wrappers for menus, popups, and floating panels.
+
+Main APIs:
+
+- `useOutside`, `OutsideClickArea`
+- `Button`, `OutsideButton`, `HoverButton`, `AbsoluteButton`
+- `FloatingWindow`, `useFloatingWindowController`
+- `useDraggableApi`, `useReorder`, `useReorderBoard`
+
+Use these when the UI problem is generic: outside-click closing, draggable
+position, ordered drag-and-drop, or a persistent floating window. Use `useFloatingWindowController` only for custom chrome around the same geometry/stack/resize behavior.
+
+Do not hide business flow inside these components. For example, a trade ticket
+window is an app component that may use `FloatingWindow`, not a library
+primitive.
+
+### Modal And Input Helpers
+
+Purpose: common modal lifecycle and simple text/file input flows.
+
+Main APIs:
+
+- `ModalProvider`, `useModal`
+- `FreeModal`, `TextInputModal`, `FileInputModal`
+- `inputModal`, `confirmModal` for low-level compatibility paths
+
+Use `ModalProvider` + `useModal` for new code. Low-level JSX stores exist for
+compatibility and rare cases.
+
+### Settings Dialog, UI Slot, And Toolbar
+
+Purpose: configurable product chrome without each app inventing its own
+settings registry, placement switcher, and toolbar editor.
+
+Main APIs:
+
+- `SettingsDialog`, `useSettingsDialogController`, `registerSettingsSection`
+- `createUiSlot`
+- `createToolbar`, `registerToolbarDensity`, `toolbarItemIcon`
+
+Use `SettingsDialog` when the app has multiple settings sections or needs a
+searchable settings tree. Use `useSettingsDialogController` when custom settings
+chrome needs the same open/search/tree/history/resize behavior.
+
+Use `createUiSlot` when the same UI fragment may live in several places and
+the user can choose the placement.
+
+Use `createToolbar` when a command strip needs:
+
+- persistent item order and visibility;
+- density modes such as icon-only or icon+label;
+- a reusable settings editor;
+- optional source-owned order/visibility via `UiListSource`.
+
+`createToolbar({source})` is important: it lets the toolbar become a view over
+another config. The main example is `columnState.api.listSource`, where grid,
+column menu, and toolbar should all mirror one column order/visibility source.
+
+### Menus
+
+Purpose: generic menu rendering and context-menu coordination.
+
+Main APIs:
+
+- `Menu`
+- `contextMenu.Layer`
+- `contextMenu.openAt(event, items)`
+- `DropdownMenu`
+- `useRightMenuController`
+
+Use `contextMenu.openAt(e, items)` for new right-click integrations. It opens
+one current menu from a concrete event/point. Older queued/global paths remain
+for compatibility through `1.x` but should not be taught in new examples.
+
+`DropdownMenu` is a floating action menu with caller-owned trigger/content
+styling. It is not the main right-click primitive. `useRightMenuController`
+keeps open/fixed/select/submenu/drag state reusable for custom floating-menu views.
+
+Menu diagnostics should start from the right-click surface: count `openAt` vs legacy queued opens, sources/layers, close reasons, item clicks by explicit stable keys, submenu opens, and async menu errors. These counters should be local/opt-in, not hidden analytics.
+
+### agGrid4
+
+Purpose: shared ag-grid lifecycle, row buffering, dynamic columns, and common
+grid defaults.
+
+Main APIs:
+
+- `createGridBuffer`
+- `useAgGrid`
+- `AgGridTable`
+- `createColumnBuffer`
+- `useAgGridTheme`, `buildAgTheme`
+- `numericComparator`, `colDefCentered`, `colDefWrap`
+
+Use plain `AgGridTable` for declarative `rowData`.
+
+Use `useAgGrid` or `createGridBuffer` when row updates arrive as patches,
+streams, or imperative transactions.
+
+Use overlay mode when React-owned `rowData` owns the row set and external
+patches should update only already-present rows.
+
+Use `createColumnBuffer` for generic dynamic column-name lifecycle. The shared
+buffer stores names and replays them; the app wrapper decides target group,
+column shape, `colId`, labels, and domain rules.
+
+Low-level `applyGridRows` exists, but it is not the preferred path for new
+React examples. Prefer the controller path because it owns attach/detach/sync
+and reduces race conditions around grid readiness.
+
+### Column State
+
+Purpose: one persisted column config that can drive desktop grids, icon menus,
+toolbars, and mobile card views.
+
+Main APIs:
+
+- `createColumnState`
+- `ColumnsMenu`, `MenuStrip`
+- `ColumnDots`
+- `CardList`
+- `columnState.grid.attach(api)` and `detach()`
+- `columnState.api.listSource`
+
+Use this when the user can change column order, visibility, width, sort,
+filter, or mobile field selection.
+
+Key idea: column config is independent from ag-grid. ag-grid is one adapter
+over it. Mobile cards and toolbar buttons read the same config without needing
+ag-grid at all.
+
+Runtime presence (`setPresent`, `setPresentGate`) is not persisted. It is for
+modes where some stable schema columns are currently unavailable.
+
+### Observe React Adapter
+
+Purpose: React hooks around `wenay-common2` Observe stores and listen objects.
+
+Main APIs:
+
+- `useStoreNode`, `useStoreKeys`, `useStoreSelect`
+- `useStoreMirror`
+- `useStoreEach`
+- `useListenEffect`, `useListenValue`, `useListenArgs`
+
+Use these when React needs to subscribe to external stores or listens. Network
+sync stays explicit through `useStoreMirror`; merely reading a node should not
+start hidden transport work.
+
+### Replay React Adapter
+
+Purpose: React-side lifecycle over `wenay-common2` Replay lines, store replay,
+route hand-off, pull frames, and archive playback.
+
+Main APIs:
+
+- `useReplaySubscribe`
+- `useReplayRouteSubscribe`
+- `useStoreReplaySync`, `useStoreReplayMirror`
+- `useStoreReplayRouteSync`, `useStoreReplayRouteMirror`
+- `useStoreReplayEach`
+- `useReplayFrame`
+- `useReplayHistory`
+
+Use these for high-frequency event lines, state sync from a replay source, and
+route hand-off between relay/direct transports.
+
+Avoid storing every frame in React state. High-frequency lines should fold into
+canvas, refs, external stores, or grid controllers. The controller exposes
+`seq()` and related getters so consumers can observe position without
+rerendering on every event.
+
+### Logs
+
+Purpose: shared logging UI and notification/table chrome.
+
+Main APIs:
+
+- `logsApi`
+- `getLogsApi`
+- `createLogsController`
+- `logsApi.React.Message`, `PageLogs`, `Setting`
+- context logger hooks/components in the rare surface (`useLogsTableController`, `useLogsNotificationsController`)
+
+Use `logsApi` for quick global logging. Use `createLogsController` when an app needs headless append/limit/settings state without the shared UI. Use context logger components when an app needs a larger logger surface.
+
+### Params
+
+Purpose: editable parameter UIs over `wenay-common2` Params structures and
+simple row/section editors.
+
+Main APIs:
+
+- `ParamsEditor`
+- `useParamsEditorController`
+- `ParamsEdit`
+- `ParamRow`
+- `useTextInputPanel`, `useFileInputPanel`
+- `TextInputPanel`, `FileInputPanel`
+
+Use these for generic param editing. `useParamsEditorController` owns the draft clone,
+immediate/delayed change notification, expand callback, and cleanup for custom renderers.
+Product-specific validation and save policy stay in the app.
+
+### Styles And Theme
+
+Purpose: shared visual tokens and theme hooks for library primitives.
+
+Main files:
+
+- `src/style/tokens.css`
+- `src/common/src/styles/tokens.ts`
+- `src/style/style.css`
+- `src/style/menuRight.css`
+- `src/common/src/styles/styleGrid.ts`
+- `src/common/src/grid/agGrid4/theme.ts`
+
+New shared UI should try existing tokens first. Add tokens when the value is
+part of a reusable primitive or expected to be themed by apps. One-off QA or
+app styles should stay in the app/demo wrapper.
+
+Default styles are part of the public usability contract. A primitive should remain usable after importing the package CSS; apps may override variables, but should not need to copy internal CSS just to avoid a broken surface. Runtime geometry can stay inline when it is computed from state; colors, spacing, borders, shadows, typography, and hover/active states should move to classes and CSS variables.
+
+### Charts
+
+Purpose: low-level chart engine and React chart demo surface.
+
+Main APIs:
+
+- `MyChartEngine`
+- `createChartCanvas`
+- chart engine internals exported through the rare surface
+
+The chart engine is intentionally low-level. Product apps should wrap it before
+using it as a domain chart.
+
+## QA Stand
+
+The live stand is `src/common/testUseReact/qa.tsx`.
+
+Run:
+
+```sh
+npm run testReact
+```
+
+The stand has active cards and an archive. Use active cards as the strongest
+signal for current behavior. Archive cards are regression checks and may show
+older or lower-level API paths.
+
+Important current cards:
+
+- 23-26: Replay hooks, store sync, per-key feed, route hand-off.
+- 28: `createColumnState` with ag-grid adapter.
+- 29: mobile `ColumnDots` + `CardList`.
+- 30: grouped sub-column mode above toolbar/columnState.
+- 31: `createToolbar` over `columnState.api.listSource`.
+
+Known audit note: archive card 5 and `src/common/testUseReact/useGrid.tsx`
+still demonstrate direct `applyGridRows`. That is useful as a regression
+check for the low-level helper, but new examples should teach `useAgGrid`,
+`AgGridTable`, or `createGridBuffer` first.
+
+## Adding A New Feature
+
+Before adding a shared primitive:
+
+1. Check whether an existing primitive already owns the problem.
+2. Decide the generic boundary: what belongs in the library, what belongs in
+   the product wrapper.
+3. Add an everyday example to `doc/wenay-react2.md` only if it is a public
+   everyday API.
+4. Prefer a `use*` hook or `create*` controller as the public behavior surface; add a visual component only as a layer over it.
+5. Add edge-case details to `doc/wenay-react2-rare.md`.
+6. Add or update a QA stand card when behavior is visual, interactive, or hard
+   to prove through unit tests alone.
+7. Add a changelog entry under `doc/changes/`.
+
+## Non-Goals
+
+`wenay-react2` should not become:
+
+- a product shell;
+- a business-domain library;
+- a hidden persistence service;
+- a transport selector;
+- a replacement for normal React local state;
+- a place for one-off app styling.
+
+The package should provide strong generic tools. Apps compose those tools into
+business behavior.

package/doc/PROJECT_RULES.md

@@ -0,0 +1,80 @@
+# Project Rules
+
+These rules are mandatory for maintainers and AI agents working in this repository.
+
+## README
+
+`README.md` is a documentation index only.
+
+It should say where the important files are, not teach the API, duplicate examples, or contain release history. Keep API explanations in the brief/rare docs and keep version notes in `doc/changes/`.
+
+Canonical documentation locations:
+
+- `doc/wenay-react2.md` - brief everyday API for this package.
+- `doc/wenay-react2-rare.md` - detailed, rare, compatibility, and migration notes for this package.
+- `doc/PROJECT_FUNCTIONALITY.md` - project functionality map: what each subsystem is for and what belongs outside the library.
+- `doc/EXAMPLE_USAGE.md` - example usage standards: which primitive to choose, how to use it, and why.
+- `doc/WENAY_REACT2_RENAMES.md` - breaking rename map for this package.
+- `doc/changes/` - recent version changes.
+
+`wenay-common2` documentation is not canonical in this repository. When common2 behavior matters, read the installed package/module docs and summarize only the React-facing impact in `doc/wenay-react2.md` or `doc/wenay-react2-rare.md`.
+
+## wenay-common2 / common2 Updates
+
+In this repository, `common2` is the short name for `wenay-common2`. If a request says to check updates, update common/common2, read what changed in common, or similar, and no other dependency is named, assume it means `wenay-common2`.
+
+Before summarizing or acting on such an update, read:
+
+- `node_modules/wenay-common2/package.json` for the installed version.
+- `node_modules/wenay-common2/doc/changes/README.md` and the newest files in `node_modules/wenay-common2/doc/changes/` for what changed.
+
+If the package is updated, read the changelog from the newly installed package before changing React-facing docs or code. Keep local docs focused on the React-facing impact.
+
+## Target Backlog
+
+- `doc/target/` is the durable queue for dictated tasks and imported task direction. Read `doc/target/README.md` before acting on a request that starts from `target`.
+- `doc/target/my.md` must show task status. Before implementation, move/normalize the selected item into `In Progress`; when implementation is believed complete, move it to `Verify`; remove it from the queue only after acceptance checks pass and durable results are recorded.
+- `doc/progress/` is temporary and must not be used as the only task-status record. If a progress file is deleted at completion, `doc/target/my.md` must already be cleaned, moved to `Verify`, or otherwise updated with the next required check.
+- `target/*.md` files are source specs/prompts. Do not edit or delete them merely for progress tracking unless the user explicitly asks.
+## Work Progress Files
+
+- For any task that is more than a tiny/local edit, create a temporary progress file before starting broad changes.
+- Put progress files under `doc/progress/`. This is the working-doc area, separate from public docs, roadmap docs, and release notes.
+- Name them by task, for example `doc/progress/replay-route-handoff.md`.
+- Keep the file short: goal, current checkpoints, notable decisions, blockers, and verification already run or still needed.
+- Update the progress file as checkpoints are completed, especially before switching context or making broad edits.
+- When the task is finished, delete the progress file.
+- Preserve only the durable outcome: final response, commit message, and, for publishable changes, the matching changelog/release-note entry.
+- If work is paused or blocked locally, leave the progress file in place and make the next required action explicit.
+- If the paused state must be committed or handed off, promote the useful part into a durable doc such as `ROADMAP`, `RECOMMENDATIONS`, `doc/target`, or `doc/changes`, instead of relying on an ignored progress file.
+
+## Recent Changes Catalog
+
+Every meaningful code, public API, dependency, migration, or documentation-policy change must add or update a file in `doc/changes/`.
+
+Rules:
+
+- Use one file per version: `doc/changes/vX.Y.Z.md`.
+- The version name is mandatory and must be visible in the file title.
+- Write the entry like a commit summary: what changed, why it matters, and how it was checked.
+- If several related changes land before the next publish, append them to the same version file.
+- Keep only the latest 10 version files in `doc/changes/`; when adding the 11th, delete the oldest version file.
+- Do not move old release notes into `README.md`.
+
+Recommended entry shape:
+
+```md
+# vX.Y.Z
+
+Date: YYYY-MM-DD
+
+- Changed: ...
+- Reason: ...
+- Verification: ...
+```
+
+## Style / Theme / Cleanup Notes
+
+When changing shared styles, tokens, theme contracts, QA stand behavior, or cleanup decisions, update `doc/wenay-react2-rare.md`. Keep README as an index and keep broad API examples in `doc/wenay-react2.md`.
+
+Do not delete public exports as cleanup in the same pass that identifies them. First document suspicious exports in the rare-doc cleanup inventory, then remove or move them only in a deliberate breaking change.

package/doc/WENAY_REACT2_RENAMES.md

@@ -0,0 +1,177 @@
+# wenay-react2 Rename Map
+
+Date: 2026-07-08
+
+This is a breaking rename map. The package does not keep old aliases for these names.
+
+## Root
+
+| Old | New |
+| --- | --- |
+| `v2` | `kit` |
+| `test()` | removed |
+| `LegacyMenuElement` | `MenuItemElement` |
+
+## Persistent Memory
+
+| Old | New |
+| --- | --- |
+| `Cash` | `memoryCache` |
+| `MemoryMap` | `memoryMaps` |
+| `staticGetAdd` | `memoryGetOrCreate` |
+| `staticGetById` | `memoryGetById` |
+| `staticSet` | `memorySet` |
+| `staticGet` | `memoryGet` |
+| `staticUpdate` | `memoryUpdate` |
+| `staticMarkDirty` | `memoryMarkDirty` |
+| `staticProps` | `memoryProps` |
+| `mapMemory.tsx` | `memoryStore.tsx` |
+
+## Outside Click And Keyboard
+
+| Old | New |
+| --- | --- |
+| `DivOutsideClick` | `OutsideClickArea` |
+| `DivOutsideClick2` | `OutsideClickArea` |
+| `ButtonOutClick` | `OutsideButton` |
+| `ButtonHover` | `HoverButton` |
+| `ButtonAbs` | `AbsoluteButton` |
+| `StyleOtherColum` | `StyleOtherColumn` |
+| `useOutsideOld` | `useOutsideRef` |
+| `useAddDownAnyKey` | `useKeyboard` |
+| `useKeyDown` | `useKeyboard` |
+| `useAnyKey` | `useKeyboard` |
+| `keyDownApi` | `keyboard` |
+| `KeyDown` | `keyboardState` |
+| `AnyKeyDownApi` | `KeyboardApi` |
+| `addDownAnyKey` | removed |
+| `useAddDownAnyKeyOld` | removed |
+| `useAddDownAnyKey.ts` | `useKeyboard.ts` |
+
+## Floating Windows And Drag
+
+| Old | New |
+| --- | --- |
+| `DraggableOutlineDiv` | `OutlineDragDemo` |
+| `DivRnd3` | `FloatingWindow` |
+| `DivRndBase3` | `FloatingWindowBase` |
+| `ExRNDMap3` | `floatingWindowMap` |
+| `tRndUpdate` | `FloatingWindowUpdate` |
+| `Drag22` | `DragBox` |
+| `Drag2Props` | `DragBoxProps` |
+| `Drag2` | `DragArea` |
+| `RNDFunc3.tsx` | `FloatingWindow.tsx` |
+| `RNDFunc.tsx` | `DragArea.tsx` |
+
+## Modal And Inputs
+
+| Old | New |
+| --- | --- |
+| `InputPage` | `TextInputPanel` |
+| `InputPageModal` | `TextInputModal` |
+| `InputFile` | `FileInputPanel` |
+| `InputFileModal` | `FileInputModal` |
+| `PageModalFree` | `FreeModal` |
+| `GetModalJSX` | `createModalElementStore` |
+| `GetModalFuncJSX` | `createModalRenderStore` |
+| `setModalJSX` argument | `modal` argument |
+| `LegacyModalSetter` | `ModalSetter` |
+| `useModalOld` | removed |
+| `useModalApi` | removed |
+
+## Params
+
+| Old | New |
+| --- | --- |
+| `ParametersReact` | `ParamsEditor` |
+| `ParametersBaseReact` | `ParamsEditorBase` |
+| `ParametersEngine.tsx` | `ParamsEditor.tsx` |
+| `EditParams2` | `ParamsEdit` |
+| `EditParams3` | `ParamsArrayEdit` |
+| `CParameter` | `ParamRow` |
+| `FButton` | `ParamLabelContent` |
+| `FNameButton` | `ParamToggleLabel` |
+| `SetAutoStepForElement` | `setAutoStepForElement` |
+
+## Menu
+
+| Old | New |
+| --- | --- |
+| `MenuBase` | `Menu` |
+| `MenuBaseProps` | `MenuProps` |
+| `tMenuReact` | `MenuItem` |
+| `tMenuReactStrictly` | `MenuItemStrict` |
+| `TimeNum` | `MenuProgress` |
+| `tCounters` | `MenuProgressCounters` |
+| `GetMouseMenuApi` | `createContextMenu` |
+| `mouseMenuApi` | `contextMenu` |
+| `ReactMouse` | `Layer` |
+| `ReactMenu` | `MenuView` |
+| `GetMenuR` | `createRightClickMenu` |
+| `MenuRightApi` | `createRightMenuController` |
+| `DropdownMenuTest` | `RightMenuDemo` |
+
+## Buttons And Grid
+
+| Old | New |
+| --- | --- |
+| `MiniButton2` | `PopupButton` |
+| `MiniButton3` | removed |
+| `AgGridMy` | `AgGridTable` |
+| `AgGridMyProps` | `AgGridTableProps` |
+| `AgGridMyInner` | `AgGridTableInner` |
+| `applyTransactionAsyncUpdate2` | `applyGridRows` |
+| `applyTransactionAsyncUpdate` | removed; use `applyGridRows` or `useAgGrid` |
+| `getUpdateTable` | removed |
+| `getComparatorGrid` | removed; use `numericComparator` |
+| `applyTransactionAsyncUpdate.tsx` | `gridRows.ts` |
+
+
+
+## Cache Helpers
+
+| Old | New |
+| --- | --- |
+| `tDirtyListener` | `DirtyListener` |
+| `IServerSaveBasePromise` | `CacheStorage` |
+| `CSaveToCache` | `BrowserCacheStorage` |
+| `CSaveToLocalStorage` | `LocalStorageCache` |
+| `CacheG` | `browserCacheStorage` |
+| `CacheLocal` | `localStorageCache` |
+| `CacheFuncMapBase` | `createCacheMapWithStorage` |
+| `CacheFuncMap` | `createCacheMap` |
+| `ObjectStringToDate` | `restoreDates` |
+## Public Type Prefix Cleanup
+
+| Old | New |
+| --- | --- |
+| `tToolbarItem` | `ToolbarItem` |
+| `tToolbarConfig` | `ToolbarConfig` |
+| `tToolbarDensity` | `ToolbarDensity` |
+| `tUiListConfig` | `UiListConfig` |
+| `tUiListSource` | `UiListSource` |
+| `tColumnMeta` | `ColumnMeta` |
+| `tColumnsSort` | `ColumnsSort` |
+| `tColumnsConfig` | `ColumnsConfig` |
+| `tMenuStripItem` | `MenuStripItem` |
+| `tReorderOptions` | `ReorderOptions` |
+| `tReorderItem` | `ReorderItem` |
+| `tReorderBoardOptions` | `ReorderBoardOptions` |
+| `tBoardPos` | `BoardPosition` |
+| `tBoardColumn` | `BoardColumn` |
+| `tSettingsSection` | `SettingsSection` |
+| `tThemeMode` | `ThemeMode` |
+| `tMapChangeListener` | `MapChangeListener` |
+| `tCallFuncAgGrid` | `AgGridClassRule` |
+| `tLogsInput` | `LogInput` |
+| `tLogs` | `LogEntry` |
+| `MenuRightPosition2` | `MenuRightVerticalPosition` |
+| `position2` prop/state | `verticalPosition` |
+| `PageLogs2` | `LogsPage` |
+| `logs3.tsx` | `logsContext.tsx` |
+## wenay-common2 Names Used Here
+
+| Old common2 alias | New name used in this package |
+| --- | --- |
+| `GetDblPrecision` / `GetDblPrecision2` | `decimals` |
+| `NormalizeDouble` | `round` |

package/doc/changes/v1.0.35.md

@@ -0,0 +1,26 @@
+# v1.0.35
+
+Date: 2026-07-08
+
+- Changed: Migrated this repository to the published `wenay-common2@1.0.62` naming surface (`Observe`, `listen`, `Replay.replayListen`, `promiseProgress`) and updated matching React docs/tests.
+- Changed: Made `README.md` a documentation index only and added the project rule file plus `doc/changes/` catalog.
+- Reason: Keep the repository aligned with the breaking rename publication and make future AI edits record version-scoped changes consistently.
+- Verification: `npm run build`; `npm run testjest -- --runInBand`.
+- Changed: Updated `wenay-common2` from `1.0.62` to `1.0.64` and refreshed the pulled `doc/wenay-common2*.md` / `doc/NAMING_RENAMES.md` files from the npm package.
+- Reason: `wenay-common2@1.0.63` adds `Observe.createStoreManager` / `Observe.managedStore` for declarative mirror/replay/offline startup; `1.0.64` packages documentation and recent-change notes into npm.
+- React impact: no required hook migration in `wenay-react2`; the new manager remains a common2 resource-planning layer, while React hooks can keep wrapping concrete stores/remotes.
+- Changed: Applied a breaking `wenay-react2` naming cleanup across public exports, internal imports, docs, and source filenames; added `doc/WENAY_REACT2_RENAMES.md`.
+- Reason: Remove old compatibility aliases and make the package surface concise (`kit`, `memoryCache`, `FloatingWindow`, `ParamsEditor`, `Menu`, `AgGridTable`, `applyGridRows`).
+- Verification: `npm run build`; `npm run testjest -- --runInBand`.
+- Changed: Added a style/token audit, QA stand note, and cleanup inventory to doc/wenay-react2-rare.md; added project rules requiring rare-doc updates for style/theme/cleanup decisions.
+- Changed: Updated the QA stand Vite middleware from the removed `ObserveAll2` name to the current `Observe` export from `wenay-common2`.
+- Reason: Make style normalization and suspected-trash decisions explicit without deleting public exports blindly, and keep the stand runnable after the common2 rename publication.
+- Verification: `npm run testReact -- --host 127.0.0.1 --port 3002` starts and `http://127.0.0.1:3002/` returns HTTP 200; `npm run build`; `npm run testjest -- --runInBand`.
+- Changed: Refactored `contextMenu` around explicit `openAt` / `close` / `getState` controller methods while keeping the old `map` as a legacy Layer queue; updated QA/demo/logger callers to use `openAt`.
+- Changed: Made `DropdownMenu` trigger glyph/content, class names, and inline style slots configurable (`trigger`, `classNames`, `styles`) instead of hardcoding all right-menu visuals.
+- Changed: Updated both `doc/wenay-react2.md` and `doc/wenay-react2-rare.md` to describe `contextMenu.openAt` as the primary right-click integration path and `contextMenu.map` as legacy.
+- Reason: Make the right-click path more logical and reduce visual lock-in from the shared library while preserving current default behavior.
+- Verification: `npm run build`; `npm run testjest -- --runInBand`; QA stand `http://127.0.0.1:3002/` returns HTTP 200.
+- Changed: Removed pulled `wenay-common2` docs from the README/project-rules canonical documentation list; `wenay-react2` docs now remain the only local docs that agents should update for this package.
+- Reason: `wenay-common2` is an external dependency and its current docs should be read from the installed module/package; this repo should only record React-facing impact in `doc/wenay-react2.md` and `doc/wenay-react2-rare.md`.
+- Verification: documentation-only update.