sn-ppt-workbench

1# sn-ppt-workbench
2 
3Start or reuse the AI PPT editing WebUI for an existing HTML slide deck. The
4helper prefers Hermes/canvas/port-forward URLs when available. Without a
5forwarded URL, native hosts bind to localhost by default, while Docker/WSL bind
6to `0.0.0.0` so remote users can reach the WebUI through the host network.
7 
8## Use Cases
9 
10- The user already generated a deck and asks to open the WebUI/editor/workbench.
11- The user provides a `deck_dir` containing `task_pack.json`,
12  `slides/slide_NN.html`, `pages/page_NNN.html`, or a root-level HTML deck.
13- The user says to inspect or edit previously generated slides without regenerating them.
14 
15## Hard Rules
16 
171. Do not run `sn-ppt-entry`, `sn-ppt-standard`, `page-html`, `batch-page-html`, or `export`.
182. Do not edit slide files directly. The WebUI handles user-visible editing.
193. If `deck_dir` is missing, auto-detect only under `$(pwd)/ppt_decks`.
20   Other roots are considered only when the caller explicitly passes
21   `--search-root`; never scan home folders by default.
224. If no usable deck is found, ask the user for the absolute `deck_dir`.
235. Workbench startup is best-effort. If it skips or fails, report the reason and do not attempt generation as a fallback.
246. Prefer a forwarded/canvas URL over localhost when the user may be on SSH, IM, or another remote device.
257. When launched from the unified PPT flow, use the exact absolute
26   `task_pack.deck_dir`; opening the Workbench must not create or switch tasks.
27…