diff --git a/docs/reference/file-map.md b/docs/reference/file-map.md index cd5978c..96d53e1 100644 --- a/docs/reference/file-map.md +++ b/docs/reference/file-map.md @@ -21,14 +21,6 @@ roughly 11,900 lines" — the line count is right, the other two are not. See D1 | `html/login.html` | login | 163 | `theme-light.css` | `login.js` | neither | | `html/index.html` | launcher | 703 | `theme-light.css`, `wp-chrome.css` | `auth-guard`, `wp-format`, `feedback-config`, `project-data`, `help`, *(inline 418–700)*, `wp-chrome` | neither | | `html/work-package-suite.html` | SOP wizard | 437 | `theme-light.css`, `wp-chrome.css`, `work-package-suite-styles.css` | `auth-guard`, `wp-format`, `feedback-config`, `project-data`, `help`, `work-package-suite-app`, `wp-chrome` | **hosts** | - -> **The SOP wizard has 11 steps, not 10, since `T5.4`.** `CR-005`'s location list was -> **appended** as step 11 rather than inserted beside Project, where it belongs by -> subject: renumbering 2–10 would touch every `sop-step-N` id, every `collectStepData` -> case, every gate key and the analytics history, for an ordering change. The count -> lives in one place — `LAST_STEP` in `work-package-suite-app.js` — and reordering is -> cheap once nothing depends on the numbers. `tests/stepper_check.py` names it -> `STEP_COUNT` for the same reason. | `html/wp-creation-index.html` | creator | 401 | `theme-light.css`, `wp-creation-styles.css` | `auth-guard`, `wp-format`, `feedback-config`, `project-data`, `help`, `wp-creation-app` | **child** | | `html/admin.html` | admin | 219 | `theme-light.css`, `wp-chrome.css`, `console.css`, `wp-sidenav.css` | `auth-guard`, `wp-format`, `console-util`, `admin`, `wp-chrome`, `wp-sidenav` | neither | | `html/users.html` | directory/users | 106 | `theme-light.css`, `wp-chrome.css`, `console.css`, `wp-sidenav.css` | `auth-guard`, `wp-format`, `console-util`, `users`, `wp-chrome`, `wp-sidenav` | neither | @@ -38,6 +30,18 @@ No script anywhere in `html/` uses `defer`, `async`, or `type="module"`. Every o render-blocking classic script. `auth-guard.js` and `wp-format.js` load in ``; the rest load at the end of ``. +Wave 5 added two `` scripts, both shared: `wp-sections.js` (the `CR-006` section list, +read by the wizard *and* the creator, so the two cannot disagree about what "Assets is off" +means) joins `wp-url.js` and `wp-autosave.js`. + +> **The SOP wizard has 12 steps, not 10, since wave 5.** `T5.4` appended Locations (11) and +> `T5.5` appended Sections (12). Both were **appended** rather than inserted where they +> belong by subject: renumbering 2–10 would touch every `sop-step-N` id, every +> `collectStepData` case, every gate key and the analytics history, for an ordering change. +> The count lives in one place — `LAST_STEP` in `work-package-suite-app.js` — and reordering +> is cheap once nothing depends on the numbers. `tests/stepper_check.py` names it +> `STEP_COUNT` for the same reason. + ### The iframe boundary (matters for `B7` / `T7.1`) `work-package-suite.html:383` declares `