# v3.9.11 — Spectrum signature stability / Review continuation ## What changed Fix an additional confirmed cause of false Sampling v6 read-only. Repeated imports of unchanged audited Spectrum source can produce different marshal bytes for equivalent normalized code objects, reproduced on Python 3.13.12. The legacy audit remains first. Only differences confined to function code digests can invoke fixed Python 3.12/3.13 supplemental profiles; all loaded descriptors, source hashes, provenance, defaults, closures and runtime state must still pass. Unknown or modified code remains non-reusable. The original four provider metadata files and persisted Sampling v6 identity are unchanged. Four genuine pre-repair safe v6 Take fixtures retained identical full contracts and reused their saved Chunk 1. Old unsafe/v5 Takes stay readable and read-only; no flags or manifests are rewritten. Public node IDs, inputs, widget order, Graph v4, Run Storage and official workflow JSON/ZIP bytes remain unchanged. No provider import, profile generation or identity learning occurs in the runtime audit. ## Validation - Full CPU/JavaScript gate: **2,139 passed / 2 skipped / 2 known Inspector expected failures / zero unexpected failures**, zero CUDA initialization. Existing 90-case Queue JS coverage is included, not an additional total. - Targeted Python 3.13: 212 passed / 1 skipped. Python 3.12.10 component gate: 155 passed / 1 skipped / 21 deselected. Those 21 depend on an independent older-Core Attention observation limitation and are not accepted here. - Real-Core CPU observer/storage fixtures matched 53 expected decisions (30 reusable, 23 intentionally refused) and the production JS predicate. These fixtures execute no Attention kernels or H3 inference. Old unsafe/v5 refusal and changed/unknown-code rejection remain tested. - Both supplemental profiles regenerated byte-for-byte with reversed provider and module import order. Compilation and offline twelve-node registration passed. Legacy metadata and official workflow bytes remained unchanged. - **Browser + GPU:** Review buttons enabled with Spectrum + Comfy Kitchen Attention. The browser's Continue From Here action retained **Chunk 1** and generated **Chunk 2**, **one reused / one new**. Both new Takes were reusable, parent links were correct, and the saved Chunk 1 raw/Take/manifest stayed unchanged. Two Queues completed without execution errors or OOM; both MP4s fully decoded video and audio (5 s / 120 frames; 10 s / 240 frames). GPU scope: Windows, Python 3.13.12, ComfyUI Core 0.42.1, PyTorch 2.14.1+cu130, Comfy Kitchen 0.2.39, RTX 5060 Ti 16 GB, audited installed 44-file local Spectrum provider ON, Kitchen launch option and ModelAttentionBackend selected, Sage OFF. T2VA 512×512, 24 fps, two 5-second chunks, 8-step Turbo, Euler/simple, first pass only. Audited KJ Preview Override was enabled with optional VAEs disconnected and Tiny VAE none. This tests the repaired product payload before release branding; it is not a fresh GPU run of the published tag. No reporter-exact reproduction, all-provider GPU matrix, Second Pass acceptance, subjective visual/audio quality, benchmark or CUDA-kernel return tracing is claimed. The supplemental path was demonstrated by CPU reproduction; whether it was invoked in the live GPU run was not traced. Older Core 0.39.2 with Kitchen 0.2.37 has a separate unobservable prequantize_int8_attention helper; that setup remains non-reusable and is not fixed by this release. ## Update and check Update the existing copy through ComfyUI Manager, or replace the custom-node package in `ComfyUI/custom_nodes/ComfyUI-H3-Continuum`. For a Git installation, update that same folder from main. Avoid duplicate installations. **Fully restart ComfyUI and hard-refresh the browser with Ctrl+F5.** Keep existing Takes, workflows and model files. Use a **new, unique Run Name**, enable Spectrum and Review Each Chunk, and generate Chunk 1. Select its new Take in Render History; check Use This Take / Continue From Here, then continue to Chunk 2. Existing read-only Takes are not automatically made reusable. No workflow rewiring or Take deletion is required. ## Separate MP4 menu-thumbnail workaround Custom Scripts' Show Image On Menu can request an MP4 through Core's image preview endpoint, causing an HTTP error despite successful generation and valid video files. If encountered, search Settings for **Show Image On Menu** and turn it **OFF**. A browser load/save of an existing MP4 after this setting change produced **zero new thumbnail HTTP errors**. The test performed no new inference. This is a separately verified setting workaround, not a Continuum/Core/Custom Scripts code change; this update does not alter the setting automatically. ## 日本語 同じ監査済みSpectrumを再読込した際、コードが同等でもmarshalの保存表現が変わり、 新規Takeが誤ってv6 read-onlyになる条件を修正しました。旧監査を優先し、コードハッシュ だけが異なる場合に限り固定プロファイルで全記述を照合します。未知・改変コードの 再利用拒否、元のSampling v6署名、正常な既存Takeの互換性を維持します。 過去のunsafe/v5 Takeを自動的に再利用可能にせず、既存Take・公式ワークフローを変更しません。 CPU/JSは2,139成功・2スキップ・既知Inspector期待失敗2件、予期しない失敗0。 Spectrum+Kitchen Attentionの対象を限定したブラウザー/GPU検証ではReviewボタンが 有効となり、Chunk 1保持・Chunk 2生成(再利用1/新規1)と両出力の映像・音声の全デコードを確認。 検証は上記構成の修正版payloadに対するもので、公開タグのGPU再実行、全構成、画質・速度、 報告者環境の完全再現を保証するものではありません。旧Core/Kitchenの独立した制約も残ります。 Managerまたは既存custom-nodeフォルダーを更新し、ComfyUIを完全に再起動、Ctrl+F5で更新。 一意な新しいRun NameでSpectrumとReview Each Chunkを有効にしてChunk 1→2を確認してください。 MP4メニューサムネイルの別拡張由来HTTPエラーは、SettingsのShow Image On MenuをOFFに する回避方法を確認済みです。コード修正や設定の自動変更は含みません。