# Project State ## Issue #20 workflow persistence hotfix (2026-09-10) - User authorized repair and publication to main from pinned 6b453fe. The only runtime change is `serialize: false` on the read-only Render History widget in `web/project_id.js`; existing `options.serialize: false` is retained. Backend widget order, Sampling, Audio, Run Storage, public workflow/ZIP bytes, and Easy Loader Bypass behavior are unchanged. - Added a regression using the real Continuum frontend script with modeled compact store persistence and forceInput migration. It covers ordinary serialization, store serialization, positional/named round trips, Advanced/Review/History/completion views, and API-input parity. It fails on the unmodified runtime; all 45 pre-existing fixture cases remain green. Full CPU pytest: 1154 passed, 2 skipped; frontend fixture: 46/46 passed. - Validation ran on an isolated GitHub Actions CPU runner after byte-verified snapshots made with `tools/snapshot.ps1`. This is not a real-browser or GPU validation. Windows source/runtime and saved Takes were not accessed or changed. Existing corrupted workflows need separate recovery; model/VAE/LoRA reset reports and the separate Bypass issue remain unverified. No Release/tag or Registry publication. Fixed H3情報チェック cross-task handoff was not sent from this session. ## Review boundary repair — CPU validated, live 3x5 pending (2026-09-08) - The latest actual Review Queue did not generate Chunk 1: backend history proved it reused all three saved chunks and returned the prior `complete` revision. The previous mode-selection presentation repair therefore did not satisfy the user's acceptance condition and is superseded by this entry. - Source now treats an explicit Full Video -> Review Each Chunk selection as a new non-destructive review series. Before Queue it refreshes canonical Run Storage state; when saved `review_ready` or `complete` history exists, only the queued payload receives `Regenerate From = Chunk 1`, automatic nonce, and no Take selection. The visible settings and saved Takes remain unchanged. The first actual Sampler result releases setup mode and loads its canonical review state; later Continue queues inherit that new branch and advance one physical group at a time. - Exact CPU contracts cover `3 x 5s`: fresh Chunk 1 -> review, Continue -> Chunk 2 review, Continue -> Chunk 3 complete. The real frontend lifecycle and backend branch/nonce resolver pass. Focused Review/UI suite `123` PASS and full CPU suite `1156/1156` PASS in `50.69s`; Registry/source declarations, JavaScript syntax and `git diff --check` pass. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-review-boundary-20260908`. - Fixed H3情報チェック returned `PASS / local runtime deploy OK`; its nonblocking queued-identity note was applied by binding setup release to the exact setup token and Run name. Installed ComfyUI_W still has the superseded frontend SHA `d84877206cc1142dbfe7fce3f7e9c1b6edb8a22cae5ab117a1407f9435f6dea7`; validated source SHA is `fe5e00020b9e942ec2e27286576aca69fb3add3f18afeea8edcfd28f6183cd91`. Runtime deployment, browser refresh and actual GPU `3 x 5s` Chunk1/2/3 screen acceptance remain pending. No workflow, Production/Sampling backend, saved Take, commit, push, tag or release change. ## Local Review mode-selection repair (2026-09-08) - Deployed locally after H3情報チェック returned PASS / local deployment OK (report-only review). Source, installed web/project_id.js and live8188 HTTP200 payload SHA all equal d84877206cc1142dbfe7fce3f7e9c1b6edb8a22cae5ab117a1407f9435f6dea7. Runtime snapshot verified1 file. Browser hard-refresh and user-visible check remain; no browser reload, GPU, backend restart or publication performed. This supersedes deployment-pending wording below. - User-reported Full Video -> Review Each Chunk opened an old complete revision before generation. Reproduced with the real frontend harness (red.xml); mode selection now retains setup and the normal readiness summary without showing Retry/Restart. Existing Return to Review explicitly opens the saved result. Saved progress remains reusable; selecting Review does not mean starting a new Run. - Presentation token is transient, not serialized or a backend identity. A matching queued generation's new review revision releases it; same-revision history reads, delayed initial history before Queue, a previously queued result, or another Run's result do not take focus. Hidden old Retry/Finish is normalized to ordinary Continue at Queue while manual boundaries remain intact. Reload recovery, review completion, saved takes, Python and workflow bytes remain unchanged. - Focused90 PASS; final full1155 PASS in48.44s, CPU-only. Initial full had one old UI fixture failure: it injected a ready revision without Queue; fixture now models queued completion and keeps its prior expectations. Evidence: D:/Codex/_test_results/ComfyUI-H3-Continuum/v38-mode-settings-20260908. Completion report sent to fixed H3情報チェック; local deployment/readback pending that review. No commit/push/GPU or backend restart authorized/performed. ## Review UI hotfix — validated for user-authorized main publication (2026-09-08) - User explicitly authorized a hotfix commit/push to existing origin/main for the confirmed Xarfai Review restart UI mismatch. Scope is frontend only: withdraw stale review actions after settings edits, preserve manual regeneration boundaries, add a non-destructive one-shot Start again from Chunk 1 button. Saved takes, sampler/transport/Audio/schema/workflow files and installed runtime remain unchanged. - Browser-side edit detection only withdraws stale actions; it does not approve saved-prefix reuse. Existing Run Storage compatibility checks remain authoritative. The separate 15-second Review chunk2 static/noise report is unresolved and is explicitly excluded from the hotfix claim. - Related pre-fix diagnostic evidence: D:/Codex/_test_results/ComfyUI-H3-Continuum/v38-xarfai-review-20260908/FINDINGS.md. New validation/publication evidence: D:/Codex/_test_results/ComfyUI-H3-Continuum/v38-review-hotfix-20260908. Initial source snapshots: nine verified one-file snapshots under before-review-hotfix-*. Final checks and publication result are recorded in WORKLOG and the task response. - Final full guarded CPU suite1155/1155 PASS (46.62s), focused61 PASS, Registry105/105 and source declaration256/256 hashes match. All guarded processes exited CUDA-uninitialized, zero blocked initialization calls. Final additions cover delayed history response and queued-baseline isolation between Run Names. User authorized waiving the external review once due delayed delivery; the fixed H3情報チェック reply subsequently arrived with PASS / PUSH TO MAIN OK. Non-blocking review note: keep revision updated_utc tied to backend writes, not ordinary history reads. No GPU or Registry/tag/release-asset publication. ## Main publication preparation (2026-09-07) - User explicitly approved commit/push to existing origin/main, then prioritized immediate README/file upload after announcing on Civitai and requested no further workflow tests. Publish the current Spectrum graph as MiniMax_H3_Continuum_V38.json and its matching ZIP, unchanged: JSON SHA e490c87e4995930f95c8fffc4c678111d7897e74003e1962b9b4a247ba43f4ac; ZIP SHA 83d28cc0cd549066962dc21ceae05d2b189fe22391b556887eab2cc1800e1e80. README, migration, package declarations and tests now describe one graph in two formats requiring Spectrum/rgthree/KJNodes/Easy Use. No separate Turbo graph and no prompt/media/title cleanup. - English and Japanese READMEs link JSON/ZIP and LightX2V near the top with git clone/pull instructions. Git exact-byte attributes prevent automatic EOL conversion from invalidating file hashes. Historical V3.7 ZIP remains a source regression fixture; unrelated node.zip and external backup archives are not publication payload. - Publication audit initially ran 1,155 tests: 1,154 passed; the real-Core CPU cache subprocess stopped at optional SageAttention import requesting CUDA capability. Initialization was blocked. The CPU cache harness now models that optional package as absent in its child process only; installed Core/Sage and Production remain unchanged. Focused rerun is recorded in v38-main-publication-20260907/focused.xml. Do not relabel the initial run as full-suite PASS. No further workflow test runs after the user's stop instruction. - Evidence: D:/Codex/_test_results/ComfyUI-H3-Continuum/v38-main-publication-20260907. Source snapshots verified before changes. This is GitHub source publication only, not a GitHub Release/tag or Registry publish. Runtime synchronization and Registry official validate/pack remain separate; user backend and GPU were untouched. ## README accuracy corrections (2026-09-07) - Corrected the English/Japanese README only: insert Core Create Video before Save Video; distinguish automatic nonce0, explicit positive nonce, interrupted resume and review Retry; scope historical compatibility promises to their releases and preserve the exact current seven-node boundary; identify Audio Switch as Core; align Japanese Advanced/Manual visibility guidance; separate the latest CPU1,154/1,154 audit from historical V3.6/GPU acceptance. - Refreshed only README-related hashes in Registry (104/104 matched) and source Manifest (254/254 matched). Final focused CPU regressions90/90 PASS; initialization tripwires stayed clean. README local links53/53 resolve and Markdown fences/whitespace checks pass. Evidence: D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-readme-correction-20260907. Initial six one-file snapshots verified under before-readme-correction-*-20260907_195135. - No workflow, image, ZIP, generation code, public schema, installed runtime, backend, commit, push or release change. The prior runtime synchronization remains pending separately; documentation checks do not promote release/GPU-quality status. ## CPU release hygiene fixes and ZIP scope correction (2026-09-07) - The previously inspected ZIP was D:\Codex\_git_push_work\ComfyUI-H3-Continuum\node.zip, not the user's Continuum.zip / Continuum3-8.zip backups. Its distribution role was never established; withdraw the ZIP-based launch blocker. Backup/local ZIPs are excluded from this release check and remain unchanged. The older audit report carries this correction at its top. - Fixed only hardening.format_memory_snapshot's CUDA observation guard: read counters only after CUDA is already initialized. Added three CPU tests for no probe/no tensor or RNG mutation, initialized-counter preservation, and nonfatal diagnostic failure. The real-Core cache test now uses explicit CPU bootstrap, initialization tripwires, and the diagnostic-only Kitchen capability bypass. - Full guarded pytest: 1,154/1,154 PASS in55.60s, zero deselection and zero intercepted initialization calls in recorded guard logs. Focused tests60/60 PASS. Registry104/104 and source Manifest254/254 refreshed for current declared files. No Sampling, Audio, mask, seed, SIGMAS, public schema, workflow, or ZIP change. - Reconstructed105-file Registry payload (104 declared files plus manifest) under D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-cpu-release-fix-20260907\registry_payload, without using or creating a ZIP. Isolated CPU import, public7-node registration, PackedLayout, diagnostics and atomic JSON replacement PASS; CUDA remains uninitialized. - Runtime update plan is a dependency-complete two-file sync of hardening.py and run_storage.py; only added import is stdlib time. One-file snapshots of each installed target verified. Deployment attempted no writes because user queue was running1/pending0. Existing backend remains untouched; disk synchronization is pending an idle queue, and an eventual user-managed restart is still needed for the running process to load the changes. ## V3.8 prelaunch CPU audit (2026-09-07, Release HOLD) - Fresh guarded full suite: 1,149 passed / 2 failed, 1,151 total in 99 modules; no deselection. Failures: stale Registry manifest and real-Core cache test launching without CPU bootstrap. Same cache harness passes all four assertions under explicit CPU/W2 bootstrap; original tests remain unchanged. - Source CPU/Core 0.34.5 probe: all seven public nodes, callable inputs, native PackedLayout and Fixed prompt self-test PASS. V3.8 core workflow 19 nodes/25 links and user Spectrum 32 nodes/38 links pass graph/schema checks; external Spectrum/KJ/Easy/rgthree sockets checked via GET metadata only. Spectrum remains byte-identical to user Downloads SHA E490C87E4995930F95C8FFFC4C678111D7897E74003E1962B9B4A247BA43F4AC. Python226/JS7 syntax PASS. - Historical observations: Registry manifest4/source Manifest7 mismatches before record update (subsequently repaired above). Root node.zip has75 files and an incomplete import, but is not an established distribution artifact and is excluded from the launch verdict. Runtime source diff was functional only in run_storage.py (source-only Windows atomic replacement retry); reference.py and v3/reference_video.py differences are whitespace/line endings with matching AST. - New independent CPU diagnostic finding: hardening.format_memory_snapshot reaches CUDA lazy init through mem_get_info even with Core --cpu when CUDA is available. Full suite blocked14 such calls plus1 Core startup call; standalone CPU diagnostic reproduces. All actual initializations were blocked. No Production/workflow/runtime fix, model load, Sampling, Queue submission, backend restart, commit, push, or publication. - Source README local links exist; 44 references across shipped docs point to non-Registry assets and need GitHub/local-documentation handling. Full report and evidence: D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-prelaunch-cpu-audit-20260907\CPU_PRELAUNCH_REPORT_JA.md. Record-only snapshots before-cpu-prelaunch-audit-state/worklog-20260907_182042 verified1+1 files. CPU wiring PASS does not grant GPU-quality or Release PASS. ## V3.8 Civitai feature infographic (2026-09-07) - Rebuilt the supplied V3.7 feature infographic as a V3.8 Civitai graphic at the exact original `1536x1024` 3:2 landscape format. The new content covers Review Each Chunk, Resume/Regenerate, simplified V3.8 controls, and the shared Spectrum/Turbo graph; it explicitly retains the V3.7 Production foundation and states that Issue #13 remains open. Saved as `docs/images/v38-manual/h3-continuum-v38-whats-new.png` (SHA-256 `5E4B876585FAC3A2D580CDAF99B83EC3E10DA90036B7923B4DFFDCF0240560BD`). No workflow/runtime change. ## Spectrum-only optional V3.8 workflow and top-level Git instructions (2026-09-07) - Added the user-supplied `MiniMax_H3_Continuum_V38_Spectrum.json` to `examples/workflows/` without changing its contents. Source and repository SHA-256 are both `E490C87E4995930F95C8FFFC4C678111D7897E74003E1962B9B4A247BA43F4AC`; its 32 nodes / 38 links parse with zero missing endpoint nodes. - Kept `MiniMax_H3_Continuum_V38.json` as the only dependency-free Registry workflow. The Spectrum graph is a GitHub-source optional workflow and is excluded by the existing Registry packaging rules. No separate Turbo JSON is published; README explains how the same optional graph can switch from its saved Spectrum/20-step state to one task-matched LightX2V Turbo LoRA after Spectrum is disabled. - Added `git clone` and `git pull --ff-only origin main` near the top of the English README and linked the LightX2V/ModelTC GitHub plus Hugging Face project. Per user direction, the Spectrum workflow's empty prompt, media filenames, node titles, widgets, and links were not edited. - Validation: focused release/public workflow tests `11 passed`, with only the existing Registry manifest hash test deselected pending the final package freeze. Snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-spectrum-readme-workflow-20260907_162216`. No commit/push/tag/release. ## English README complete V3.8 UI reference draft (2026-09-07) - Expanded the English README from the Review-only walkthrough into a complete reference for every user-facing socket/control/output on the seven-node V3.8 public surface. It now distinguishes Main, Advanced, Review/Take, three Continuum Settings, loader bypass, First/Last/Reference Image roles, Video Guide, Driving/Reference Audio, Reference Audios, Finalize, and Second Pass. Hidden frontend-managed IDs are not presented as editable UI. - Added a top-level provider-neutral “ask an AI to read this manual” path using current official ChatGPT/Gemini/Grok information. The text does not promise that a pasted GitHub URL always imports a repository; Gemini's explicit Import code route and README paste/upload fallback are stated. - Copied seven user-supplied PNGs unchanged into `docs/images/v38-manual/`: loader bypass, three Reference Images, First/Last Image, First Image Draft sizing, LightX2V LoRA selector, First Image tooltip, and Manual Width/Height. Source/destination SHA-256 matched for all seven; README now has 32 local image links and zero missing targets. - Confirmed from source that Manual accepts 32x32, size selection is built into the V3.8 Sampler, loader OFF uses native bypass behavior, and the public surface remains exactly seven nodes. LightX2V's own Hugging Face/GitHub records were used to separate FL2VA/Ref2VA and 4/8-step targets; a 4-step LoRA at six inference steps is labeled workflow-specific rather than an upstream default. - Recorded Issue #13 conservatively: still Open; Standard V3.8 has no active mitigation; the isolated 6x5 R6-A improvement did not become a Production claim because the later 4x8 gate produced gains 1.0 and A/C bit-exact no-op. This documentation change does not alter Production, runtime, workflows, manifests, Sampling, or backend state. - Validation: focused tests `120 passed`; one registry-manifest test remains expectedly red because README plus pre-existing `run_storage.py` and `web/project_id.js` are not yet re-frozen into `REGISTRY_MANIFEST.sha256`. README image-link audit is `32/32`; no manifest was rewritten before the final workflow/package freeze. Snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\before-v38-full-ui-readme-20260907_152253`. No commit/push/tag/release. ## English illustrated continuation manual live revalidation (2026-09-07, Continue PASS) - Used the user-owned `127.0.0.6:8188` Chrome workflow `MiniMax_H3_00058_` through Computer Use with Turbo4 v1.2, actual Steps 4, Euler/simple, Spectrum OFF, Draft 0.30 MP, fixed seed, Review Each Chunk, Progress ON, and 2x5 seconds. The backend was not stopped or replaced. - Fresh Chunk 1 reached the three-action review panel. Selecting `Use it and continue` did not execute by itself; the top-right blue `Run` queued the action. The next Queue sampled only Chunk 2 (Sampler UI time 43.738s), reused the accepted Chunk 1, and reached `Saved sequence is complete` at 10 seconds. First Queue Sampler UI time was 103.802s; do not interpret the cold/warm difference as a general speed ratio. - Added exact UI crops for review actions, selected Continue, completed sequence, Back-to-Settings completion state, Render History actions, and Regenerate From with visible Variation Nonce. README removed the obsolete retry-failure warning, uses the new screenshots, explains that Chunks is the final total, and updates the diagnostic four-step expectation to `sampling_steps_total=4`. - Evidence full screenshots are under `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-manual-live-20260907`. Snapshot before edits: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\before-manual-steps4-capture-20260907_142631`. No commit, push, tag, release, or backend shutdown was performed. ## V3.8 Continuation Regression Final Gate (2026-09-07, Pre-GPU PASS / approval pending) - Supersedes the stale restart-required review status below. The repaired Review state was live-validated: `Try this chunk again` regenerated the selected chunk and returned the three-action review screen; after the user disabled an accidentally enabled Spectrum node, `Continue / Next` completed normally. Manual screenshots remain deferred. - Current task follows the supplied `H3 Continuum V3.8 — Continuation Regression Final Gate`: compare current Standard/Balanced22/Audio ON Masked AV against Compatibility Reference Context under one frozen `4×8s`, `896×896` GPU A/B. No Production transport change is allowed unless GPU result is Case A. - Snapshot `pre-v38-continuation-regression-final-gate-rg-20260907_110054`:935 entries, manifest SHA `DD62DCA87437CABB049D16BFB720DF45FAC04988096C7A3827433D95206CD698`, creation-time source mismatch0. Normal snapshot helper hit the inherited pytest-cache ACL; verified robocopy+rg fallback retained the same authoritative source. - Code audit confirms V3.4 final code baseline `d3dab7b` uses fresh-target Reference Context; current Standard/Balanced22/Audio ON uses masked AV target prefixes and Compatibility uses Reference Context. Both remove the later-group hard First Image keyframe while retaining original visual/Qwen identity tokens. - Actual Comfy CPU Shadow PASS: Standard has exact Video7/Audio37 tail prefixes with zero prefix masks and no continuation refs; Compatibility has one exact AV ref, fresh zero target, no mask, target-head MM-RoPE alignment and preserved `position_ids` identity. CUDA remained uninitialized; owned PIDs/8190/HTTP ended. - Pre-GPU focused5/5 and syntax PASS; stage/source runtime153/153 exact. Frozen semantic graph diff is only `continuation_backend`; Spectrum/Sol/Still/Driving/Reference/Last/Run Storage/Second Pass/Hi-Res/R6-A are OFF. Protocol SHA `7c525971a0a98694f75915b304c349b5f95d59ae0d450a07efd98ceb91ab4736`; execution manifest SHA `3f801370f69e8709f24a6849535483fbb00d49978ba419acf779c127d7afd412`. - GPU authorization artifact is absent. Negative launch test refused before creating a run or opening8190. GPU Sampling, A/B result, reset/seam and Case A/B/C are pending explicit approval. User-owned8188 is untouched; no Production/commit/push/tag/release. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-continuation-regression-final-gate-20260907\PRE_GPU_REPORT.md`. The previously recorded fixed-task id was no longer readable; the current task list resolves title `H3情報チェック` to ChatGPT conversation `6a8ef934-10ac-83e8-9af2-9e2417af7224`, but detailed handoff was rejected because this changed destination identity lacks fresh explicit authorization. No workaround was attempted. Mandatory review and GPU remain pending user authorization. ## Regenerate From / provenance reuse repair (2026-09-07, installed / restart required) - Immediate current task: reach the user's actual Chunk1-review screen with Continue / Retry / Finish buttons, then STOP before generating Chunk2. Manual screenshots and transport research remain deferred. Do not fake readiness or delete existing media. - Actual UI run29e95cfc-1c9d-41fd-b32c-0d07855353a6 submitted Review Each Chunk,2x5s,Regenerate From Chunk1,nonce0,Continue / Next,Take Automatic. Unexpected result: cb575f0c6aa00705 nonce1/new_revision,2 reused/0generated,10s video00070,52.35s. This is NOT successful first-chunk regeneration. - Root cause: prepare's provenance candidate path checked ancestry/lineage/prompt but ignored changed per-chunk sampling contracts. `_valid_provenance_prefix` now optionally enforces actual producer-revision chunk-contract hashes from the requested branch boundary onward; prepare enables it. Prefix before the cut remains reusable, same-nonce interrupted work remains resumable, explicit Take selection remains separate. Stored-manifest validation is unchanged. No new hard stop or Sampling/Audio/Assembly/schema change. - Also repaired blank Render History: actual custom canvas widget now draws selected/canonical Take text instead of relying on an unsupported multiline primitive. Existing transient serialization guard retained. Lifecycle fixture verifies that Selected text is actually drawn. - Tests107 PASS (9 new on-disk provenance cases plus review/branch/control/execution suites); UI19 PASS; extra canvas-draw fixture PASS; diff check PASS. First test collection failed due to importlib-mode fixture import and was corrected without production changes. Stage AST confirms ONLY prepare/_valid_provenance_prefix differ from previous runtime, exactly matching tested source, zero import changes; old source-only atomic JSON helper remains excluded. - Installed runtime run_storage SHA0E402AD912926AE02FDC2A50BED9009B4C3A090EF6D52F6344C3B26FA33C1676; JS SHA7B318BE7E0A6FFA7A0B924F149EE90C10E4EBFB731DA2BC40297BAD0ECF63269. Full runtime snapshot181files before-review-reuse-runtime-20260907_104350; source scoped4files before-review-reuse-scoped-20260907_104350 (normal helper hit inherited cache ACL). - User-owned8188 remains running old Python code, queue0/0 at deployment. User restart and browser reload REQUIRED before another Run. Then keep Regenerate From Chunk1 for exactly one Review execution, verify1generated/1of2available,review_ready and visible3buttons. Reset manual Regenerate From to Auto through UI before later continuation (do not rerun Chunk1 inadvertently). Smart Retry GPU still unverified; no completion handoff/commit/push/release. Previous full-suite2 failures remain documented below. ## Completed-review UI repair (2026-09-07, deployed / browser reload and GPU retry pending) - Supersedes the older diagnostic-only status below. Review identity repair is installed in runtime run_storage.py (SHA59593daf4e2021bad2e6849427aae95a439220745f582b406ea1d240b19ebe45): canonical set observation and Core archived parameter dtype observation prevent false LoRA/VAE identity changes. CPU169 focused tests passed. Post-fix fresh Chunk1 `45dc7891-f3a8-4995-8bd7-25c1f3e959d2` and Continue `ffff7252-33b9-4f38-8bf7-fe3033c2d453` succeeded; revision99684d4a78b5855b, Chunk1 file SHA unchanged, only Chunk2 generated, 10-second video00065. Smart retry GPU remains unverified. - Current UI failure independently reproduced: `/view?...project.json` returns200, canonical99684d4a78b5855b is complete with review_unit2, while frontend reviewReady accepted only review_ready. Backend already permits Regenerate Current for complete+review_unit. User Runs638b84ae and2c52c22f actually submitted Continue / Next and reused2/generated0, not retry; latestvideo00068, workflow25.34s. - Changed web/project_id.js only for the runtime UI: backend-derived completed panel remains accessible; valid reviewed unit allows retry; completed Continue/Finish hidden; history/settings retained even for complete without a retry unit. No Sampling/Assembly/schema/status/persisted-revision changes. Source/runtime JS exact SHAB571FD4E061B113931D5470DD9844CAD77390B5227CC0EF05576ECCDA9662812. Scoped web snapshots7+7files and records3files verified under before-completed-review-*20260907_101839. - New real-JS lifecycle fixture covers initial/partial/running/interrupted/completed,1..6 chunks, Terminal Merge label, one-shot queued retry, settings round-trip serialization parity, history, reload and failed fetch. Focused128 passed; additional frontend15 passed with one distribution-manifest hash failure. Full suite:1139 passed /2 failed (same manifest mismatch and identity test assumes process-global CUDA remains uninitialized after earlier tests; isolated identity suite passes). Do not claim full-suite PASS or pure CPU-only full-suite execution. Package/Release remains HOLD; these two failures need separate disposition. - Auto-review blocked browser Ctrl+R because current00058 tab is dirty (`*`). No reload or extra GPU Queue occurred. Ask the user to save/reload or explicitly approve reloading the unsaved tab; do not circumvent the block. Then verify completed UI, select Try this chunk again, submit once, compare saved Chunk1 SHA and generated/reused counters. User-owned8188 remains running. Manual screenshots and Standard/Compatibility proposal remain deferred; no commit/push. Completion handoff is pending the live repair gate, not yet complete. ## Review retry diagnosis follow-up (2026-09-07, restart required / root cause still unresolved) - User authorized fixing the live retry failure. Read-only CPU load of saved revision `52e4e5124afd5d7a` passes `_validated_review_head` and `find_latest_review_head` against its stored contract: prefix1, review_ready, no notes, CUDA uninitialized before/after. Saved data corruption is not demonstrated; the actual retry-time contract remains uncaptured. A model/runtime fingerprint change is a hypothesis, not a confirmed cause. - Added hash-only mismatch diagnostics to `run_storage.py`: when no compatible head exists, report up to three nearest stored contracts and differing contract sections. Retry retains its original error and rejection policy; no unsafe fallback, identity relaxation, Sampling/seed/mask change, or automatic fresh generation. Successful lookup skips the new comparison. Tests: Run Storage/review79 plus policy/cache/UI/branch83 =162 PASS; diff check PASS. - Installed only the three diagnostic-definition changes into runtime `run_storage.py`, SHA `16f0bb17b863dc0b1aef95656deae9a4783338b35145f010bec95a661feae6df`. AST audit proves no other runtime/import changes and exact agreement with tested source for those definitions. The source's pre-existing atomic-replacement retry helper was intentionally NOT included in this narrow deployment. Full runtime snapshot181 files: `before-review-mismatch-runtime-20260907_093306`; source scoped snapshot4 files/SHA4: `before-review-mismatch-scoped-20260907_092947` (normal source helper encountered existing cache ACL). - Diagnostic code is on disk but the user-owned8188 process has NOT been restarted or stopped; queue0/0. User restart is required before further Computer Use retry diagnosis. No new GPU run, publication, final manual validation or completion handoff. Resume using evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-manual-live-20260907\RETRY_DIAGNOSTIC_STATUS.md`; do not claim the underlying bug fixed. ## English illustrated continuation manual (2026-09-07, Computer Use recovered / retry validation FAIL) - Computer Use now initializes successfully. Used the existing Chrome tab `927290933` (`00058`, user-owned `127.0.0.6:8188`) directly. Exported the current UI workflow before edits and snapshotted five files at `before-live-manual-scoped-20260907_090852`. Changed only seed control to fixed and Run to Review Each Chunk (UI enabled Progress automatically); retained supplied Turbo4 v1.2 / actual4 Euler/simple / Spectrum ON / KJ Sage / blank prompt / 2x5s / effective544x544. - First UI Run PASS: prompt `e2c6038a-6403-4b27-bc4e-4d390a61741e`, backend execution75.232s, sampling30.447705s,120frames/5s, video `D:\output\video\comfy_video\video\MiniMax_H3_00064_.mp4`. Review panel actually appeared. New exact-pixel crops show settings, blue top-right Run, review-ready, and selected retry; README distinguishes top-right execution Run from the in-node Run setting (review messages still say Queue). - Second UI Run, Try this chunk again: FAIL before new sampling, prompt `f8c18378-7a42-40b5-8408-19e8e86b877b`, `Regenerate Current requires an existing reviewed unit`. Full submitted graph differs only by `review_action`. Saved manifest remains `review_ready`, unit1..1, resume_safe=true; saved chunk SHA matches manifest. The read-only trace locates missing compatible review-head resolution, but why it rejects/misses this stored head remains unresolved. Do not blame a seed change or claim retry/continue/finish verified. Stop further GPU runs pending diagnosis/fix authority. - Runtime/source check: review_control.py, v3/nodes.py, web/project_id.js exact; run_storage.py differs only by the source's Windows atomic JSON replacement retry helper. No evidence links that difference to the observed missing-head error. No runtime installation or code fix performed. Queue running0/pending0; user backend intentionally left running. Source README has an explicit draft-validation warning; no commit/push. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-manual-live-20260907` contains exported workflow, both full prompt/history records, summaries, saved manifest, full screenshots and UI action timestamps. Failure screenshot kept as internal evidence, not public manual artwork. Remaining history/settings/continue/finish/regeneration/extension screenshots and final release documentation review are pending. Earlier tool-blocked notes below are historical. - README now contains a general 11-section Review/continue/retry/finish/settings/history/regeneration/extension/timing guide, with six unmodified user-supplied UI crops under `docs/images/v38-manual/`. Two chunks is only an example; total-vs-added count, fixed Base Seed, later-section rebuild, and Last Image/Terminal Merge exceptions are explicit. README_JA is unchanged by this task. - Source/code cross-check and six PNG relative links plus section anchors PASS; no claim of fresh UI or arbitrary extension GPU validation. Prior two-Queue six-step timing is identified separately; downstream time is not individually profiled. GitHub-ready source assets only; Registry/package refresh and commit/push are not performed. - User then supplied a running ComfyUI at `http://127.0.0.6:8188/`, workflow `00058`, Turbo at four steps, and requested live Computer Use screenshots plus execution timing. Use that user-owned backend after visual verification; do not stop or replace it. No Queue, UI edit, or new GPU execution has occurred in this documentation task. - Both `node_repl` (`@oai/sky` bootstrap) and `cua_repl` fail before execution with `failed to write kernel assets: 指定されたパスが見つかりません。 (os error 3)`. Resetting each kernel did not resolve it; workspace/TEMP/TMP exist. Exact missing internal path and root cause are unknown. No unsupported screenshot/desktop automation fallback was used. Live capture remains blocked pending tool recovery; record new observed UI before any action. - Verified four-file pre-edit snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\before-illustrated-review-readme-scoped-20260907_085726`; standard helper first failed on inherited `.pytest_cache` ACL. Resume from README and the current-scope note in `docs/V38_BEGINNER_MANUAL_PLAN_AND_CAPTURE_SCRIPT_JA.md`. Completion review is pending until live documentation validation is complete; do not send to the unpinned duplicate H3 task. ## Issue13 R6-A Turbo4 v1.2 / actual 6-step / 0.30 MP A/B (2026-09-07, VALID / NEGATIVE-HOLD) - Executed the supplied Turbo4 v1.2 / 6-step Euler/simple / Draft0.30 MP settings as an adapted `6x5s` efficacy test, not an exact reproduction of the supplied `2x5s` workflow. Effective size was `544x544`; prompt remained empty; Audio Continuity/Balanced22/KJ Sage were ON. Fresh Group1 was shared; A had R6 OFF and B differed only by frozen global latent AC contraction. - Execution contract PASS: both arms are `720f/24fps/30s`, stereo32k PCM `960000` samples; Assembly exact; Sampling traces complete; resources `5/5` with hard-stop/contract errors zero; both dedicated backends normal-shutdown with owned PIDs gone,8190 closed and HTTP offline. Exactly five policy evaluations occurred: G2 required no-op, G3 natural no-op, then gains G4 `.9`, G5 `.95440975`, G6 `.9`. Raw AV is exact through G3 and diverges from the first effective intervention at G4. - Numeric promotion evidence is NEGATIVE/HOLD for this condition: endpoint Laplacian `+8.28%`, Gradient `+11.85%`, Contrast `+113.44%`, Shadow `+71.07%` worse; motion proxies about `1.6%` lower and seam metrics warn worse. Highlight endpoint improved `99.14%` and mean-saturation endpoint improved `20.20%`, but they do not offset the primary/guard negatives. Perceptual A/B playback remains pending; seam ratios are not a perceptual-cut claim. - Interpretation is narrow. The empty prompt produced severe shared semantic excursions before R6 acted, including near-white G3 and green-background G5, so this is weak evidence for Issue13 natural cumulative drift. Do not generalize to R6 overall or invalidate the separate earlier Turbo8 numeric candidate. No Production/public schema/default/package or release change. - The first attempt stopped pre-Sampling on expected-plan evidence ordering; it was preserved and the isolated runner ordering was corrected without graph/Sampling change. The completed wrapper later exited only because atomic `RESULT.json` refused to overwrite that first attempt; all A/B artifacts were durable and shutdown complete, so no GPU rerun was needed. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-turbo4-6step-0p3mp-20260907\TURBO4_6STEP_0P3MP_REPORT.md`. Fixed `H3情報チェック` completion review `bd47c1b1-8aa6-4f87-b24a-efa7c8d74fe7` accepted `EXPERIMENT VALID / EXECUTION CONTRACT PASS / NUMERIC PROMOTION EVIDENCE NEGATIVE / HOLD / DO NOT PROMOTE` with no mandatory correction. Source-record snapshot `pre-r6-turbo4-report-record-filtered-20260907_081550` has `919` files after the standard helper met the inherited `.pytest_cache` ACL. No commit/push/tag/release. ## Issue13 R6-A resumed B: numeric candidate, perceptual review pending (2026-09-07) - Fixed completion summary review25ee8534/9747f470 read: accepted with explicit NUMERIC GPU EXPERIMENTAL CANDIDATE qualifier, not perceptual PASS. Full30s A/B playback/listening is next, before additional GPU/new workflow experiments. Review did not independently inspect local media/artifacts. Final source230 code hashes unchanged; diff --check0; B41648/40316/36912 absent,8190 listeners0. - User explicitly resumed B before supplied Turbo/Spectrum workflows or Audio Continuity experiments. Completed A evidence reverified (R3B rawAV12/12 plus exact historical decoded/PCM and owned shutdown); interrupted B retained. New fresh B0b0b607953934a6bb2e7ed7142784ae6 completed13m08s from shared savedG1 under unchanged frozen protocol79bbe9a5..., after53/53 resume CPU tests and fixed-task prelaunch review542d0853/3bfd0ff3 accepted inside-lock checks. No numerical method or threshold changed. - EXPERIMENT VALID / FROZEN NUMERIC GATES PASS / PERCEPTUAL REVIEW PENDING. Lap endpoint drift39.86749->13.36942 (66.47% reduction), Gradient72.91%,Highlight91.17%,Contrast26.82% better. Saturation4.10% worse; seam1.38317->1.51302 (9.39% worse); both within frozen guards. Motion/detail/PCM numeric screens PASS. These are metric-drift changes, not overall quality percentages. - Counterevidence: largest benefit is Group6; G5 Lap nearA and Gradient slightly worse. Peak Lap excursion reduction only15.15%, so uniform long-trajectory suppression is NOT established. Paired stills are coherent but full playback/listening and perceptual identity/detail/seam PASS remain unverified. One scene/seed only, not Issue13 solved or Production promotion. - Actual invariants/noise5/5 match, rawG1/G2AV4/4 exact, scope violations0,720frames/30s/960000sample stereo32kHz PCM. GainsG2..6=1,.991727,.995747,.994723,.973105. Both owned backends normal shutdown/PID/8190/HTTP confirmed; user backend untouched. No additional GPU phase started. - Evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-pre-gpu-20260907\FINAL_REPORT.md`, QUALITY_SCREEN.json,PAIR_REVIEW. Two supplied workflows retained unchanged in user_workflows, NOT executed/mixed intoB. Completion review requested at fixed H3情報チェック before any next phase. Source record snapshot919 pre-r6-B-completion-record-excluding-cache-20260907_063034. Production/Release/A5/general A8b HOLD; no commit/push/tag/release. Earlier user-paused state below is historical. ## Issue13 R6-A: Standard A complete, B USER-PAUSED (2026-09-07) - Latest user instruction stopped continuation and requested analysis of A only. GPU authorization is now false; do not resume B or start another GPU run without a new user instruction. The stop arrived after B Group2 had begun (last log2/8 steps); immediate launcher interrupt ended the run. This is not a B quality FAIL or completed experiment. - Fresh A completed13m04s: R3B rawAV12/12 exact, historical decoded metrics and PCM exact, five Sampling/noise records, intervention-scope violations0, normal A shutdown confirmed. Review of the corrected PreGPU gate was accepted by fixed summary reply70782869-06e2-461a-96fb-0edb978f4eea before launch. - All six A/B owned PIDs41304/21224/20080/19020/2276/4140 independently confirmed gone;8190 listener0/HTTPoff. B normal queue-drained shutdown was not established because immediate interruption took priority. User backend untouched. Pause evidence `issue13-r6a-pre-gpu-20260907\USER_PAUSE.json`. - A-only CPU analysis:720f/24fps/576x864/30s, central25-frame means show Lap248.55->288.42 (+39.8675 units, +16.04%, NOT +39.87%), Gradient+5.44%, highlight clipped fraction0.1794%->0.5662%. Sampled subject/composition remains coherent; late edge/texture strengthening persists. Strongest normalized seam at15.0833s=1.3832. PCM intact/exact but RMS~-54.9dBFS; no listening/full-playback perceptual PASS claimed. This is baseline reproduction, not mitigation success. - Evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-pre-gpu-20260907\A_ANALYSIS\REPORT.md`, summary/seam/detail/join artifacts. Fixed summary review c4a59d67/f1b2f17a accepted interpretation, emphasizing that observed late-stage edge strengthening is not a fresh causal proof, nor a playback/listening PASS. Review does not authorize GPU resume. Source-record snapshot919 `pre-r6-A-analysis-record-excluding-cache-20260907_034446`. Production, commits, push, release unchanged. ## Issue13 R6-A corrected Pre-GPU freeze (2026-09-07, supersedes prior freeze) - User approved correction, CPU verification, refreeze and the single Fresh A -> conditional Fresh B GPU pair; no renewed GPU permission is needed for that pair. Fixed-task completion review is pending before launch. GPU efficacy is still untested. - Independent local inspection corrected signed-negative Laplacian acceptance, seam threshold discrepancy, unrelated two-secondary-improvements requirement and missing actual Sampling invariant recording. Absolute Laplacian threshold remains31.89399101047766; per-chunk Lap/Gradient>=80% shared Group1 is an added blur screen, not perceptual proof. Secondary absolute drift<=1.2A, motion>=.8A, seam<=1.2A. One-seed candidate only. - Symmetric observer records actual seed/noise/SIGMAS/conditioning/ordered wrapper and sampler evidence; B must match current A before model execution. Intervention source/reference/Audio/generated-region/mask hashes remain exact; Group2 prefix no-op. Completion manifest requires both sampling_trace and pin_renorm evidence. Fresh A rawAV12/12 and exact historical decoded/PCM parity remain mandatory. - CPU46+controller/lifecycle45=91 PASS; CUDA tripwire clear in correction suite; canonical/stage230 code SHA exact; upstream14 and execution259 hashes exact. New protocol SHA79bbe9a5b671ed2d6d2c66d0d549e759ab28bef1b4a67938cd0e80a3049a442d. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-pre-gpu-20260907\CORRECTION_GATE_REPORT.md`. - Research pre-edit snapshot353 files; pre-record source snapshot919 files `pre-r6-correction-record-excluding-cache-20260907_031923` after inherited .pytest_cache ACL prevented ordinary helper completion. Production/commit/push/release unchanged. No automatic retry or sweep. ## Issue13 R6-A Pre-GPU Gate PASS (2026-09-07) - Frozen comparison is one pair only: A is Standard/Balanced22 with the R6 hook disabled; B differs only by enabling the global latent AC scalar contraction on protected Video-prefix slots. Shared saved Group1, 576x864/24fps/6x5, seed131325, FL2VA INT8/Turbo8/Euler/simple/KJ Sage and all other settings are fixed. This is not a texture- or frequency-specific correction. - Fresh A must pass R3B raw Video6/6 + Audio6/6 exact plus PCM/artifact/resource/Assembly/owned-shutdown checks. It must also exactly reproduce frozen historical A decoded metrics and PCM after excluding only run ID and output path. Any raw or decoded baseline difference prohibits B. Historical Laplacian drift39.8674887631 and B threshold<=31.8939910105 remain fixed; motion>=80%A, seam<=1.2xA, secondary Video metrics, PCM and perceptual review are guards. - Dedicated CPU tests passed55, including all existing fail-closed cases, authorization refusal, graph parity, and exact-A-quality acceptance plus a 1e-9 motion-metric rejection. Upstream hashes14/14 and execution files251 are frozen. Protocol SHA `48d110db7d376622f4275125207220a997d3134c1ecdf48276cd37d65fab936a`. GPU authorization artifact is absent; no backend/GPU ran;8190 listener zero. Production remains unchanged. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-pre-gpu-20260907\PRE_GPU_REPORT.md`. Snapshot `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-r6a-pregpu-record-excluding-cache-20260907_024434` has919 files; ordinary helper first stopped only on inherited `.pytest_cache` ACL. Fixed review aa0cb846-a49f-44ea-a3e3-e682d6a144d5/9a9dc5e1-3363-459c-bc3e-86511dfb97e2 required decoded-A parity; after correction, review91ee90f4-ebf4-4659-a329-e85747c4aac0/a5c3e54b-6ff7-4a08-84f2-a11c58a42664 accepted final Pre-GPU PASS with no remaining design correction. GPU still requires explicit immediate approval. ## Issue13 R6-A actual Comfy CPU Shadow PASS (2026-09-07) - One owned CPU-only Comfy backend completed an actual Queue/history request using staged public V3.8 registration, Core NestedTensor, the real masked AV prefix builder, and saved R3B rawAV. No model/VAE/noise/Sampling. OFF returned original latent object for Groups2..6. ON Group2 gain1.0 was exact no-op; only Groups3..6 protected Video first7 slots changed with gains0.9917270/0.9927173/0.9882362/0.9733208. - Generated Video, whole Audio object/content, masks object/content, metadata, conditioning fixture, SIGMAS, current tails, fixed Group1 reference, saved raw12 and Python/Torch RNG remained exact. Five events shared one reference SHA.9 prototype tests and15 actual verification checksPASS. - CUDA false at import/bypass/node/shutdown; no tripwire. OwnedPIDs9704/36796/29444 ended; queue empty,8190 listener/HTTP off; user backend untouched. Evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-actual-comfy-shadow-20260907\REPORT.md`. Snapshot `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-r6a-shadow-record-20260907_013958` has924 files. - Pre-GPU Gate remains incomplete: actual model Sampling OFF rawAV12/12, noise/derived-seed/full-conditioning/wrapper/Assembly invariants, execution hash freeze, and decoded AV quality remain GPU-stage evidence. GPU not started and requires explicit approval immediately before launch. User-authorized fixed summary review 6ae817e0-7654-4c06-a06b-75bd9eee42fc /a1bab86c-09b8-4132-aa30-91e2f85bb637 accepted classification with no mandatory correction. R6 does not directly change Sampling-input Audio, but joint AV generation may indirectly change output Audio; GPU must measure it. Review is not independent local-artifact inspection. ## Issue13 R6-A Pin Renorm CPU design audit PASS WITH CONDITIONS (2026-09-07) - Isolated non-Production prototype freezes Group1 final seven Video slots as the Balanced22 reference and applies `current_mean + gain*(current_tail-current_mean)` only to the protected seven Video prefix slots for Groups2 onward. `gain=clamp(reference_std/current_std,0.90,1.00)`; amplification prohibited. Audio37T, masks, generated regions, seed/noise/SIGMAS/conditioning/Assembly/State/Session/RunStorage remain unchanged by contract. This is global latent AC scaling, not texture-only/frequency-selective. - Actual R3B shadow requested gains feeding Groups2..6:1.0000000,0.9917270,0.9927173,0.9882362,0.9733208. Thus Group2 is unchanged and intervention first appears at Group3; maximum measured reduction2.67%. Per-channel ratios are heterogeneous, so decoded efficacy/motion safety remain unproven. - Focused CPU9 passed: OFF object identity and RNG neutrality, Group1 exclusion, source/reference immutability, Video-prefix-only scope, Audio/mask/metadata preservation, bounded/no-amplification gain, and invalid/degenerate/shape/transport fail handling. Actual rawAV finite/expected shapes; CUDA remained uninitialized; no backend/GPU Sampling. Evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r6a-pin-renorm-cpu-20260907\REPORT.md`. - Valid pre-record snapshot `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-r6a-cpu-record-20260907_012541` has924 files. GPU not authorized by this CPU Gate; next phase requires isolated actual-Comfy OFF parity/Shadow/lineage wiring and frozen decoded evaluation, followed by explicit GPU approval under the latest instruction. User-authorized fixed summary review 05b4095a-89d0-4262-9323-d5932f3ea630 /f8e60c80-b3d1-4637-9cbb-48f490d178f6 accepted PASS WITH CONDITIONS. Numeric degeneracy contract is explicitly CPU float64,epsilon1e-12; reference <=epsilon fails, current <=epsilon no-op. Review is not independent local-artifact inspection. ## Issue13 R5 5f actual GPU pair closed: PRIMARY QUALITY FAIL (2026-09-07) - Actual fresh A matched R3B raw Video6/6 + Audio6/6 bit-exact. PCM/artifact/plan/resource checks and full owned-backend shutdown passed before fresh B. B applied immutable Group1 first5f reference exactly for Groups2..6. Both720frames/30s and stereo32kHz960000sample PCM. Execution/integrity PASS; no OOM/nonfinite. - Primary Laplacian drift A+39.86749 -> B+74.97015 (88.05% larger drift; not overall image-quality percentage), failing frozen <=31.894. Gradient drift91.44% worse. Several tone/color drifts improved, but cannot override primary failure. Motion/seam numerical guards PASS; PCM numeric screen clean, listening/full-playback perceptual verdict not established. - DO NOT PROMOTE this fixed5f compound content+rows+AV-position intervention. No sweep; Issue13 unresolved; Release HOLD. No Production code/commit/push/tag/release change. Source230 py/js hashes match924-file pre-run snapshot. A/B owned processes zero and8190 listeners zero rechecked after completion; user backend untouched. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-gpu-ab-20260907\FINAL_REPORT.md`. Fixed H3 information-check summary review f62e27e4-6b3c-477b-aa0b-7a25c9d20454 /827767df-4345-48e2-b511-f36b1eeeb583 read: no mandatory correction; not independent artifact review. ## Issue13 R5 GPU A/B authorized; preparation frozen (2026-09-07) - User expressly authorizes continued GPU testing without repeated confirmation, within current R5 single5f A/B scope. Previous GPU-unapproved entries are historical. A actualR3B rawAV12/12 +PCM/artifacts/resource/plan/normalshutdown remain mandatory beforeB. No sweep/Production/publication authority added. - Isolated runner/graphs at `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-gpu-ab-20260907`; PRE_GPU_REPORT.md and final execution hashes.14upstream/assets/protocol hashes matched;4CPU preparationtestsPASS. GPU not started at this record; mandatory fixed review requested before launch. DirectGPU startup never uses W2 CPU bypass. ## Issue13 R5-W2 scoped CPU wiring PASS (2026-09-07) - Fixed summary review c03e9c5b-823c-4f74-93e1-bba5a8bd48c2 /56226d50-cf39-4acf-ab2c-1f5949fa947f read; accepts scoped PASS, no mandatory correction. Synthetic evidence is not quality/GPU parity. Actual A12/12 and R5 ON execution remain POST-approval GPU checks; preparation/freeze remains CPU work, not authority to start GPU. - CPU bootstrap alone bypasses kitchen INT8 availability; lazy/C initializer tripwires retained, CUDA availability API unmodified. Actual Fresh Comfy A/B fixture Queue/history and PCM-observed stage Finalize completed720frames/960000samples each with observer parity/RNG unchanged and CUDA uninitialized through preexit. No model/VAE/Sampling; R5 source and GPU Sage/KJ unchanged. - Real A live denied B; current A synthetic raw12/PCM/evidence verified only after queue0/0 and owned PID/listener/HTTP shutdown, then rechecked under exclusive lock before CPU fixture B. Raw12 fixture is NOT GPU baseline parity. A41480/2120/9176 and B24760/5132/30700 ended. 15 offline evidence assertions plus37 regressions PASS. Source230 unchanged vs snapshot924 pre-r5-w2-20260907_000922. - Evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-w2-cpu-bootstrap\REPORT.md`. Full R5-2 NOT YET PASS: actual GPU runner quality metrics/resource/plan bindings and final execution freeze remain. GPU unapproved. Fixed summary review requested. No Production/publication change. ## Issue13 R5-W1 first CUDA initialization cause isolated (2026-09-07) - Fixed-task summary review read:738aad5c-f71f-43fa-af16-b0f82de4a8e1 /0938013b-95fc-4e41-963b-0ff48cddec72. Accepts first-cause isolation PASS only; no remediation, no exhaustive-trigger claim, no inference of normal GPU Sage defect. Next CPU-specific workaround requires its own scope; not started. - One guarded startup intercepted Core attention.py54 -> comfy_kitchen.sage_attention.is_available:75 -> torch.cuda.get_device_capability -> _lazy_init before actual initialization. torch initialized false before/after; intentional exit86. No prompt/model/Sampling or automatic retry. First observed cause is CPU-unconditional Core/kitchen capability probe, before R5 registration; later triggers not ruled out. - Nine offline checks PASS; source230 py/js unchanged against snapshot924 pre-r5-w1-init-isolation-20260906_235631. Owned26156/33568/15832 ended,8190 listener/HTTP offline. Evidence `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-w1-init-isolation\REPORT.md` plus full stack, command, result and hashes. - Cause isolation PASS only; no remediation or installed-runtime edit. Full R5-2 NOT YET PASS; GPU unapproved. CPU-specific availability-probe avoidance remains proposed, retaining the tripwire and preserving eventual GPU Sage configuration. Fixed-task review requested. ## Issue13 R5 actual Comfy wiring HOLD (2026-09-06) - Isolated stage/Sampler/PCM Finalize graph adapters created; nine CPU tests PASS. Actual Comfy object_info and nonce-only prompt/history binding worked. No model or Sampling request submitted. - Strict probe detected torch.cuda.is_initialized=True despite --cpu and Device:cpu. CPU-only integration is NOT PASS; initializer unresolved. Do not automatically repeat startup or weaken the guard. All owned PIDs4812/10092/38456 and earlier attempts gone; queue0/0,8190 listener/HTTP offline. Production unchanged. - Full R5-2 NOT YET PASS: real metrics/resource/plan binding, controller integration and final freeze remain incomplete. GPU unapproved. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-comfy-wire-20260906\REPORT.md`. Snapshot pre-r5-comfy-wire-20260906_233825:924 files. Fixed-task summary review requested; awaiting reply. - Fixed review ec956664-22e1-4846-8023-e574b7967a2b / 02c95f2c-ef0e-42d4-83a9-afd26c748f4e read: summary-only PARTIAL wiring PASS, CPU-only claim rejected, full NOT YET PASS. CUDA runtime initialization is observed; GPU computation is not established by that fact. Next is initialization isolation and full controller/evidence/freeze, not GPU sampling. ## Issue13 R5-2 CPU launch lifecycle (2026-09-06) - CPU lifecycle sub-Gate PASS: 8 tests, actual minimal loopback CPU service A/B start/shutdown, PID tree/create_time/8190/HTTP verified stopped. No ComfyUI/model/torch/CUDA/GPU. Cross-process exclusive lock, fresh controller identities/root, atomic completion-last publication with bounded retry, immutable decision hash and B recheck verified. First test exposed Windows read-only fsync Errno9; diagnostic r+b flush correction passes, no B launched on failure and A cleaned up. - Final A PIDs14284/18348/38780 and B25704/40888/39560 exited;8190 absent. Fixture12/12 is not GPU baseline parity. Source230 unchanged versus snapshot924 pre-r5-launch-lifecycle-20260906_231926, diff check0. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-launch-lifecycle-20260906\REPORT.md` and JSON/XML/frozen evidence. - Fixed summary review `fd337f43-4b58-494a-bbf6-6339635fb0d7` / `913264ed-3b1b-42f2-8aaa-d8acd33930dc` accepts CPU Launch Lifecycle PASS. Full R5-2 NOT YET PASS pending actual ComfyUI prompt/history/resource/shutdown adapters and real R5 stage graph wiring/freeze. Future actual GPU A12/12 is post-approval B permission gate, not a prerequisite to running CPU preparation. GPU remains unapproved; no publication. ## Issue13 R5-2 CPU evidence evaluator / Finalize adapter (2026-09-06) - Sub-Gate PASS: 37 CPU/Shadow tests. Evaluator reads actual safetensors keys/shape/dtype/SHA, recomputes PCM slices/assembly/pad/capture, checks artifact completeness/hashes/run provenance/settings/plan/resource and live-OS probe interface. Tests mock OS/launch only; no backend/GPU. Actual historical R3B 12 raw files hashed, 14 CPU assets frozen with mismatch0; source230 unchanged against snapshot924 pre-r5-runner-control-20260906_230811. - Fixed review turn `fa12ae03-03e4-430e-a2eb-26408a82ab1b`, reply `cde10501-5542-4b83-b075-864125170228` accepts sub-Gate PASS only (summary review). Full Pre-GPU remains NOT YET PASS pending real launcher/controller context ownership, exclusive lifecycle, atomic completion-last publication, and actual shutdown E2E. Review proposes non-sampling service for shutdown E2E, but none was started; current CPU-only/no-backend scope is preserved and any service-start authority must be resolved before execution. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-runner-control-20260906\REPORT.md`, SHADOW_TESTS.xml, R3B_BASELINE_RAW.json, HASH_FREEZE.json. No Production/runtime change, GPU approval, commit or push. GPU observer Sampling transparency remains unproven until separately approved Fresh A actual12/12. ## Issue13 R5-2 real Assembly/Finalize PCM integration (2026-09-06) - CPU integration sub-Gate PASS: real Finalize/Assembly with synthetic decoded stereo32k PCM and 8x8 images, 85 tests (14 integration/predicate +25 detector +46 Assembly regression). No VAE/model/backend; CUDA uninitialized. Source230 code files unchanged versus snapshot924 `pre-r5-pcm-integration-20260906_224938`. - Complete sample ledger checks input/copy order, exact retained content, hidden padding, natural958667 -> repeat-tail1333 -> final960000, capture SHA and restoration/RNG/input parity. Shortfall hidden by native padding, duplicate copy, wrong final pad and wrong capture point are detected. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-pcm-integration-20260906\REPORT.md`, JSON/XML/fixtures and 23-file hash freeze. - Fixed-task review delivered and read: turn `26c56b98-8172-4f3c-bd58-ff3d391d851e`, reply `771b11bf-9d7f-49f1-88c9-bdcd8d16335a`. Summary-only review accepts sub-Gate PASS. Full R5-2 remains INCOMPLETE pending runner integration, real file-hash A12/12 + actual shutdown E2E control, and final runner/prompt/prototype/observer execution-hash freeze. No GPU approval requested; user explicitly requires GPU waiting. ## Issue13 R5-2 Audio CPU preparation (2026-09-06) - Audio CPU sub-Gate PASS: offline NumPy PCM screen and capture helper, 25 tests passed. Stereo32k/960000 samples, actual five cuts, per-channel RMS/spectral/edge/click/dropout limits frozen. Numeric clean means review pending; confirmed Audio harm fails R5 regardless of Video improvement. - Natural Assembly 719f/958667 samples -> exact 720f/960000 adds 1333 samples. Future isolated runner must capture decoded counts, retained slices and pre/post adjustment; final count alone cannot establish no hidden shortfall. - Full R5-2 remains INCOMPLETE: executable runner/capture integration, CPU validation and runnable prompt/observer hash freeze remain pending. No GPU/backend or Production edits. Model/media/shared Group1 hashes 8/8 match; 244 CPU assets frozen; source230 code files unchanged from snapshot924. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-2-pre-gpu-20260906\R5_2_AUDIO_CPU_REPORT_JA.md`. - Following explicit user CPU sharing permission, the previously denied report was delivered: turn `b738494e-a202-4736-a9c8-a2c6380d110c`, reply `bf27b4da-9d2c-4313-95dc-4d43b1f04867`. Review accepted Audio CPU PASS and thresholds, requiring real-path PCM ledger/capture integration. This requirement is now CPU-tested as recorded above. GPU requires separate later approval. ## Issue13 R5 position-control CPU audit (2026-09-06) - Same-layout zero Reference is constructible, but it is not a neutral no-anchor control: Core default augmentation makes all 93,312 zero-latent row values nonzero; removing augmentation does not remove projection/modulation/unmasked-attention participation. Metadata without latent leaves 972 required condition rows missing. - Within the current native Reference contract and without row/attention/position rewrites, an inert matched control was not found. Reclassify Standard-versus-R5 as generated Group 1 reference plus additional conditioning rows and Core-native AV positional shift; do not claim pure appearance-content causality or general mathematical impossibility of controls. - Zero-ref versus real-ref remains a possible non-neutral content ablation, not a no-anchor baseline. No extra GPU arm has been authorized or run. R5-1 PASS WITH CONDITIONS remains; Pre-GPU design uses 5f only, Run Storage OFF and explicit shared saved Group 1. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-position-control-20260906\POSITION_CONTROL_REPORT_JA.md` and `POSITION_CONTROL_RESULT.json`. CPU assertions passed, source tensor immutable, CUDA uninitialized, backend/GPU Sampling absent. Fixed-task turn `57811644-8575-4e2d-87cd-930a7065ad45`, reply `5ac513f9-ba7e-4814-87c4-d42bff3f2518` accepted `Position-Matched Control Audit PASS` and the limited reclassification. Next freeze is Standard A versus R5 B only, with Video quality, motion/identity, Video join, Audio join and Audio continuity guards. GPU remains unapproved. ## Issue13 R5-1 isolated CPU/Shadow prototype (2026-09-06) - Implemented Default-OFF diagnostic scope, immutable 5f Group 1 Video-only reference, ordinary/Terminal sequence integration, exception cleanup and ON identity separation only in `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-1-prototype-20260906\prototype_src`. Production 230 Python/JavaScript files match the 924-file pre-change snapshot. - CPU tests: 88 passed; actual unmodified Core PackedLayout definitions: 10 cases passed. OFF sequence parity, Group 2-6 fixed anchor, user-reference presentation/tags, Replay/Review/Branch and Terminal shadows passed. These are stub-sampling structural tests, not GPU quality or kernel parity. - Conditional finding: native reference addition shifts absolute target Video and Audio positions by 8.333333 while preserving Audio values/count/relative timing. Do not claim absolute Audio position invariance. Persistent old-lineage selection after Group 1 replacement and ON disk-restart E2E remain unimplemented; proposed GPU scope must use explicit saved Group 1 and Run Storage OFF. - Two full-Core import attempts initialized CUDA as an import side effect and exited without model loading/forward/Sampling/backend. Final layout runner executes unmodified Core layout AST definitions and verifies CUDA uninitialized. Ports 8188/8190 have no listener. Release/A5/general A8b HOLD; no publication. - Formal verdict: CPU/Shadow PASS WITH CONDITIONS. Fixed-task turn `87d13aed-685c-4b5c-b13b-22a484da8766`, reply `f64a95b6-219d-4f8c-9073-006290220483` accepted it and requires a position-matched control feasibility audit before R5-2, or explicit reclassification as anchor plus native AV positional shift. A zero latent is not assumed neutral. No custom Core position correction is allowed. Evidence: `R5_1_REPORT_JA.md`, `R5_1_TESTS.xml`, `R5_1_PACKED_ROWS.json`, `R5_1_SOURCE_PARITY.json`. GPU remains unapproved. ## Issue13 R5-0 Dual-Role Anchor / Tail CPU architecture audit (2026-09-06, PASS WITH CONDITIONS) - Audited a long-term Group 1 anchor and the existing short-term previous-tail transport without starting a backend or GPU. The current I2VA Standard path already retains the original First Image as Qwen visual tokens while Balanced 22 uses the immediately previous `22f Video / 37T Audio` as a masked target prefix; R5 therefore must add only the generated Group 1 appearance cue, not duplicate the existing first-image role. - Rejected a Group 1 frame-zero keyframe: Core `PackedLayout` places it at the same position as the masked target head, so it competes directly with the previous-tail pose. The viable prototype route is one fixed Group 1 head `5f / 2 video slots` as a Video-only `minimax_refs` block, appended after existing user refs, while the previous `22f / 37T` AV tail, masks, restoration, trim, and Audio ownership stay unchanged. - CPU evidence using the frozen R4 Standard Group 1 raw Video proved source immutability and separate segments. Baseline rows were `21,501`; the 5f Video-only reference produced `22,473` (`+972 / +4.52%`). A 22f reference is structurally valid but deferred at `24,903` rows (`+15.82%`) because it repeats substantially more Group 1 motion and approaches the R2.6 over-constraint mode. - Shadow `PackedLayout` also accepted the hidden Video-only anchor after existing image/audio refs while retaining a final-frame keyframe; hidden anchor Audio rows remained zero. This proves packability only. Quality improvement, motion freedom, user-reference semantics, wrapper runtime behavior, and GPU cost remain unproven. - R5-1 may proceed only as an isolated Default-OFF diagnostic policy: OFF bit-exact, Group 1 and tail immutable, one anchor from Group 2 onward, no Audio in the anchor, existing reference order preserved, no new schema, and safe Standard fallback when only an initial State is available without the Group 1 entry. Review/branch/replay and Terminal Merge must pass CPU/Shadow before any GPU proposal. - Fixed-task review turn `3f6fc599-b9b0-4ca9-8e5e-8910cce205d6`, reply `3179d562-3414-41bd-8e38-d91ec4bf03a5` accepted `PASS WITH CONDITIONS` and froze three R5-1 prerequisites: hidden anchor is appended after all user refs without changing numbering/presentation/tags; PackedLayout row ranges and positions for target/current-tail/user-refs/hidden-anchor/Audio are measured separately without custom row-order or position-ID rewriting; and the anchor remains the immutable Group 1 of the run lineage across replay, branch, and Review. - Formal verdict: `R5-0 CPU ARCHITECTURE AUDIT = PASS WITH CONDITIONS`. Production, public schema, Sampling v5, seed/SIGMAS, State, Session, Run Storage v3, Assembly, Release, A5, and general A8b remain unchanged/HOLD. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r5-dual-role-anchor-audit-20260906\R5_DUAL_ROLE_ANCHOR_AUDIT_JA.md` and `R5_CPU_AUDIT_RESULT.json`. ## Issue13 R4 Native Guided Overlap final GPU A/B (2026-09-06, VALID / FAIL / DO NOT PROMOTE) - After explicit GPU approval and the user's durable resource-policy correction, executed the frozen full pair in the required order. Fresh Standard A completed `6x5` and reproduced the R3B raw Video `6/6` plus Audio `6/6` exactly (`12/12`), then its Queue `0/0` backend was fully stopped before Fresh R4 B started. - R4 B completed `720` frames / `30.000s` Video and `30.000s` Audio with `6` finite raw AV groups and no OOM, allocation error, backend crash, NaN/Inf, packed-layout, AV-alignment, or duration hard stop. Hidden overlap did not extend final duration. - Formal verdict: `ISSUE13 R4 NATIVE GUIDED OVERLAP = GPU A/B VALID / FAIL / DO NOT PROMOTE`. Laplacian drift worsened from `+39.8675` to `+74.1887` (`+86.1%`), Video join was `2.1225 > 1.6598`, Audio join was `3.3896 > 1.6069`, highlight drift worsened `282.9%`, and gradient drift worsened `74.2%`. Saturation improved `63.0%` and the frozen motion floor passed, but they do not offset the primary failures. - B sampling was `22.0%` slower and peak backend RSS was `47.24 GiB` versus A `43.29 GiB`. Per user instruction, low free VRAM and RSS alone are advisory for future approved GPU runs; actual OOM/allocation/backend/integrity failure is the stop boundary. - Fixed task `H3情報チェック` completion review turn `a2e7fa47-e1ec-44c4-b83c-ff9e9872f25a`, reply `e7884bfc-6a46-4aad-8618-3ebead295311` accepted the verdict without mandatory correction. The result is limited to this frozen one-scene, one-seed condition; it does not invalidate Native Guided Overlap in general. - Do not retry, sweep, or promote R4. The next research candidate may be a CPU/read-only design audit of `Group 1 persistent anchor + current tail`, keeping Video and Audio intervention roles separate and preserving clean tail, State/Session/Assembly, Replay/Terminal/Review, and Core layout contracts. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r4-final-ab-20260906\R4_FINAL_AB_REPORT_JA.md`, `R4_FINAL_AB_RESULT.json`, `A_RAW_PARITY.json`, and the preserved A/B raw AV, videos, resource logs, decoded analyses, contact sheets, and boundary sheets. - A owned PIDs `40224/36876` and B `9164/41744` were each stopped after Queue `0/0`; port `8190` listener and HTTP are offline. User `8188` was absent and never operated. Production/runtime/contracts and commit/push/tag/release remain unchanged. ## Issue13 Standard Group 2 repeatability (2026-09-06, PASS / prior M3A divergence not reproduced) - After fresh explicit GPU approval, ran the frozen Standard Group 2 trace on three fully independent fresh 8190 backends. All three reproduced the R3B generated Video SHA `38e8eb8f...a188` and Audio SHA `2b482cfc...12d8` exactly. - Every run matched all `150/150` ordered trace boundaries and all `8/8` predict-noise, diffusion-forward, and sampling-step records. Different/missing were `0/0`, first divergence was `null`, runtime/model options/wrapper order matched, and hook transparency passed `3/3`. - Reverified the frozen model, CLIP, Video VAE, Audio VAE, Turbo8 LoRA, First Image, Core H3 nodes/model, KJ Sage patch, and shared Group 1 AV hashes. OOM, NaN/Inf, and unexpected backend crash were `0`. - Formal verdict: `STANDARD GROUP 2 REPEATABILITY PASS / PRIOR M3A DIVERGENCE NOT REPRODUCED`. This closes the Group 2 repeatability blocker but does not identify the earlier M3A cause and does not assess R4 efficacy. - Fixed task `H3情報チェック` completion review turn `0da950e6-2fc3-4c75-8a69-9daac82c9374`, reply `1d3c4727-9259-4832-8219-ae227a9477b1` accepted the verdict without mandatory correction. The next authorized proposal must resume the original frozen Gate order: fresh Standard A full `6x5`, require R3B raw AV `12/12` exact and no hard stop, stop A backend, then and only then run one frozen R4 B in another fresh backend. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-standard-group2-repeatability-20260906\STANDARD_GROUP2_REPEATABILITY_REPORT_JA.md` and `STANDARD_GROUP2_REPEATABILITY_RESULT.json`; raw traces remain under the prior M3B result root with `standard_group2_repeat_1` through `_3` case names. - Run 1 PIDs `18612/39884`, Run 2 `19416/39548`, and Run 3 `6968/4652` were each stopped after Queue `0/0`; 8190 listener and HTTP are offline. User 8188 was absent and not operated. Production/runtime/contracts and commit/push/tag/release remain unchanged. R4 B and final video were not run. ## Issue13 R4-M3B Group 2 GPU trace (2026-09-06, PASS / no divergence reproduced) - After explicit GPU approval, executed the frozen Group-2-only diagnostic in the mandatory order. The R3B control generated-region hashes reproduced historical Video `38e8eb8f...a188` and Audio `2b482cfc...12d8` exactly, so and only so the R4-M3A Standard harness ran in a separate fresh backend. - The two current traces are bit-exact through all 150 ordered boundaries: conditioning, pre-sampler latent/SIGMAS/noise/mask, eight `predict_noise` calls, all eight diffusion forwards, all sampling-step `x/x0`, sampler output and Group 2 generated Video/Audio. Different/missing are `0/0`; model options, wrapper order, memory runtime and PyTorch/CUDA settings also match. - The first raw comparator mismatch was only the isolated Python module location (`stage_r3b` versus `stage_r4`) for the same `model_patch.py` SHA and callable. Comparator post-processing now ignores only that capture-location string when source SHA/name/qualname match; capture contract remains frozen at SHA `39affe50...19c2`. Dedicated tests pass `13`. - Formal verdict: `R4-M3B GPU TRACE PASS / NO DIVERGENCE REPRODUCED / PRIOR M3A CAUSE UNRESOLVED`. The earlier R4-M3A output mismatch is not reproducible under this one frozen pair, so no internal first-divergence point or cause can be assigned. This one pair does not prove repeated determinism. - R4 Native Guided Overlap B, quality A/B, retry and sweep were not run. R4 quality remains unassessed and requires a new direction decision before any additional GPU work. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r4-m3b-first-divergence-20260906\R4_M3B_GPU_RESULT_JA.md`, machine result `R4_M3B_GPU_RESULT.json`, ordered comparison `R4_M3B_FIRST_DIVERGENCE.json` and both raw traces/logs. - Fixed task `H3情報チェック` completion review turn `d9289f52-2ed6-49f5-937a-73ca63e6efe3`, reply `ebb530f8-372d-4707-8636-84d3dc306980` accepted the verdict with no mandatory correction. It explicitly forbids calling this one-pair match `baseline recovery confirmed` and prioritizes a separate fresh-backend Standard Group-2 repeatability Gate before any R4 Native Guided Overlap quality A/B. - R3B backend PIDs `7608/35932` and R4 PIDs `35984/39160` were stopped after Queue `0/0`; port 8190 listener and HTTP are offline. User 8188 was absent and not operated. Production/runtime/contracts and commit/push/tag/release remain unchanged. ## Issue13 R4-M3A baseline parity root-cause audit (2026-09-06, first contract divergence identified / output cause unresolved) - CPU/read-only comparison of R3B baseline, the earlier R4 A `retry2`, and R4-M3 A `rerun2` found the first contract-level bit-exact break at Assembly Plan `chunks[0].context_frames`: R3B `5`, R4 shared-Group-1 harness `0`. - This metadata difference is not the Group 2 output cause: R4 `retry2` has the same value `0` and nevertheless matches every R3B Group 1-6 Video/Audio tensor bit-exact. `entry_to_state()` does not consume the plan's `context_frames` field. - The first saved tensor SHA divergence is Group 2's generated region: Video begins at latent `T=7`, Audio at `T=37`. The protected 7-slot/37-tick prefixes match the exact Group 1 tail and remain bit-exact. - Normalized prompt graph, Group 2 derived seed, shape, scheduler settings and CPU-reconstructed target/mask/noise recipe match. R3B did not capture actual conditioning, actual SIGMAS, pre-sampler latent, first-forward, or per-step SHA, so A/B/C internal classification remains unresolved. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r4-m3a-parity-audit-20260906\R4_M3A_BASELINE_PARITY_ROOT_CAUSE_AUDIT_JA.md` and `R4_M3A_FIRST_DIVERGENCE_AUDIT.json`. No GPU, backend, Production change, A rerun, B execution, commit, push, tag, or release. - After separate explicit user authorization, the fixed task `H3情報チェック` reviewed this CPU audit (turn `b9306a6b-b2da-486e-80d8-0b054eb80f76`, reply `7e67d0bf-783b-4a52-a2d7-d8d9cb2f6c16`). It accepted the formal verdict and the R4 B STOP. The next Group-2-only instrumentation must also capture model options, wrapper registration/order, attention patch identity and Dynamic RAM/runtime settings. The `context_frames=0` difference is not sufficient by itself to explain the output divergence; interactions are not excluded. - R4 quality remains unassessed. Any next in-sampling telemetry run requires a separately frozen diagnostic plan and fresh user approval immediately before GPU execution. ## Issue13 R4-M3 GPU rerun (2026-09-06, INCOMPLETE / A baseline parity stop) - After explicit GPU approval, corrected only the isolated observer runtime hook from the facade `v3.driving_nodes` to the actual Production binding `v2.nodes.run_sequence`; compile/static checks and R4 focused CPU tests passed `4/4`. Production source and installed runtime were unchanged. - Fresh-backend A `A_standard_6x5_s131325_rerun2` completed Group 2-6 Sampling and produced 720 frames / exact 30.000 seconds / 24 fps / 576x864 / 32 kHz stereo in `780.011 s`, with no OOM, allocation error, NaN/Inf, backend crash, layout, AV, or duration failure. - The mandatory pre-B check failed: frozen Group 1 Video/Audio remained exact, but Groups 2-6 Video/Audio did not reproduce the prior R3B baseline tensor bit-exact (`2/12` exact total). Derived seeds, prompt and geometry remained fixed; this is not a file-metadata-only difference. Per the frozen protocol, B and all retries/sweeps were not started, so R4 quality and the Group 5 B-A memory delta remain unassessed. - A Group 5 RSS was `41.715 GiB` before Sampling, `41.854 GiB` immediately after, and `41.846 GiB` after cleanup. Overall minimum available RAM was `2.989 GiB`, peak commit `72.219%`; no hard resource stop fired. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r4-native-guided-overlap-20260906\R4_M3_GPU_RERUN_RESULT_JA.md`. Dedicated 8190 Queue was `0/0` before stopping listener PID `34336` and launcher PID `34940`; HTTP/listener shutdown was verified. 8188 was not operated. No commit/push/tag/release. - Fixed-task completion review turn `c476af69-2f07-4dfb-a495-fea7f881199e`, reply `7259d478-7029-4077-9e8c-94d94f83ce78` confirmed the verdict with no mandatory correction. Next is a CPU/read-only-first bit-exact reproducibility cause audit; no further GPU A/B is authorized by this result. ## Issue13 R4-M1 Memory Ownership Audit (2026-09-06, PASS / GPU rerun awaiting approval) - CPU/read-only ownership audit found no R4-specific major leak or unbounded Group-to-Group retention. The R4 guide clones are call-local, share one tensor pair across conditioning entries, and are released with conditioning; fresh targets are not referenced by R4 conditioning. Existing full physical CPU entries and the latest continuation tail are bounded A/B-common ownership required by the current Assembly Plan. - Prior R4-3 wording is corrected to `R4-3 INCOMPLETE — SOFT RESOURCE THRESHOLD EXCEEDED`. Groups 2-5 sampled normally; the old 46 GiB exception fired before the Group 5 result returned to sequence cleanup. R4 remains a continuation candidate, not HOLD / FAIL. - CPU verification: weak-reference ownership check PASS; existing R4 6-Group and Terminal Merge shadow tests `4 passed`; modified isolated files compile. At 576x864 BF16 the R4-specific 22f guide clone is about 0.623 MiB video plus 0.0045 MiB audio, not a GiB-scale explanation for backend RSS. - The isolated R4 observer and test copy now treat RSS >=46 GiB as a Soft Warning, record Sampling-before/after and Group-cleanup snapshots plus system RAM/pagefile/commit/GPU/time, and defer resource stops until cleanup where possible. Production and installed runtime remain unchanged. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r4-native-guided-overlap-20260906\R4_M1_MEMORY_OWNERSHIP_AUDIT_JA.md`. The unchanged frozen R4-3 A/B GPU rerun is eligible only after fresh explicit user approval immediately before execution. - Fixed-task review was supplied/read: `R4-M1 PASS`, no mandatory correction, and Pre-GPU conditions may be presented. The required follow-up is an explicit A/B Group 5 comparison at Sampling-immediate and post-cleanup points. - R4-M2 Pre-GPU final freeze is `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r4-native-guided-overlap-20260906\R4_M2_PRE_GPU_FINAL_CHECK_JA.md` with machine freeze `R4_M2_PRE_GPU_FINAL_CHECK.json` SHA-256 `b31daaf81c00534df8811755d47b956ee27c16b34e00772722427fdaaef3c959`. - Fixed-task review turn `72fc3888-2e94-4911-a531-39598e855576`, reply `13c5d2dc-0013-436c-8d23-3c5bafd48ab0`: R4-M2 PASS WITH CONDITIONS. The one mandatory correction is applied: backend health failure now has mechanical process/API/stall criteria. Results must emphasize fresh-process run-internal RSS deltas. This review is not GPU authorization. ## V3.8 beginner manual plan and capture script (2026-09-06, draft ready / capture deferred) - Created the persistent Japanese manual design and Computer Use capture script at `docs/V38_BEGINNER_MANUAL_PLAN_AND_CAPTURE_SCRIPT_JA.md`. It is the canonical restart point for the later image-led V3.8 beginner guide. - The plan reuses the current exact `README_JA.md` Review walkthrough, separates Quick Start from reverse-lookup help, defines stable Shot IDs, capture prerequisites, environment records, filenames, abnormal-state coverage, a bug-report template, and completion checks. - Final screenshots remain deferred until the V3.8 public UI, standard workflow, and launch treatment of the active drift investigation are stable. A later instruction to start the manual must read the plan first and verify current labels before capturing `V38-M01` onward. - No Computer Use capture, runtime synchronization, backend operation, GPU generation, publication, commit, or push was performed in this planning step. ## Issue13 Texture-only RGB/VAE-delta Feedback Clamp (2026-09-06, FAIL / closed) - Static prototype/policy/source-order checks passed `13/13`, but the real fp16 H3 Video VAE feasibility gate failed before any Diffusion Sampling. GPU placement OOMed on the first 22f decode, including tiled retry: peak allocated `14,764,005,888` and reserved `16,280,190,976` bytes on the 16GB device. - Corrected `--cpu-vae` fallback was then attempted. After about five minutes its owned PID used `54,954,274,816` bytes working set, private allocation reached `163,648,221,184` bytes with paging, available RAM fell to about `6,658MB`, and Windows displayed a Python memory application error. The owned process was interrupted; available RAM recovered to about `56,262MB` and GPU free memory to about `14.9GB`. - Therefore the decoded-RGB `encode(corrected)-encode(decoded original)` path is operationally infeasible here and also conflicts with the protected V2 rule against Video/Audio VAE decode between H3 chunks. Close this concrete candidate; do not run its `6x5` efficacy A/B, switch to int8-only, lower resolution, CPU forcing, or threshold tuning automatically. - Production/source runtime is unchanged. No ComfyUI backend or listener was started; owned PIDs `9440` and `4472` exited. Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-texture-clamp-cpu-design-20260905\REAL_VAE_PREFLIGHT_RESULT_JA.md`. New GPU work still requires fresh explicit confirmation. A5/general A8b/Release HOLD remain unchanged. ## Issue13 Schedule-Matched Disposable Prefix screen (2026-09-05, closed) - Completion review faf8917a-b718-48e6-b40c-b380cc68c17a / reply26bc256c-bf10-49e8-b131-0d01e2740844 received/read: experimentPASS / this22f screenFAIL, no mandatory correction, pair closed. Report-only review; no independent media inspection. No next GPU phase authorized by this result. - User explicitly approved proposal execution and one frozen6x5 pair after integration gates. Experiment validity PASS / specified22f mitigation FAIL: edge drift39.8675→56.3675 (+41.39%); contrast/highlight guards failed, saturation/gradient/shadow passed. Flow mean0.510734→0.534240 (+4.60%); not full motion/semantic AV certification. No sweep or60s promotion. - Same savedGroup1 on both sides,10new physical groups total. A801.79s/B779.90s, each720f/30s. A rawAV12/12 exact vs baseline. Actual Core noise/seed/SIGMAS/inputmask/shape5/5 equal; conditioning/Assembly equal; B40H3 mask observations valid; cleanAV exports10boundaries exact. CPU14+protected85 PASS, assets10/sourceRegistry104/isolatedPython83 unchanged,Public7. Fullpytest not rerun. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-schedule-prefix-20260905\RESULT_JA.md`. Production/runtime unchanged; only isolated experiment and source state/history docs edited. A5/generalA8b/Release HOLD, no commit/push. Owned8190 PIDs13280/26320 and monitors stopped, listener offline; user8188 idle/reachable/unmodified. PreGPU fixed-task review26665e59 read before A; completion review pending at report creation. ## Issue13 R3B consolidated report / direction review (2026-09-05) - User requested consolidation of all completed R3B tests and direction review, not new GPU or Production changes. Ten30s runs/57physical groups/300s output; all completed, no accepted mitigation. Existing analysis equal_5s_windows and MP4 SHA were rechecked10/10. Do not substitute 3x10 chunk-center metrics for common5s windows. - Consolidated report: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r3b-consolidated-20260905\ISSUE13_R3B_CONSOLIDATED_REPORT_JA.md`. GPU_TEST_MATRIX.json retains exact values/provenance. HistoricalR2.6 remains a strong diagnostic positive, not a failed experiment; Video/Audio fixed-tail and motion confounds remain. R3B did not establish handoff-count-only causality or a motion-preserving fix. - Fixed H3情報チェック review received/read: turn4ee9d332-985c-49b5-8f3c-1e3c5186d3d2, reply7326b44b-f2b4-4828-a1f6-d8011f5113c3. Supports investigation progress/Production mitigation none/initiating bias unresolved. Reviewer read report only, not local media independently; broad exclusion language is restricted to the tested settings. - Proposed priorities only: reporter-exact differential, saved-data temporal/region analysis, then design one controlled same-prefix intervention if justified. No new intervention method approved or ready; temporal observations alone do not establish causality. No additional GPU, backend launch, Production fix or publication in this consolidation. A5/general A8b/Release HOLD remain. Source Registry104/104 unchanged; source edits only state/history documentation. ## Issue13 R3B non-Turbo Reference20 pair (2026-09-05) - User explicitly authorized only two matched non-Turbo20step30s Reference OFF/ON cases. Ref2VA pruned INT8, seed131325,6x5,Manual576x864,Standard/Balanced22,AudioON,FirstImage; no LoRA node executed. Production/runtime and general A5/A8b/Release HOLD unchanged. - Experiment PASS / this Reference mitigation screen FAIL. OFF1771.584s, ON1854.748s; each720f/30s AV,6physical groups. Laplacian delta25.1840→39.2554 (+55.87% larger, not a global quality score); saturation drift0.00238→0.01139 and highlight drift failed guards. Contrast drift improved58.05%; gradient/shadow nearly equal. No candidate accepted; one scene/seed does not reject native Reference generally or isolate Turbo causality versus prior8step. - Actual Core noise/seed/SIGMAS/mask/target-shape6/6 match; both21SIGMAS unchanged and modelpatches0. Clean Video/Audio prefixes each10/10 exact. Same FirstImage keyframe and persistent native Reference payload in all6 ON groups; Assembly equal except runtime start. Sampled identity/scene retained; similar ON poses are a caution, not proof of freeze. Full semantic AV/motion unqualified. - Evidence/report: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r3b-ref2va-standard20-20260905\ISSUE13_R3B_STANDARD20_REFERENCE_GPU_REPORT_JA.md`. Registry104/104, livePublic7/7 before/after,10assets unchanged,AST18,observerCPU anddiff-check PASS; fullpytest not rerun. Only state/history documentation changes. Existing Development mismatch1/254 remains separate. - Dedicated8190 launcher29056/backend29368 stopped19:14:23JST; PID/listener/HTTP,conhost32972 andmonitor exit verified. User8188 untouched. Monitoring370samples,minRAM0.995GiB,no safetyinterrupt. OuterPowerShell stale LASTEXITCODE check falsely returned nonzero after successful shutdown; independent exit checks confirmed success, no GPU rerun. - Current R3B total10runs/57physical groups, no accepted mitigation. Fixed-task completion review a9db6c24-27cc-4b15-b0c6-da908eb1702f received/read: experimentPASS/screenFAIL, no mandatory rerun. Clarified that Reference changes the first generated image too; compare each conditioning trajectory's own start-to-end change, not identical initial videos. Reviewer did not independently view local media. Approved pair closed; no additional GPU, multiseed/long-form, Production promotion or publication under this two-case approval. ## Issue13 R3B isolated context-noise GPU screen (2026-09-05) - User explicitly approved the proposed single-intervention Video context-noise experiment with "許可、許可。" after the Ref2VA review. This supersedes the earlier waiting-for-approval status only for this isolated A/B. Product A8b, A5 and Release remain HOLD. Production/runtime must stay unchanged. - Work directory: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r3b-noise-20260905`. CPU10/10 + existing69 protection tests, observer and5-boundary Shadow passed. Fixed-task review received; corrected Gaussian0.05 definition to a standard-deviation multiplier (not maximum amplitude), then ran only the approved pair. - GPU experiment PASS / this0.05 tapered Video-noise screen FAIL. OFF876.398s and ON830.900s, each720f/30s. Laplacian delta39.8675→43.9942 (+10.35% worse), saturation delta+47.25% worse; contrast/highlight/shadow partly improved. Motion proxy0.510734→0.336667 (−34.08%) and repeated sampled poses are cautions, not proof of complete freeze. No candidate accepted or Production promotion. - Fresh OFF raw Video/Audio matches prior baseline12/12. OFF/ON first raw AV exact, actual packed Core noise/SIGMAS/derived seeds6/6 exact, Assembly geometry and exogenous conditioning exact. Intended interventions5/5; newest slot delta0; clean Video/Audio prefixes each10/10 exact. Recursive Audio diverges fromGroup3 through joint generation but is never directly modified. - Registry104/104 and livePublic7/7 passed;10asset files rehashed unchanged. Source changes are only AGENTS, PROJECT_STATE, WORKLOG and the AGENTS hash row in Development Manifest. Pre-existing Registry-manifest mismatch remains1/254; package/Production source unchanged. Full pytest not rerun. Dedicated8190 launcher1972/child4128 stopped16:26:44JST; PID/listener/HTTP and monitor exit verified, user8188 untouched. - Report: `ISSUE13_R3B_NOISE_GPU_REPORT_JA.md`. Current exploration totals8runs/45physical groups, no accepted mitigation. This narrowly approved pair is complete; do not infer approval for a parameter sweep, another intervention, multiseed/long-form, or Production changes. Fixed H3情報チェック completion review received/read in turn4832f123-abeb-47de-9d97-56e25840a79c: experiment PASS / this condition screen FAIL; no mandatory correction or additional GPU. Reviewer did not independently view local media. Issue13 remains unresolved; A5/general A8b/Release HOLD remain. ## Issue #13 R3B Ref2VA paired GPU screen (2026-09-05) - Initial-screen review was received from fixed H3情報チェック task `6a94b91e-af7c-83e8-be18-ddc504f690c4` (turn `1ca3ed8b-f859-43d7-84ee-7459c3a87ce9`) before this phase. It supported matched Ref2VA Reference OFF/ON and retained the initial conclusion: no accepted mitigation; Audio OFF is mixed. - Ref2VA checkpoint + matching Ref2V8step LoRA, seed131325,6x5s,Manual576x864,Standard/Balanced22,AudioON: OFF and ON completed720f/30s AV in888.343s/918.375s. Reference connection was the only sampling-input delta. Laplacian increase was13.1606 OFF versus27.7282 ON (6.75%/13.20% from each starting value); native Reference did not meet the predeclared mitigation screen. Some secondary metrics improved, but no multi-seed/long-form promotion or Production fix is justified by this pair. - Raw Video/Audio prefixes each10/10 exact; actual public-call SIGMAS identical and unchanged; First Image latent exact between cases; same Reference payload present in all6 ON groups. Twelve pre-sampling Refine conditioning signatures were recorded without hooks or mutation. CPU noise replay6/6 matches are reconstruction, not actual-noise telemetry. Sampled identity/scene remained, but semantic AV and full temporal naturalness remain unqualified. - Report: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r3b-ref2va-20260905\ISSUE13_R3B_REF2VA_GPU_REPORT_JA.md`. Six current-environment30s cases/33physical groups total across both screens; Issue13 remains unresolved. Pair completion review was received and read (turn `b916ed28-cb5f-4587-8456-4a7bff915049`): experiment PASS / mitigation screen FAIL; no candidate promotion, no additional mandatory GPU for this screen. Next requires reporter-exact workflow or explicit single-intervention experimental approval. Context-noise interventions remain subject to A8b HOLD; generic GPU authorization does not waive its release conditions. A5 and Release HOLD remain. - Production/source runtime files unchanged; only project state/history recorded. Registry source/stage104/104 and live Public7/7 passed. Development Manifest's pre-existing stale REGISTRY_MANIFEST.sha256 entry (1/254 mismatch) remains separate. Full pytest not rerun. Dedicated8190 PIDs5792/3228, listener/HTTP and monitor exit verified at15:13:36JST, user8188 untouched. No commit/push/tag/release/publish. ## Issue #13 R3B initial GPU screen (2026-09-05) - GPU execution completed for four matched current-environment30s cases:6x5 baseline,3x10,6x5 with native Reference Image1,6x5 with Audio Continuity OFF. All21 physical groups and four720f/30s AV outputs succeeded; no accepted Issue13 mitigation yet. Longer chunks and clean Reference did not meet the frozen screen. Audio OFF reduced Laplacian drift41.83% but increased saturation drift51.25%; keep it diagnostic, not a recommended default. - Current FL2VA8step LoRA is not the unavailable historical4step LoRA. This is not reporter-exact R3. A/D first raw AV group is bit-exact; Video prefixes17/17 and Audio-ON prefixes12/12 are exact. CPU reconstructed noise parity is evidence replay, not actual Sampling-time telemetry. One seed/scene only; long-form, multiple seeds, semantic AV and wrapper matrix remain untested. A5/A8b remain HOLD. - Evidence/report: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue13-r3b-20260905\ISSUE13_R3B_INITIAL_GPU_SCREEN_REPORT_JA.md`. User explicitly authorized sharing this GPU audit only with pinned H3情報チェック task `6a94b91e-af7c-83e8-be18-ddc504f690c4`. Completion review was received before the paired Ref2VA-model native Reference gate; see the later phase above. - Source/runtime Production was unchanged. Dedicated8190 PIDs36076/28936 and its monitor were stopped and checked offline at14:15JST; user8188 remained live and untouched. Registry104/104 passes. Development Manifest has one pre-existing stale entry for REGISTRY_MANIFEST.sha256 (same bytes as pre-GPU snapshot), retained for separate Release Track correction. Full pytest was not rerun in this GPU screen. Release HOLD and publication prohibition remain. ## V3.8 Review Fixed-Seed Guard (2026-09-05) - `Run = Review Each Chunk` now requires the visible `Control After Generate = fixed` setting. With `randomize`, `increment`, or `decrement`, the Main card shows `Set Control After Generate to fixed`, explains that Base Seed must remain unchanged, and the frontend cancels Queue with the same exact instruction instead of silently creating another unrelated Chunk 1 revision. - `Try this chunk again` continues to create a distinct Take through the existing Review variation/nonce contract; users must not randomize Base Seed for it. Full Run and V3.7 or earlier nodes retain their existing Control After Generate behavior. - Run Storage reload now runs after `execution_success`, `execution_error`, and `execution_interrupted`, with the existing node-local execution callback retained as fallback. This makes completed, failed, and interrupted persistence states visible without changing Queue or Review intent. - The immediate README walkthrough now begins with `Control After Generate = fixed`. A separate image-led, exact-label, one-action-per-step beginner guide remains a required follow-up before release; it must describe a known-good `2 × 5s` path without internal terminology or inferred UI labels. - Focused Review/UI regression passed `116/116`; full pytest passed `1127/1127`; JavaScript syntax, Development Manifest `254/254`, Registry Manifest `104/104`, runtime verifier/public surface `7/7`, source/runtime SHA `2/2`, all four live served-extension markers, and `git diff --check` passed. - Public/backend schema, widget/socket order, Sampling v5, Run Storage v3, Branch/Take provenance, State/Session, Assembly, and GPU behavior remain unchanged. Release / Registry readiness remains **HOLD** pending package staging after this UI/documentation change. - Pre-change snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-review-seed-guard-filtered-20260905_024733-0a7c670` (`11/11`, mismatch `0`). ## V3.8 Review Completion Refresh + Step-by-step Guide (2026-09-05) - Confirmed the reported `2 × 5s` run was configured correctly and that the first 5-second output is the intentional first Review unit. Run Storage contained a valid canonical `review_ready` Chunk 1 with 33 Takes; the defect was the stale frontend view after execution, not missing backend generation or storage. - The V3.8 frontend now reloads Run Storage on ComfyUI's global `execution_success` event, with the existing per-node `onExecuted` hook retained as a fallback. The first load is immediate and one bounded 250 ms follow-up covers filesystem/UI timing without changing a widget, choosing an action, or automatically starting Queue. - `README.md` and `README_JA.md` now give a literal `Chunks = 2`, `Seconds per Chunk = 5`, `Total Length = 10 seconds`, `Run = Review Each Chunk`, `Progress = On — Resume and Takes available` walkthrough. It explains the intentional 5-second first result, all three visible Review buttons, the required second Queue, Back to Settings/Return to Review, and common mistakes using the exact UI labels. - Focused Review/UI regression passed `86/86`; full pytest passed `1126/1126`; JavaScript syntax, Development Manifest `254/254`, Registry Manifest `104/104`, runtime verifier/public surface `7/7`, source/runtime SHA `2/2`, live served-extension markers, and `git diff --check` passed. - Public/backend schema, serialized widgets, Review intent, Run Storage v3, Branch/Take provenance, Sampling v5, State/Session, Assembly, and GPU behavior are unchanged. Release / Registry readiness remains **HOLD** pending package staging after this frontend/documentation change. - Pre-change snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-review-refresh-readme-filtered-20260905_022621-0a7c670` (`10/10`, mismatch `0`). ## V3.8 Single-chunk Review Guidance (2026-09-05) - `Run = Review Each Chunk` with `Chunks = 1` no longer presents a misleading `Ready to Queue` card. The Main card now explains that the first chunk is also the last and directs the user to set `Chunks` to `2` or more before Queue to use Review and Continue. - The `Chunks` and `Run` mouse-over help carries the same instruction. This is diagnostic guidance only: values are not changed automatically and Queue is not blocked. - Public/backend schema, serialization, Run Storage v3, Review/Branch semantics, Sampling v5, State/Session, Assembly, and GPU behavior are unchanged. Release / Registry readiness remains **HOLD** pending package staging after the UI change. - Pre-change snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-review-single-chunk-guidance-filtered-20260905_010500-0a7c670` (`10` exact files, mismatch `0`). ## V3.8 Review Back to Settings (2026-09-05) - A canonical `review_ready` screen now includes `Back to Settings`. It restores the normal Main controls without changing the pending Review action, selected Take, canonical branch, Queue, or any serialized backend value. `Return to Review` returns to the three Review actions. - The normal `Ready to Queue` card shows the still-pending chunk Review while Settings are open. A newly completed review revision opens the Review screen automatically; the view toggle itself is transient and non-serialized. - This is Frontend presentation only. Public schema/sockets, Sampling v5, Run Storage v3, State/Session, Assembly, Branch/Take provenance, Seed/SIGMAS, and GPU behavior are unchanged. Release / Registry readiness remains **HOLD** pending package staging after the UI change. - Pre-change snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-review-back-to-settings-20260905_002018-0a7c670` (`8` exact files, mismatch `0`). ## V3.8 Main Core Controls + Card Alignment (2026-09-04) - Restored `Prompt Format`, `Continuity`, `Base Seed`, `Control After Generate`, and `Audio Continuity` as the first five normal Main controls, using readable facade labels while preserving the existing serialized backend widgets and values. These controls no longer require opening Advanced. - Fixed the custom Ready/warning/Review card draw contract. The card now always draws with its declared 62/68 px height instead of accepting an incorrect 20 px widget-height argument from the canvas callback, so the rounded border no longer crosses the headline or detail text. - Focused UI/schema passed `86/86`; full pytest passed `1124/1124`; JavaScript passed `7/7`; Development Manifest passed `254/254`; Registry Manifest passed `104/104`; source/runtime UI SHA matched; runtime verifier/public surface passed `7/7`; and `git diff --check` passed. Public Schema, sockets, Sampling, Run Storage, State/Session, Assembly, and GPU behavior remain unchanged. - Pre-change snapshots: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-main-core-controls-card-alignment-source-filtered-20260904_223526-0a7c670` (`10` exact files, mismatch `0`) and `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-main-core-controls-card-alignment-runtime-w-filtered-20260904_223526` (`2` exact files, mismatch `0`). The standard helper stopped only on the known `.pytest_cache` ACL. ## V3.8 Explicit Main Controls (2026-09-04) - Replaced the over-automatic Main facade with explicit, independent `Chunks` and `Seconds per Chunk` controls. `Total Length` is now a read-only calculation only; changing it cannot recalculate either generation setting. Values such as `3 chunks × 10 seconds` and `2 chunks × 15 seconds` are directly configurable again. - Removed the permanent Connected Inputs badges and automatic Input Mode row. `Size Source` is always visible and remains exactly `First Image` or `Manual` until the user changes it. First Image uses the existing Resolution choices; Manual shows the exact Width and Height directly. The facade no longer converts an inactive First Image into an apparently user-selected custom frame size. - If `Size Source = First Image` has no active First Image because it is missing, disabled, or bypassed, the Queue summary reports `Check First Image` and the exact fallback size without silently changing the selection. Reference Image and Video Guide size controls remain conditional inside Advanced. - Review-ready behavior remains the approved amber state with three explicit Queue actions. Public Python schema, sockets/order, serialized widget values/order, Sampling v5, Run Storage v3, State/Session, Assembly, Branch/Take, Seed/SIGMAS, and GPU behavior are unchanged. Focused UI/schema passed `86/86`; full pytest passed `1124/1124`. - The standard pre-change snapshot stopped only on the established `.pytest_cache` ACL. Accepted filtered snapshots are `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-explicit-controls-source-filtered-20260904_214419-0a7c670` (`10` exact files, mismatch `0`) and `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-explicit-controls-runtime-w-filtered-20260904_214419` (`2` exact files, mismatch `0`). Release / Registry readiness remains **HOLD** pending package staging after this UI change. ## V3.8 Mock-faithful Main UI (2026-09-04, superseded by Explicit Main Controls) - Reworked the presentation-only V3.8 Main facade to follow the approved mock hierarchy: active-input badges, automatic `Input Mode`, one `Video Length` selector plus `chunks × seconds` detail, conditional Output/Quality or Frame Size, Run, Progress, a Queue-ready summary card, and one Advanced disclosure. Existing serialized widgets remain behind that facade and keep their original values/order. - Input detection now follows effective graph state. A connected First Image, Video Guide, or Audio loader in ComfyUI bypass/never mode (`2`/`4`) or with its enable widget OFF is shown as inactive. This prevents the public workflow's bypassed optional loaders from falsely changing T2VA to I2VA or exposing irrelevant controls. - Review mode uses the second approved mock state only when Run Storage reports the canonical revision as `review_ready`: an amber chunk-ready card, `Use it and continue`, `Try this chunk again`, and `Use it and finish the rest`, followed by Render History and Advanced. Selecting an action does not auto-Queue and does not change the canonical branch until the normal Queue runs. - Public Python schema, input sockets/order, serialized widget values/order, Sampling v5, Run Storage v3, State/Session, Assembly, Branch/Take, Seed/SIGMAS, and GPU behavior are unchanged. Focused UI/schema passed `86/86`; full pytest passed `1124/1124`. Live visual acceptance remains for the user's next ComfyUI reload because the isolated browser route could not be used without joining an existing Edge process; no user tab was touched. - Pre-change snapshots: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-mock-faithful-ui-source-20260904_201500-0a7c670` (`327` files, mismatch `0`) and `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-mock-faithful-ui-runtime-w-20260904_201500` (`105` files, mismatch `0`). The dedicated validation backend on port `8190` and its exact temporary Edge profile were stopped; ports `8190`, `8188`, and `9223` were not listening at cleanup. Release / Registry readiness remains **HOLD** pending package staging after this UI change. ## V3.8 Complete Mouse-over Help (2026-09-04) - Added non-empty mouse-over help to all 12 Main facade controls, all nine visible Advanced controls, Review/Render History actions, and all 47 required/optional public V3.8 Sampler inputs. Tooltip text is stored on both the widget and widget options so current ComfyUI frontend paths can display it consistently. - `Output Size` now explains the selected behavior directly: First Image preserves the connected image aspect for I2VA/FL2VA, while Manual exposes exact 32-aligned Width/Height for T2VA, missing-First-Image workflows, or explicit canvases. Resolution, Resume & History, Reference Image Size, and Video Guide Size help also updates with the current selection. - This is help text and presentation metadata only. Widget names/order/values, sockets/types, Public `7/7`, Sampling v5, Run Storage v3, State/Session, Assembly, Branch/Take, Seed/SIGMAS, and GPU behavior remain unchanged. Focused UI/schema passed `85`; full pytest passed `1124/1124`; JavaScript passed `7/7`; Development Manifest `254/254`; Registry Manifest `104/104`. - Pre-change snapshots: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-all-hover-help-source-filtered-20260904_192259` (`326` files, mismatch `0`) and `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-all-hover-help-runtime-w-filtered-20260904_192318` (`105` files, mismatch `0`). The four changed Registry files are synchronized to ComfyUI_W with source/runtime SHA `4/4`; the live extension route returns the new help code. The already-running backend was deliberately not restarted, so new Python socket help becomes visible after the user's next restart. Eight unrelated source/runtime Registry mismatches predated this task and were preserved for a separate full-runtime sync decision. Release / Registry readiness remains **HOLD** until a tooltip-inclusive package staging Gate passes. ## V3.8 Intuitive Main UI Refinement (2026-09-04) - The compact facade now exposes `Generation = Full Video | Review by Chunk`, integer `Chunks`, compact `Seconds per Chunk`, `Output Size`, `Resolution`, `Resume & History = Off | On`, connection-specific Reference/Video Guide sizing, and one `Show/Hide Advanced Settings` button. Seed remains available inside Advanced Settings. - Chunks and Width/Height display without decimal places. Seconds display only a meaningful single decimal, so `3.000` and `5.000` render as `3` and `5` while values such as `5.5` remain available. `Review by Chunk` automatically enables the unchanged backend `Save + Auto Resume` requirement. - Review controls no longer appear merely because Review mode was selected. Before the first Queue, the UI asks the user to create the first chunk. Only a canonical Run Storage revision with backend status `review_ready` reveals `Keep & Continue`, `Try This Chunk Again`, and `Finish Automatically`; selecting one leaves a persistent Queue instruction instead of only a momentary button flash. - Empty Render History is hidden. Once at least one backend Take exists, the collapsed History button becomes visible and retains the existing N2c Take selection/actions. Video Guide and Reference Image sizing remain connection-driven. - This is Frontend presentation only. The serialized V3.8 widget order and values, Python/public schema, seven public nodes, Sampling v5, Run Storage v3, Branch Provenance, State/Session, Assembly, Seed/SIGMAS, and GPU behavior are unchanged. Focused UI passed `15`; full pytest passed `1120/1120`. - Source/runtime snapshots: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-intuitive-ui-prototype-source-filtered-20260904_144147` (`915/915`, mismatch zero) and `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-intuitive-ui-prototype-runtime-w-20260904_144128` (`179` files). The user-provided rollback ZIP remains unchanged at `D:\StabilityMatrix\Data\Packages\ComfyUI_W\custom_nodes\ComfyUI-H3-Continuum38_924.zip`, SHA-256 `6FF68ECA71DA9459C15EAB5B31480D65F03E2734E3ED3A2D86D7DCB024CB802D`. - Refinement snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-intuitive-ui-refinement-20260904_153802` (`9` exact source/runtime files). Synced only `web/project_id.js` and `REGISTRY_MANIFEST.sha256` to ComfyUI_W; hashes match, the live extension route returns HTTP 200 with every new marker, and runtime verification passes public `7/7`. User visual acceptance, README/CBT images, and package staging remain later work. **Release / Registry readiness = HOLD.** ## V3.8 Resolution / Size Source UX Refactor PASS (2026-09-03) - The user moved V3.8 test videos and test artifacts to `D:\output\video\comfy_video\v38`; the verified directory currently contains 868 files. Treat it as the current V3.8 output archive and preserve its contents. - Main V3.8 now presents only `Size Source = First Image | Manual`. First Image preserves the connected First Image aspect and reuses the existing Draft 0.30 MP, Balanced 0.60 MP, Native 768, Custom MP, 32-pixel alignment, and 1344 long-edge-cap resolver. Manual accepts exact aligned Width and Height and does not apply the preset. - Width and Height are appended after every existing serialized V3.8 widget. They remain visible, are read-only in First Image mode, and become editable in Manual mode. The frontend updates them from exact available First Image preview geometry before Queue; the backend remains authoritative and reports the final resolved canvas in Status. - The prior `aspect` key and its old values remain accepted as a hidden compatibility field. Frontend migration maps Auto to First Image and maps Landscape, Portrait, and Square to Manual using the exact former resolved canvas. API prompts that omit the new fields retain the legacy resolver path. - If First Image is selected but no usable First Image reaches the sampler, execution follows the project fail-open rule: the displayed Manual Width and Height are used deterministically and Status states the fallback. Reference Image and Video Guide are never implicit size sources. FL2VA without First Image therefore uses the same explicit Manual fallback. - Public node count remains `7/7`. The only Python schema change is the approved append-only `size_source`, `width`, and `height` UI contract; existing keys/order/sockets remain intact. Sampling Contract v5, Seed/SIGMAS, physical grouping, Run Storage v3, Branch Provenance, State/Session, Assembly, Driving Audio, Reference Audio, Second Pass/O1, and Terminal Merge are unchanged. - Validation passed focused `107`, full pytest `1117`, JavaScript `7/7`, Development Manifest `253/253`, Registry Manifest `102/102`, public workflow `19` nodes / `25` links / orphan `0`, protected contracts `16/16`, Python compile, and `git diff --check`. - Snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-resolution-size-source-ux-refactor-filtered-20260903_152559-0a7c670` (`320/320`, mismatch zero). Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-resolution-size-source-ux-20260903_153907`. - Accepted snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\accepted-v38-resolution-size-source-ux-final-20260903_160000-0a7c670` (`320/320`, mismatch zero). Formal result: **Resolution / Size Source UX Refactor = PASS**. Because the last staged ZIP predates this UX/schema/workflow change, **Release / Registry readiness returns to HOLD until a new package staging Gate passes**. GPU was unnecessary. On user request, ComfyUI_W was preserved in exact 199-file runtime snapshot `pre-v38-resolution-size-source-runtime-w-sync-20260903_163000`, then synchronized from the current 102-entry Registry Manifest. The initial four-file-only attempt exposed the expected missing N2b dependency `branch_provenance.py`; the complete manifest sync resolved it. Restarted only the command-line-verified ComfyUI_W backend at `127.0.0.6:8188`; live `object_info` and frontend routes now pass public registration `7/7`, Size Source/Width/Height schema, and current `project_id.js`. No commit, push, tag, release, or publish was performed. ## ComfyUI_W Reference-Audio / Installer Sync PASS (2026-09-03) - Treated the already-correct ComfyUI_W implementation as authoritative for this limited synchronization. `reference.py` now adds each bundled Reference Audio individually and in order when Reference Image conditioning is also present; legacy single-Audio behavior remains unchanged. - Added the public-surface verifier helper to the package allowlist, made the Windows installer stop explicitly when that helper is absent, and included the runtime dependency `v3/reference_video.py`. Registry Manifest is now `104/104`; Development Manifest remains `253/253`, both with zero mismatch. - Focused source regression passed `18`; it includes the new Reference Image + Audio 1/2/3 presentation and `minimax_refs` ordering test. Stage-only import and runtime verifier both passed with public `7/7`. No runtime synchronization, backend/frontend operation, GPU, commit, push, tag, release, or publish occurred. Release / Registry readiness remains HOLD pending official package staging. ## V3.8 Final Package Staging Re-Gate PASS / Release readiness GO (2026-09-03) - The latest 320-file working tree was staged through official `comfy-cli 1.18.0`. The first current-tree archive exposed one packaging-only gap: historical validation/design documents, old-version UI images, `.github`, `.gitignore`, and `pytest.ini` were still included. - The minimal correction changed only `.comfyignore` plus the two Manifests. Historical/internal docs and repository-only configuration are excluded; only the current N2b, O1, and V3.8 release/migration contracts are retained. Production Python/JavaScript/workflow/schema/Sampling/Run Storage/State/Session/Assembly code is unchanged. - Official `comfy node validate` and `pack` exited zero. The final archive contains 103 files, is 349704 bytes, and has SHA-256 `9675373D8BD37A345D4467BF3BDB6E869EA3BFE051B730E316AE338A60B0D97F`. - Source→stage and stage→archive missing/extra/mismatch are all zero. Registry Manifest is `102/102`; Development Manifest is `253/253`. Duplicate, unsafe, zero-byte, banned internal, secret, user-specific-path, and temporary-log findings are all zero. - Isolated stage-only import passed with no repository fallback. Public class/display/category/schema is `7/7`; AUDIO-R1 helper/backend/frontend/socket and O1 Second Pass finite validation/contract are present. The package contains exactly the two required `tools/` runtime files and one V3.8 public workflow with no orphan/duplicate links or old/experimental nodes. - Validation passed focused `126`, full pytest `1086`, JavaScript `7/7`, runtime verifier, protected contracts `16/16`, and `git diff --check`. GPU was not run. - Snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-v38-final-package-staging-regate-filtered-20260903_141442-0a7c670` (`320/320`, mismatch zero). Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\v38-final-package-staging-regate-20260903_141519`. - The designated `H3情報チェック` task accepted **V3.8 Final Package Staging Re-Gate = PASS**, found no mandatory correction or additional Gate, and approved **Release / Registry readiness = GO**. Commit, push, tag, GitHub Release, Registry publish, and all other publication remain separate explicit-approval actions and were not performed. ## Issue #19 Chunk Boundary Continuity PARTIAL REPRODUCTION (2026-09-03) - The reported severe video/audio cut resembling separately joined clips was not reproduced under the wrapper-free V3.8 baseline. Dedicated `8190` completed `1x5`, `2x5`, `3x5`, `2x10`, and matched-seed `2x5` explicit-prompt cases; optional `3x10` was safely omitted after the `2x10` run reduced available system RAM to about `0.004 GiB` without exposing a new anomaly. - Video and Audio latent prefixes were bit-exact at all five physical boundaries. Separately decoding each physical group nevertheless made the same 22-frame RGB overlap non-bit-exact at `5/5` boundaries and increased the visible-join frame MAE by `10.657–21.899%` relative to the raw same-group prefix-to-generated transition. Finalized boundaries remained non-outliers (`0/5`) with SSIM `0.953167–0.972468`; no severe visual cut or trajectory restart was observed. - Audio had no silence or dropout. Five-second Seam-OFF splice jumps remained below each case's ordinary adjacent-sample P99.9, and existing Audio Seam Auto reduced them from about `0.0958–0.0964` to `0.00354–0.01428`. The accepted FL2VA Terminal `[1]+[2,3]` evidence also showed no new video or audio cut and preserved Terminal atomicity. - Issue #13 remains a separate cumulative Group 4–6 recursive-feedback pattern. The immediate weak decode-context effect observed here starts at Group 1→2 and did not worsen through three groups. Prefix corruption is rejected for both; Fixed Prefix remains diagnostic-only and was not run for Issue #19. - Formal cause status: **separate-decode context asymmetry is a reproducible low-level candidate, but causal contribution to the reporter's severity is unproven**. Production remains unchanged. Further promotion requires either reporter-exact reproduction or a cache-only A/B of the same saved latent through separate versus consistent-context/overlap-aware Video VAE decode. - Validation passed focused `72`, full pytest `1086`, development Manifest `253/253`, Registry Manifest `141/141`, runtime/public export `7/7`, pre-Gate snapshot comparison `320/320`, and `git diff --check`. Dedicated `8190` was stopped after Queue `0/0`; the temporary probe was removed; `8188` and the user Frontend were untouched. - Evidence: `D:\Codex\_test_results\ComfyUI-H3-Continuum\issue19-chunk-boundary-continuity-20260903_130500`. Pre-Gate snapshot: `D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-issue19-chunk-boundary-reproduction-filtered-20260903_130348-0a7c670` (`320/320`, mismatch zero). - The designated `H3情報チェック` task formally accepted **ISSUE19 PARTIAL REPRODUCTION**, found no mandatory correction or additional GPU requirement for this Gate, and agreed that no Production change is justified. Release / Registry readiness remains HOLD; no commit, push, tag, or release was performed. ## V3.8 AUDIO-R1 Multi Reference Audio 1/2/3 PASS (2026-09-03) - Core ComfyUI 0.34.2 formally supports up to three standalone `ref_audios`, presents them to the tokenizer in connection order as `