| 1 | # Library Assets DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own small browser-side helper scripts outside the main WebUI module tree. |
| 6 | - Keep injected browser automation assets stable and narrowly scoped. |
| 7 | |
| 8 | ## Ownership |
| 9 | |
| 10 | - `browser/` contains scripts used by browser automation and DOM extraction flows. |
| 11 | - Main WebUI code belongs under `webui/`. |
| 12 | |
| 13 | ## Local Contracts |
| 14 | |
| 15 | - Browser helper scripts must not depend on unavailable bundlers or Node build steps. |
| 16 | - Keep scripts safe to inject into arbitrary pages by minimizing global side effects. |
| 17 | - Do not collect secrets or page data beyond what the calling tool explicitly needs. |
| 18 | |
| 19 | ## Work Guidance |
| 20 | |
| 21 | - Prefer plain JavaScript with clear inputs and outputs. |
| 22 | - Coordinate DOM extraction changes with browser tools, browser plugins, and tests. |
| 23 | - Avoid adding large third-party libraries here. |
| 24 | |
| 25 | ## Verification |
| 26 | |
| 27 | - Run browser-agent or browser-tool regression tests after changing browser helper scripts. |
| 28 | - Manually smoke-test browser flows when tests do not cover the changed path. |
| 29 | |
| 30 | ## Child DOX Index |
| 31 | |
| 32 | No child DOX files. |