Falling Leaves paired motion; OrganicArt finite startup blocker
Run scratch/runs/20261118-fallingl-oasaver-paired-moving-scenes/ personally
reviewed and reused two accepted original Falling Leaves moving pairs. Two
fresh OrganicArt originals, one per backend, closed UNKNOWN at the unchanged
prebinding deadline. Two of four requested pairs are reviewed; OrganicArt
motion remains open. No measured renderer defect or production repair was
established. No original was replayed after closure.
| Registration / actual route | Selected evidence | Finding |
|---|---|---|
scr_fallingl, WAT software, cooperative |
20261107-graphics-saver-motion/retrieved/motion-software-scr_fallingl-coop/scene-30s.png and scene-60s.png |
Gold/green leaves rotate and move across fixed printed leaf motifs; offset shadows move. |
scr_fallingl, owning browser WebGL, cooperative |
Same historical run, motion-webgl-scr_fallingl-coop/scene-30s.png and scene-60s.png |
Leaves and shadows change position and orientation against the same backdrop; actual owning draws 141→279 and flips 12→23, errors/fallbacks zero. |
scr_oasaver, software requested, guest Worker |
Fresh oasaver-software/terminal.json |
No completed presentation admitted within 15 seconds; no baseline or PNG. Actual completed executor identity remains unknown. |
scr_oasaver, WebGL requested, guest Worker |
Fresh oasaver-webgl/terminal.json |
Same finite startup blocker; no baseline or PNG. Actual completed executor identity remains unknown. |
The four selected Falling Leaves PNGs are complete, lossless 1100×820 images,
copied byte-for-byte into this run and rehashed. Their scene geometry and native
window metadata agree before/after. Scene-only changes number 85,386 software
and 48,562 WebGL pixels; visual object/background review establishes motion.
The direct software route has no owning GPU object; its completed raster draw
count is unknown, not zero. Native D3DRM and D3DXOF observations and instantiated
module receipts are retained in reused-fallingl-pairs.json.
Those accepted historical runs use source
3a006e140abb03641fce5af461c0f404d4bcaebc with their named patches and module
e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467, Chrome
151 and ANGLE Vulkan SwiftShader. They do not test November18 main. The original
runtime inventory and its named gzip are missing locally, as is the old
new-source.patch; the accepted report, named case receipts, source metadata,
dirty patch and selected images remain. Missing custody is explicit rather than
reconstructed from today's inputs. Historical response-body observation gaps
and edge/texture artifacts remain unqualified.
OrganicArt scope and identity
The accepted October30 and November7 OrganicArt reports were read first. Their named original PNGs are absent from the available local run folders; they cannot supply personally reviewed whole moving pairs here. Exactly two fresh local originals were used; no Falling Leaves duplicate was launched.
Dispatch main was 5883f89a504a0bf176083098460facc2c690f017, branch main.
dispatch-relevant.patch records relevant foreign working-tree differences
observed during preparation, with its timestamp recorded independently; those
differences were excluded from execution. The immutable Git runtime was
compiled from that exact commit before either original clock. Retained module
SHA-256 is
eb2395e1c115980dd78dbb646a26f755a4119a2a1e086942e715240e07c34bc6.
Source pins, original media paths/hashes and successful PNG codec construction
precede original launch. There is no source archive or media copy.
The app-specific run script reads released tools/rm-startup-run.cjs from
a373de9ba and replaces only its hardcoded scr_rockroll registration with
scr_oasaver. The released 15-second binding, 300-ms stability, geometry and
generation checks, nonresizing secondary inspection, three-second capture
limit and deferred Debugger inventory remain unchanged. Planned delays were
15/15 seconds after binding; neither scope reached them. Its focused deferred
inventory/error/late-capture closure test passed. No tracked helper, test,
renderer or guard was edited; no code commit or new build acceptance is claimed.
Both originals use ordinary registered OASAVER.SCR /s and all 85 registered
executable/scene entries. Their executable is 1,005,056 bytes, SHA-256
470e28bcbc3cf92c514cd8e8bbf9eae399c59f79ed2adbf7bf2b91d25cfb477c.
Registered Falling Leaves uses identical executable bytes but a distinct scene
manifest. Real Microsoft d3drm.dll is
fd80f3839a035b6b52362735b22eb8d2523d3434bf18afb3e0f1b5ace84357b0;
d3dxof.dll is
1f2d0683668b3039d451d88ed449fd9d49371fab3fadb991636cd6bfb0aa6eee.
All supplied media remain unchanged. Logs record native D3DRM loading,
DllMain success and original import binding, and requests record D3DXOF
delivery. The supplied module hash is verified at HTTP delivery; actual
instantiated byte inventories are deliberately empty because UNKNOWN closed
both scopes before deferred inventory. No postclosure query recovered them.
Both scopes created a live 640×480 Screen Saver window and observed startup canvas/presentation geometry changing while the viewport remained 1280×960. Every retained readiness sample is false. The guard therefore did not establish a completed PRESENT plus stable composition within its original 15-second interval. These observations cannot distinguish slow native scene construction, presentation starvation or another startup cause. No blank image is accepted, no bound scope is rebaselined, and no deadline is extended. Missing optional UI/type-library resources and same-directory D3DXOF probes remain logged; their presence alone does not establish this timeout's cause.
Historical corrections and cleanup
The October10 lit-material alpha correction remains authoritative: the old claim that opaque black leaf shadows were intended was wrong. The November3 paired shadow-alpha report separately validates original alpha127 and source alpha blending; this task does not repeat that diagnostic. Registered CLI 2-ms scene-clock policy and the historical device-rebuild/blank-surface corrections remain intact; browser wall time and CLI batches are distinct.
OrganicArt's historical white rectangle is associated with the native missing
CALogo.gif path. Native logo-disable/substitute diagnostics do not recover
authentic installation defaults. The older single “box gone” picture does not
establish a permanent renderer repair. This task obtained no OrganicArt image
and adds no current rectangle observation. Authentic intended logo appearance
still requires matching Plus!98 installation assets/metadata; Windows reference
correctness would require an owner-provided real Windows VM run.
Both fresh scopes have actual native/browser command waits, separate stdout
and stderr EOFs, independent finite-watchdog waits, native-supervisor
leaked:false, absent/dead owned PIDs and closed listeners. Independent finite
supervision uses native-supervise.cjs; worker-owned disk monitoring stayed
above 1.5 GB with no RAM gate. No guest input or native Quit claim. Neither
closed original received later endpoint requests or a replay. Recovery uses
Git, the recorded patches/transformation scripts, retained module and existing
hashed media paths. Artifacts precede final result.json.
Box ID null, state NOT_CREATED, expiry null, stop receipt null. No boxes,
workers, Python, Wine or public deployment. Ownership is released after report
publication. Backend parity, FPS, audio, full saver cycles, visual correctness
and complete historical27 membership remain open.