Bone Flow #119 State Package Version: 1.0.26 Status: Development Candidate Runtime: BoneState 1.0.0 HTML Functional Class Runtime: 1.0.4 HTML Functional Class: bf-state Install target: C:\work\pcsr\pcsr.net\public\boneflow Confirm URL: http://localhost/boneflow/test/bone-state.html Scope: - #119 standalone package only. - Cumulative regression runner is NOT bundled and is NOT modified. - index.html is NOT bundled and is NOT modified. - #001/#002/#017/#040/#116/#117/#118 files are NOT bundled and are NOT modified. - BoneState Runtime 1.0.0 and bf-state Functional Class Runtime 1.0.4 are retained byte-for-byte from the uploaded candidate after independent Node contract verification. v1.0.26 rebuild: - OUT WAIT / FIFO / BLOCKED now follows the actual #017 reference flow: one visible #002 Joint stage, WAIT / FIFO execution, automatic READY restoration after 650ms, FIFO delivery, BLOCKED execution, and Reset. The rejected manual Target READY redesign is removed. - Joint display layers follow the formal order: line z-index 1, Component nodes z-index 2, #002 WAIT/BLOCKED marker z-index 3. - State Relation error cards keep real #002 drawError markers and reserve additional marker/target spacing. - Untrusted IN / Security Test keeps the isolated #119 Security State, uses real #002 drawError, and reserves a wider Gate/Target marker gap so the formal X marker does not collide with nodes. - Property language control uses the formal "Property 表示言語 / 日本語 / English" presentation. - HTML Functional Class detail is kept in the Operation Guide; the page uses a compact live sample and bottom class bar. - State Relation Image uses #002 Bone Joint v1.1.36 evaluate/drawLine/drawError instead of CSS pseudo-lines. - Security Test remains isolated from normal Preview and uses #002 Bone Joint for its relation path and BLOCK error marker. - OUT WAIT/FIFO/BLOCKED remains delegated to the #002 Joint delivery channel and uses official Joint WAIT/BLOCKED markers. - Smoke/Validation uses the formal control/status IDs used by the cumulative runner: run-smoke-test, run-validation, run-all-tests, clear-test-results, smoke-status, validation-status. - The stale blocked.banCount Smoke condition from the prior candidate was removed; the real #002 .bf-joint-blocked-ban marker count remains the check. - No fixed PASS, skip, FAIL ignore, runner shim, runner timeout workaround, or cumulative runner special case is included. QA status at package build: - BoneState Node contract: executed separately. - bf-state Node contract: executed separately. - JavaScript syntax / HTML inline JavaScript syntax / duplicate id / DOM id reference / ASCII control / package version / MANIFEST / ZIP integrity / re-extract checks are package-build gates. - Headless Chromium Completion DOM regression: PASS (Complete -> Reopen -> Complete). - Windows PowerShell 5.1 actual execution: NOT EXECUTED in the build environment. - User localhost Browser Smoke/Validation: NOT CONFIRMED. ZIP root: install.bat install.ps1 boneflow\... v1.0.26: Component Completion now follows the working current-page pattern: Complete -> Reopen -> Complete is supported without localStorage/package completion persistence, and the actual DOM sequence is regression-tested.