diff --git a/docs/reference/file-map.md b/docs/reference/file-map.md index 463c5ac..5871c2a 100644 --- a/docs/reference/file-map.md +++ b/docs/reference/file-map.md @@ -300,6 +300,7 @@ Wave 9 adds these: ```bash python tests/export_check.py # CR-008/CR-017 - export walk + hours guard 20 checks +python tests/sample_check.py # S7 - one sample affordance, confirmed+fenced 10 checks ``` **Three probes were re-pointed at `T7.1`.** `sections_check.py` 5b drove the live diff --git a/html/work-package-suite-app.js b/html/work-package-suite-app.js index 74b14df..74a5e31 100644 --- a/html/work-package-suite-app.js +++ b/html/work-package-suite-app.js @@ -391,95 +391,14 @@ function initializeWPTypes(){ } // ── LOAD SAMPLE DATA ────────────────────────────────────────────────────────── -// This page's sample is the sample SOP. It used to reach into the frame and call -// the creator's loadExample() when the WP tab was open; the creator is its own -// page since T7.1 and carries its own sample controls in its toolbar (D1), so -// there is nothing to reach into and nothing to duplicate here. -// -// S7 still counts more sample affordances than it should. T9.4 reduces them; this -// task only stops one of them pretending to belong to a document it is not in. -function loadSampleData(){ - if(currentTool && currentTool !== 'sop'){ - wizardToast('The work package sample is on the Work Package Creation page, in its toolbar.', - {role: 'status'}); - return; - } - // Populate Step 1 - document.getElementById('proj_name').value = 'MICRON_PH1_CUP_HPM_FMCS INSTALL'; - document.getElementById('proj_number').value = '26-67-008'; - document.getElementById('proj_client').value = 'Micron Technology, Inc.'; - document.getElementById('proj_division').value = 'Semiconductor'; - document.getElementById('proj_site').value = 'Boise, ID — Fab 7'; +// Removed at T9.4 (S7). This was the affordance one click from live project +// data: it filled the wizard state that completeSOP() pushes to the PROJECT, +// with no confirm and no undo. The suite's one sample control lives on the +// creator's toolbar, where it fills that page only. The location and material +// list steps keep their "Load sample values" buttons - those fill a PASTE BOX +// that acts only through an explicit, dry-runnable Import, which is a +// different thing from loading sample data into a live configuration. - // Populate Step 2. The leadership slots are account pickers now, so the sample's - // fictional names can't be "selected" — setting .value on a