T5.5 - CR-006: section toggles, and X4 resolved rather than deferred

X4 first, because the brief asks for it explicitly.

IMPLEMENTATION.md sequences CR-006 after B7 on the grounds that the toggles must
suppress sections inside the creator, which is an iframe child until T7.1. The
wave file puts it in wave 5 anyway, and its last done-when is written to
accommodate exactly that: "toggle state propagates into the creator, OR the PR
documents exactly where it does not and why".

It propagates. Both ways, by two separate paths, because they fail differently:

  ON THE CREATOR'S OWN BOOT the flags ride on the SOP, which the creator already
  reads - ProjectData.pullProject hydrates it from the server. Nothing crosses
  the frame boundary at all, so this path is unaffected by B7 either way. It
  covers a reload, a fresh tab, the standalone creator page, and a colleague
  opening the project on another machine.

  WHILE THE FRAME IS OPEN the wizard hands the change straight across
  (pushSectionsToCreator -> cw.applySopSections), the same shape T5.3 used for
  the dashboard filter. Without it, flipping a toggle would appear to do nothing
  until a reload.

T7.1 removes the second path, not the first. That is the whole of the X4
exposure and it is one function, commented as such. Building CR-006 after B7
would not have made the SOP-borne path any different; it would only have saved
writing the hand-off.

What it does

  Ten sections, one shared list (html/wp-sections.js) read by the wizard, the
  creator's form and the creator's rendered document. Three surfaces meant three
  chances to drift, which is how "Assets is off, except in the export" happens.

  Off means NOT RENDERED - form, detail view and PDF export. It never means
  deleted. renderPackage() was rebuilt from one long string into a list of
  (section, html) blocks so a suppressed section leaves no empty heading and the
  survivors renumber 1.0, 2.0, 3.0 instead of leaving a hole. The print window
  reuses that same HTML, so the export needed no separate change.

  Absent means ON. A SOP saved before today mentions no sections, and reading
  that as "all off" would blank every project in the estate the moment this
  shipped. WPSections.normalize is the one place that decision lives.

  html/wp-sections.js               new - the shared list, defaults, normalize
  html/work-package-suite.html      step 12, a 12th rail button
  html/work-package-suite-app.js    the toggles, state.sections, the hand-off
  html/work-package-suite-styles.css the toggle rows
  html/wp-creation-index.html       stable ids on the five unnamed cards
  html/wp-creation-app.js           WP_SECTION_NODES, applySopSections,
                                    renderPackage rebuilt as blocks
  tests/sections_check.py           new - 53 checks

Done when
  [x] all 10 sections are toggleable - each one driven off and back on
  [x] a section toggled off is absent from the form, the detail view and the
      PDF export - checked by content marker, not by heading, so "the section
      is gone" and "the section was empty" cannot be confused
  [x] toggling off then on restores prior data with no loss - and the sharper
      version: a package EDITED while Assets is off still carries its assets
      through collectPackage(), which is what Save uses
  [x] new SOPs default to all sections on
  [x] toggle state propagates into the creator - both paths, separately

Two things worth arguing with

  General Information is toggleable, because CR-006 enumerates it. Turning it
  off leaves nothing to identify a package by. The row says so in its own note
  rather than being quietly excluded from the list.

  Location has no card of its own - it is a field inside General Information's
  grid, and its toggle governs that one row. CR-004 gives it structured
  building/floor/sector fields in wave 6, at which point one line of
  WP_SECTION_NODES changes. Written down because "the toggle does nothing" and
  "the toggle governs one row" look identical from outside.

  Approvals & Sign-offs is NOT toggleable and is not one of the ten. A package
  nobody signed is not a shorter package.

Verified one at a time
  sections_check  53/53  new
  stepper_check   70/70  (STEP_COUNT 11 -> 12)
  locations_check 58/58  (its "step 11 is last" check now asserts the thing that
                          is actually invariant - the wizard's navigation follows)
  browser_check   71/71
  a11y            22/22
  url_state       23/23
  autosave        34/34
  aggregates      16/16
  pipeline        43/43
  launcher        58/58
  f_items         F1-F5 FIXED, F6 REPRODUCES (T7.2)

No colour literal added: still 0 across all page sheets and inline blocks. Each
toggle says its state three ways - the checkbox, the words "In use" / "Not used",
and the rule down its left edge (C1).

Question for the PR, per CLAUDE.md: the toggles are SOP-wide, so a project
cannot use Kitting on install packages and not on BIM ones. BL-000b already
records the field-level version of this question; the per-WP-type version is the
same shape and is not recorded anywhere yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

html/work-package-suite-app.js

@@ -36,6 +36,11 @@ let state = {
   signoffRoles: [{role:'Superintendent',name:''},{role:'Foreman',name:''}],
   wpTypes: [],
   governance: {woformat:'', wosize:'', issuance:[], disciplines:['Mechanical','Electrical','Tech'], discMode:'choice', instanceSuffix:'letter', sizeHoursMax:''},
+  // CR-006: which work package sections this project uses. Present from the start
+  // rather than filled in lazily, because sopIsDirty() fingerprints this object —
+  // adding a key on first read would make merely LOOKING at step 12 count as an
+  // unsaved change and fire T4.3's guard on the way out.
+  sections: (typeof WPSections !== 'undefined') ? WPSections.defaults() : {},
   quality: {qcreq:'', photo:'', hold:''},
   platforms: {tracking:'CxAlloy', commissioning:'CxAlloy', trackingUrl:'', commissioningUrl:''},
   sequence: [],
@@ -458,6 +463,11 @@ function restoreSavedSOP(){
   state = savedState;
   sop = savedSop;
   sopComplete = true;
+  // A SOP saved before CR-006 mentions no sections, and "says nothing" has to
+  // mean every section is on — the alternative would switch them all off for
+  // every project in the estate. Normalised HERE, before the dirty fingerprint
+  // is taken, so filling the gap does not read as an edit.
+  if(typeof WPSections !== 'undefined') state.sections = WPSections.normalize(state.sections);
   // A SOP saved before the team was account-backed has no teamIds; default them
   // so the pickers render (the stored names show as "(no account)" until linked).
   if(!state.teamIds) state.teamIds = {pm:'', apm:'', cm:'', qm:''};
@@ -1501,6 +1511,93 @@ document.addEventListener('DOMContentLoaded', function(){
   }
 });
 
+// ── STEP 12: WORK PACKAGE SECTIONS (CR-006) ───────────────────────────────────
+// Which sections of a work package this project uses. The list itself lives in
+// wp-sections.js, shared with the creator so the two cannot disagree about what
+// "Assets is off" means.
+//
+// Toggling a section OFF never deletes anything — it stops the section rendering,
+// in the form, in the package and in the export. Whatever was captured stays on
+// the package and comes back intact. That is the difference between this and
+// removing a field, and it is the reason CR-002 and CR-016 are expressed here.
+function sopSections(){
+  if(typeof WPSections === 'undefined') return {};
+  state.sections = WPSections.normalize(state.sections);
+  return state.sections;
+}
+
+function renderSectionToggles(){
+  const host = document.getElementById('section-toggles');
+  if(!host || typeof WPSections === 'undefined') return;
+  const on = sopSections();
+  host.innerHTML = WPSections.LIST.map(sec => `
+    <label class="section-toggle${on[sec.id] ? '' : ' is-off'}" for="sec-${escAttr(sec.id)}">
+      <input type="checkbox" id="sec-${escAttr(sec.id)}" data-section="${escAttr(sec.id)}"
+             ${on[sec.id] ? 'checked' : ''}>
+      <span class="section-toggle-body">
+        <span class="section-toggle-name">${escAttr(sec.label)}</span>
+        <span class="section-toggle-note">${escAttr(sec.note)}</span>
+      </span>
+      <span class="section-toggle-state">${on[sec.id] ? 'In use' : 'Not used'}</span>
+    </label>`).join('');
+  renderSectionSummary();
+}
+
+function renderSectionSummary(){
+  const el = document.getElementById('section-summary');
+  if(!el || typeof WPSections === 'undefined') return;
+  const off = WPSections.offList(sopSections());
+  el.textContent = off.length
+    ? `${off.length} section${off.length===1?'':'s'} turned off: ${off.join(', ')}. `
+      + 'Their data is retained and returns if they are turned back on.'
+    : 'Every section is in use. Turn off anything this project does not need.';
+}
+
+document.addEventListener('DOMContentLoaded', function(){
+  const host = document.getElementById('section-toggles');
+  if(!host) return;
+  host.addEventListener('change', function(e){
+    const t = e.target;
+    if(!t || !t.dataset || !t.dataset.section) return;
+    const on = sopSections();
+    on[t.dataset.section] = !!t.checked;
+    const wrap = t.closest('.section-toggle');
+    if(wrap){
+      wrap.classList.toggle('is-off', !t.checked);
+      const st = wrap.querySelector('.section-toggle-state');
+      if(st) st.textContent = t.checked ? 'In use' : 'Not used';
+    }
+    renderSectionSummary();
+    // The creator may already be loaded in the frame next door. Hand the change
+    // across rather than waiting for a reload — see pushSectionsToCreator.
+    pushSectionsToCreator();
+  });
+});
+
+// X4, the sequencing note this task had to resolve: the creator is an iframe
+// child until T7.1, so the SOP it reads is the one hydrated into localStorage by
+// ProjectData.pullProject at ITS boot. A toggle flipped in the wizard afterwards
+// is invisible to an already-loaded frame.
+//
+// Two paths, therefore, and both are needed:
+//   • on the creator's own boot, applySOP() reads SOP.sections — this covers a
+//     reload, a fresh tab, and the standalone creator page;
+//   • while the frame is open, this hands the change straight across, the same
+//     way T5.3 hands the dashboard filter across.
+// What T7.1 removes is the second path, not the first.
+function pushSectionsToCreator(){
+  const frame = document.getElementById('wp-frame');
+  if(!frame) return false;
+  try {
+    const cw = frame.contentWindow;
+    if(cw && typeof cw.applySopSections === 'function'){
+      cw.applySopSections(sopSections());
+      return true;
+    }
+  } catch(e){ /* cross-document timing; the creator picks it up on its next boot */ }
+  return false;
+}
+
 // ── STEP GATES (A4 / S9) ──────────────────────────────────────────────────────
 // validateStep() guarded steps 1, 5 and 6 with three hand-written conditions and
 // three hand-written messages. The rail needs the same answer for every step, not
@@ -1526,8 +1623,8 @@ const STEP_GATES = {
 
 const STEP_LABELS = {1:'Project', 2:'Team', 3:'Sign-offs', 4:'WP types', 5:'Governance',
                      6:'Quality', 7:'Platforms', 8:'Sequence', 9:'Constraints', 10:'Sources',
-                     11:'Locations'};
-const LAST_STEP = 11;
+                     11:'Locations', 12:'Sections'};
+const LAST_STEP = 12;
 
 // Steps you have actually been on. A stepper's tick means "done", and a step you
 // have never opened is not done however its defaults happen to read — step 6's QC
@@ -1771,6 +1868,7 @@ function updateStepUI(){
   // actually opened rather than on every page load. locLoad() is idempotent and
   // no-ops once it has the list.
   if(currentStep === 11 && typeof locLoad === 'function') locLoad();
+  if(currentStep === 12 && typeof renderSectionToggles === 'function') renderSectionToggles();
 
   // Update buttons
   document.getElementById('sop-prev-btn').disabled = currentStep === 1;
@@ -1913,6 +2011,9 @@ function completeSOP(){
       state.platforms.trackingUrl ? {label:'Tracking — '+state.platforms.tracking, system:state.platforms.tracking, url:state.platforms.trackingUrl} : null,
       state.platforms.commissioningUrl ? {label:'Commissioning — '+state.platforms.commissioning, system:state.platforms.commissioning, url:state.platforms.commissioningUrl} : null
     ].filter(Boolean),
+    // CR-006. Rides on the SOP because the creator already reads the SOP: this is
+    // what makes the toggles reach a work package without a second channel.
+    sections: (typeof WPSections !== 'undefined') ? WPSections.normalize(state.sections) : {},
     quality: {
       qcReq: state.quality.qcreq,
       photo: state.quality.photo,