release: publish H3 Continuum V3.8X (3.8.1)

This commit is contained in:
ukr8b3g-cmyk
2026-09-15 03:46:57 +09:00
parent c421913bf1
commit 764179869f
62 changed files with 5707 additions and 2018 deletions
+93
View File
@@ -0,0 +1,93 @@
# R0 Failure Semantics Baseline
Date: 2026-09-14
Scope: current V3.8 Python-exception behavior
Storage root: pytest `tmp_path` only
## Isolation contract
すべてのfailure injectionは一時Run Storage rootで実施した。
```text
real h3_continuum storage touched: NO
existing Take / revision touched: NO
user backend 8188 touched: NO
GPU used: NO
public workflow changed: NO
```
このbaselineは、catch可能なPython exceptionが`RunStorageController.__exit__()`へ到達する場合を記録する。OS強制終了、電源断、process killの挙動を成功扱いしない。
## Results
| Injection point | Committed records after cleanup | Manifest status | Canonical pointer | Current observable behavior |
|---|---:|---|---|---|
| before Sampling | 0 | `interrupted` | none | errorを記録し、review pause metadataを除去 |
| after Sampling / before chunk commit | 0 | `interrupted` | none | sampled resultは永続化されない |
| after first entry of terminal physical group | 1 | `interrupted` | none | terminal pairの片側raw/recordがinterrupted revision内に見える |
| before manifest update (one-shot exception) | 1 | `interrupted` | none | in-memory recordを`__exit__()`が再度manifestへ書き、interruptedとして回収 |
| after manifest update | 1 | `interrupted` | none | committed recordを保持してinterrupted化 |
| before output projection | 1 | `interrupted` | none | recordを保持してinterrupted化 |
| during output projection | 1 | `interrupted` | none | recordを保持してinterrupted化 |
| before storage finalize | 1 | `interrupted` | none | in-progress recordを保持してinterrupted化 |
| before canonical pointer update (first `_write_project`) | 1 | `interrupted` | none | finalize途中のmanifestをexception cleanupがinterruptedへ戻し、2回目のproject writeはcanonicalを設定しない |
Assertions are implemented in:
```text
tests/test_runtime_redesign_r0_characterization.py
```
## Current write ordering
### `commit_chunk()`
```text
validate one logical entry
→ write temporary safetensors
→ fsync temporary
→ os.replace to chunk_000N.safetensors
→ fsync chunks directory
→ construct one record
→ replace manifest chunks in memory
→ write manifest
```
この処理はphysical group単位ではなくlogical entry単位である。terminal merged pairでも、1件目commitと2件目commitの間に例外が起きる窓がある。
### `finalize()`
```text
validate committed prefix and Session length
→ set status / review metadata
→ write manifest
→ build branch provenance
→ write manifest again
→ write project with set_canonical=True
```
Python exceptionが上位のstorage scopeへ戻れば、`__exit__()`はstatusを`interrupted`へ変更し、canonical指定なしでprojectを再書込する。
## Process-crash limitations
このR0 testは、次を保証しない。
- `os.replace(raw)`直後、manifest更新前にprocessが消失した場合のorphan raw回収
- 既存`chunk_000N.safetensors`を上書き中にprocessが消失した場合の旧manifest/raw整合性
- terminal pairの両entryを不可分にpublishすること
- manifest provenance書込後、project canonical更新前にprocessが消失した場合の再起動時selection
これらはR5のprocess-crash consistency対象である。R0でwrite orderやschemaを変更していない。
## R5-approved delta boundary
将来R5で許可される差分はV9どおり次に限定する。
- physical group全entryを先にvalidate
- immutable transaction raw filenames
- raw durabilityとSHA verification後にmanifestを1回でswitch
- `commit_group()`はcanonical pointerを更新しない
- canonical pointerはsuccessful finalize後だけ更新
Sampling結果、Session/State/Assembly、Review user-visible semantics、Run Storage v3 readabilityは変更しない。
+90
View File
@@ -0,0 +1,90 @@
# Failure Semantics Delta — R5
Date: 2026-09-14
Status: R5 Design Delta PASS / Implementation PASS / Validation PASS
Baseline: authoritative ComfyUI_W dirty tree, with R0–R4 PASS before R5
## Approved differences
R5 may change only these two externally observable failure details.
### D1: terminal physical-group manifest visibility
Previously, the first logical entry of a terminal merged pair could become
visible in an interrupted manifest before the second entry was committed.
R5 publishes all records of that physical group in one manifest replacement.
An incomplete terminal group is never manifest-visible.
After all raw files have been written and verified, catchable Python exceptions
may recover the entire terminal group as `interrupted`. They may not recover
only one logical half.
### D2: immutable transaction raw names and orphan layout
Legacy raw name:
```text
chunks/chunk_000N.safetensors
```
R5 raw name:
```text
chunks/rev-<revision>-txn-<transaction-id>-chunk-000N.safetensors
```
The reader continues to accept the legacy filename stored in existing v3
manifests. A retry uses a new transaction filename and never overwrites a raw
file referenced by an older manifest or Take. A process stop may leave an
unreferenced raw or temporary file. R5 does not adopt, promote, or delete that
orphan automatically.
## Manifest switch definition
```text
write a complete candidate manifest to a unique temporary file
→ flush and fsync the temporary file
→ atomically replace the active manifest
→ run the available directory durability helper
```
The completed atomic replacement is the **manifest visibility switch**. The
subsequent directory helper completion is the **manifest durability
completion**. Process-stop tests observe the state before replacement,
immediately after replacement, and after the directory helper separately.
On Windows, atomic replacement and media-level durability are not treated as
equivalent. The current Windows directory helper is a no-op; validation records
that limitation and does not claim power-loss or OS-crash durability.
## Behavior that remains unchanged
- non-terminal accepted-prefix meaning and resume position
- manifest status and Review/Take behavior
- canonical eligibility, fallback selection, and pointer meaning
- Sampling, Projection, and finalize failure semantics
- accepted chunk tensors, seeds, prompts, Session, State, and Assembly data
- Run Storage v3 schema readability
- Storage OFF filesystem-I/O behavior
`commit_group()` writes physical-group raw files and publishes their records.
It never updates the canonical project pointer. Canonical promotion remains in
the existing successful-finalize path.
## Process-stop acceptance
- Before manifest replacement, a fresh reader sees the previous complete
manifest. Any new raw files are unreferenced orphans.
- After manifest replacement, every raw referenced by the new manifest exists,
has the recorded size, and matches the recorded SHA-256.
- At the replacement boundary, the active file is a complete old manifest or a
complete new manifest. A partial JSON file and a half terminal group are
invalid.
- A forced process stop does not run `__exit__`; it is not required to change
status to `interrupted`.
- Existing canonical fallback selection is preserved even in windows where the
project pointer has not yet been replaced.
The test fixture covers raw-write, raw-verification, manifest-temporary,
manifest-replace, directory-helper, finalize-manifest, and project-pointer
boundaries with a separately terminated worker and a fresh reader.
+256
View File
@@ -0,0 +1,256 @@
# Runtime Redesign R0 Characterization
Date: 2026-09-14 (Asia/Tokyo)
Phase: R0 only
Architecture changes: none
## 1. Authoritative baseline
R0の正本は、開始時点の次のdirty treeである。HEADや別cloneへ置き換えない。
```text
authoritative_runtime_path:
D:\StabilityMatrix\Data\Packages\ComfyUI_W\custom_nodes\ComfyUI-H3-Continuum
branch: main
HEAD: c421913bf1311050ac10a6d782ce40f9e72be852
Python: 3.13.12
Torch: 2.14.0+cu130
ComfyUI: 0.35.1
GPU initialized by R0: NO
user backend 8188 touched: NO
```
開始時点には既存のtracked変更と、次のuntrackedファイルがあった。すべてユーザー作業として保持した。
| Untracked file | SHA-256 |
|---|---|
| `examples/workflows/MiniMax_H3_Continuum_V38.json` | `9772DD1A82C20FD0D6F40AE7CD2B2F11DFB81641B86515ADB17C6555ADA7AFF3` |
| `examples/workflows/MiniMax_H3_Continuum_V38.zip` | `9B684C37EBFE116FCB5C68032B82E5D49279325548C48494F23B3309BB211924` |
| `tests/test_audit_boundary_repairs.py` | `FE23752312D62DDC8C23A3C598ED2F92F2D46E2E4460F06AEA91921659092451` |
Workflow ZIP内の唯一のentryは`MiniMax_H3_Continuum_V38.json`で、展開JSONのSHA-256は上表のJSONと一致した。
Baseline diff artifact:
```text
D:\Codex\_test_results\ComfyUI-H3-Continuum\r0-runtime-redesign-20260914\BASELINE_WORKTREE.diff
```
Snapshot:
```text
verified:
D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-r0-runtime-redesign-verified-excluding-pytest-cache-20260914_021621
files: 892
partial attempt (Copy-Item was denied by .pytest_cache ACL):
D:\Codex\_snapshots\ComfyUI-H3-Continuum\pre-r0-runtime-redesign-20260914_021557
```
Verified snapshotは`.git`とアクセス不能だった`.pytest_cache`だけを除外し、source/destination file countを一致確認した。
## 2. Baseline validation
R0変更前:
```text
full CPU pytest: 1187 passed, 1 skipped, 1 warning, 62.18 s
frontend_review_queue.cjs: 46 passed
tools/verify_runtime.py: PASS
registered public nodes: 7
```
実ComfyUI Queue、GPU、VAE DecodeはR0の対象外であり未実行。
## 3. Continuation source baseline
### 3.1 Storage OFF
| Inputs | Accepted prefix | Effective generation start | Continuation state | Current result |
|---|---:|---:|---|---|
| none | 0 | Chunk 1 | none | fresh Full Run |
| compatible explicit Session with 1 accepted chunk | 1 | Chunk 2 | last accepted Session entry | prefix reuse |
| Session + `Regenerate From = 2` | 1 | Chunk 2 | Session Chunk 1 | Chunk 2以降を再生成 |
| incompatible explicit Session | 0 | Chunk 1 | none | Sessionをadvisory rejectしてfresh run |
| initial State only | 0 | logical Chunk 1 | supplied State | generated plan is continuation and increments State `clip_index` |
| compatible Session + valid State | Session prefix | prefix後 | Session last entry | StateはSession検証前に抑止 |
| invalid Session + valid State | 0 | Chunk 1 | none | Stateへfallbackせずfresh run |
| initial State + invalid `Regenerate From > 1` | n/a | n/a | n/a | `SequenceRuntimeError` |
重要なV9との差分: 現在の`_preserved_prefix()`はSession validation、resolution、duration、identity不一致を例外として外へ出さず、noteを付けて空prefixを返す。このため、V9の「invalid/incompatible Sessionなら既存Sessionエラー」は現行実装の事実ではない。
実際の現行結果は次である。
```text
Session present + initial State present
→ initial State = None
→ Sessionを検証
→ Session invalid/incompatibleならSession prefixを0件へ落とす
→ initial Stateには戻らない
→ fresh Chunk 1を生成
→ reportへ "saved session was ignored; generated a fresh run (...)"
```
したがってR1以降で維持すべきbaselineは、ユーザーが別途変更を承認しない限り「no State fallback + advisory fresh run」である。
Storage OFF characterizationでは、Run Storage Review policy invocationは0、Run Storage filesystem I/Oは0だった。
### 3.2 Run Storage ON
| Inputs / saved state | Current result |
|---|---|
| explicit Session present | `RunStorageError: Run Storage cannot be combined with an explicit Session`。storage書込前に停止 |
| validated saved prefix + initial State | saved prefixが優先。Stateはcontinuation sourceにならない |
| no saved prefix + initial State | initial Stateを使用 |
| Review Continue | review decisionを作成後、prefix実読込後にreconcileして再度decisionを作成 |
現在のReview Continue decision-producing pathを隔離すると、pure policy callは2回だった。
```text
_resolve_review_contract()
→ resolve_review_execution() # first decision
→ prefix selection/load
→ _reconcile_review_execution_with_reused_prefix()
→ resolve_review_execution() # second decision
```
`_validated_review_head()`も同じpure functionをmetadata validationに使用するが、その戻り値はQueue decisionではない。R2の「Decision 1回」は上記decision-producing 2経路を1経路にする課題であり、R0では変更していない。
## 4. ContinuationSourceFacts mapping baseline
この型とprojection関数はR0時点のsource treeには存在しない。R3/R4で新しい意味を作らないため、現行runtime値からのmappingを次で固定する。
| selected kind | `accepted_chunks` | `reroll_from_chunk` | `physical_group_boundaries` |
|---|---:|---|---|
| `run_storage` | 実際にraw検証とloadを通過した`best_entries`数 | final branch contractの有効boundary。通常continueは0 | accepted prefix内で完全に成立した現行physical groups |
| `explicit_session` | `_preserved_prefix()`が受理したentries数 | explicit Session経路の実効`reroll_from_chunk` | terminal atomicity適用後、accepted prefix内で完全に成立したgroups |
| `initial_state` | 0 | 0または現行で許可される1 | empty tuple |
| `none` | 0 | 0(plain Full Run baseline) | empty tuple |
`initial_state`はaccepted raw prefixではない。logical Chunk 1のSamplingにcontinuation stateを供給するだけである。
## 5. Current validated-prefix representation
R0 source treeには`ValidatedPrefix`、`EmptyValidatedPrefix`、`PrefixFacts`、`ContinuationSourceFacts`、`to_planning_facts()`はまだ存在しない。現在は次のmutable valuesへ分散している。
- `review_head`: `revision_id`, `status`, `validated_prefix_count`, `review_unit`, `branch_regenerate_from`, `effective_reroll_nonce`, `updated_utc`, `manifest`
- `best_entries`: raw existence、SHA-256、entry contractを通過して実際にloadされたentries
- `best_records`: accepted entriesに対応するmanifest records
- `RunStorageController.reused_count`: `len(best_entries)`
- `RunStorageController.review_execution`: prefix load前decisionを、load後reconcileで置換した値
よってV9の`ValidatedPrefix.to_planning_facts() -> PrefixFacts`は「現行契約」ではなく、R2で導入する将来契約である。R0でその型を追加するとR1/R2実装へ先行するため、追加していない。R2で導入する場合も戻り型を`ContinuationSourceFacts`へ流用しない。
## 6. ReviewUnit inventory
Productionの`ReviewUnit`定義は1種類だけである。
```text
v3/review_control.py
class ReviewUnit(start, end, physical_group)
```
Production usage:
- `v3/review_control.py`: unit作成、normalization、pause metadata、Review/Take policy
- `run_storage.py`: import、review group marker、pause metadata validation、finalize validation
- `v3/nodes.py`: `review_execution`からprojection rangeを読む。別`ReviewUnit`型は定義しない
R0検索では別の`class ReviewUnit`は存在しなかった。
## 7. Required behavior coverage map
新しいR0 testは`tests/test_runtime_redesign_r0_characterization.py`に隔離した。既存fixtureと合わせた代表coverageは次の通り。
| Contract | Characterization coverage |
|---|---|
| Review Q1 → next → complete | `test_limit_one_returns_one_new_chunk_and_prefix_assembly`, `test_prefix_five_generates_only_chunk_six_and_completes`, L0/L1 storage tests |
| Regenerate Current | N0-N5 and terminal regenerate tests in `test_v38_review_run_storage.py` |
| Finish Remaining | `test_n5_finish_remaining_keeps_current_branch_nonce`, `test_finish_remaining_complete_records_the_final_generated_group` |
| Use This Take / Continue From Here | N2B take-selection, canonical, and continue tests |
| Back to Settings compatible extension | `test_i2va_two_to_three_reuses_both_canonical_prefix_chunks` |
| terminal physical group | terminal atomic tests in execution-cap and Run Storage suites |
| Session/State precedence | new R0 characterization tests |
| Balanced 22 / Strong 39 | new parametrized R0 characterization test |
| Reference Image / Audio and Refine Context | `test_audit_boundary_repairs.py`, `test_v35_context_sampler.py` |
| Video Reference | `test_p46a_reference_video_memory.py` and sequence contract tests |
| Timeline Video | `test_timeline_video.py` |
| Driving Audio | `test_v34_driving_audio.py` |
| Second Pass | `test_v35_second_pass_contract.py`, `test_v35_second_pass_sampling.py`, selective node tests |
| external wrappers | graph-contract Turbo/Sage tests and `test_model_patch.py` |
## 8. Hardening signature baseline
`hardening.run_sequence_with_hardening()` calls `inspect.signature(base).bind_partial(...)`. The current keyword-only `run_sequence` signature contains 41 parameters, in this order:
```text
model
clip
video_vae
audio_vae
sampler
sigmas
first_frame
last_frame
prompt_plan
width
height
continuity
base_seed
audio_continuity
exact_total_duration
diagnostics_mode
reroll_from_chunk
reroll_nonce
strict_compatibility
debug
seam_correction
enable_preview
session
initial_state
latent_only
reference_assets
reference_audio_source
reference_audio_vae
driving_audio_source
driving_audio_vae
reference_video_source
timeline_video_source
guide_source
capture_refine_context
memory_attribution
prompt_conditioning_cache
reference_encode_cache
continuation_transport
max_new_physical_groups
_memory_attribution_collector
_diagnostic_continuation_policy
```
R4 thin adapterはこの名前・keyword-only形・defaultsを維持する必要がある。
## 9. R1 concrete plan (not implemented)
R1はProjectionだけに限定する。
1. 現在`v3/nodes.py`にある`_review_decode_chunk_range()`の判断を、torch/ComfyUI非依存のpure `ProjectionDecision`へ写す。
2. `full_accepted_prefix`と`current_review_unit(start,end)`だけを表現する。
3. 現在の`_apply_review_decode_scope()`のTensor/Assembly再構築をOutput Projectorの単一ownerへ移す。
4. Session、full Refine Context、Run Storage recordsは切り詰めず、表示用Video/Audio latentとAssemblyだけを同じrangeで投影する。
5. terminal merged unitは既存physical group境界に従い分割しない。
6. Full Run、Finish Remaining、complete、Use This Takeは現行どおりfull projectionを維持する。
7. focused parity、full CPU、frontend、manifest、workflow SHA/ZIP parity、public schemaをGateにする。
R1ではReview policy、prefix探索、Session/State priority、Sampling、commit/finalizeを変更しない。R1実装は明示承認までHOLD。
## 10. R0 disposition
R0 Characterizationの実装対象はtest/documentationだけで、Production runtimeは変更していない。
R1へ進む前の要確認事項:
1. V9の「invalid/incompatible Sessionは既存エラー」を、実コードの「advisory reject + fresh run」へ訂正するか。
2. `ValidatedPrefix.to_planning_facts()`を現行契約ではなくR2導入契約として扱うか。
この2点を未訂正のままR2/R4へ進むと、現行挙動維持とV9本文を同時に満たせない。
+41
View File
@@ -0,0 +1,41 @@
# R6 Node Facade Delta
## Purpose
R6 reduces only the public V3.8 Sampler method into this fixed boundary:
```text
public inputs
-> RuntimeRequest
-> existing hardening/runtime adapter
-> RuntimeOutput
-> public tuple
```
`v3/node_facade.py` owns the immutable request container and the V3.8
status-only resolution/diagnostic decoration. It does not import or create a
Coordinator, Planner, Run Storage controller, Sampling Engine, or ReviewUnit.
## Preserved ownership
- `v2/sequence.run_sequence` remains the R4 signature-compatible hardening
adapter and keeps its explicit 41-keyword signature.
- `InternalRuntimeCoordinator` remains the sole owner of continuation-source,
Session/State priority, prefix validation, and Runtime execution ordering.
- `execution_planner` remains the sole owner of physical-group and Projection
decisions.
- `run_storage` remains the sole owner of R5 immutable raw transactions and
manifest publication.
- The V3.8 node still resolves its existing Size Source contract before the
request boundary and calls the unchanged V3.7 runtime inheritance path once.
## Non-goals and compatibility
No public node ID, socket, widget order, output tuple, Workflow, Sampling,
Review, Run Storage schema, canonical selection, or hardening behavior is
changed. Tensor/model identities are preserved; only keyword containers are
copied into immutable request mappings. Duplicate runtime keywords fail
instead of being silently overridden, matching the prior explicit-keyword
call's fail-closed behavior.
This phase introduces no temporary adapter, new dependency, or future hook.
@@ -15,14 +15,13 @@
- README冒頭に「Web対応AIへこのREADMEを読ませる」案内を置く。ChatGPT/Gemini/Grokの現行公式情報に限定し、URLだけでrepository全文を読めるとは保証しない。GeminiのImport codeと、失敗時のREADME貼付/uploadを案内する。
- Size Source/Resolution/Manual Width・HeightはV3.8 Sampler本体に搭載されたため、通常workflowに外部MP/size nodeは不要と説明する。32×32は音声だけを聴く診断用であり、映像品質の推奨値にはしない。
- Issue #13はOpen、StandardにはProduction mitigationなし、R6-Aは一条件で改善したが最終4×8ではno-opだった、という証拠範囲を固定する。「解決済み」「全く改善方法がない」のどちらにも誇張しない。
- ユーザーが `http://127.0.0.6:8188/` で起動した `00058` ワークフローを使用した。ユーザー所有backendは停止しない。
- READMEの測定例は今回の4-step実測へ更新し、旧6-step値と混在させない。commit/pushは今後の明示依頼時のみ。
作成日: 2026-09-06
対象: `H3 Continuum Sampler V3.8`の現在のMain UI
再開時の正本: この文書と`PROJECT_STATE.md`
再開時の正本: この文書と公開README
## この文書を読めば撮影準備から再開できる
@@ -30,11 +29,9 @@
撮影開始の指示を受けた担当者は、最初に次を読みます。
1. `AGENTS.md`
2. `PROJECT_STATE.md`
3. この文書
4. `README_JA.md`の「10秒を5秒ずつ確認しながら作る」
5. `examples/workflows/MiniMax_H3_Continuum_V38.json`
1. この文書
2. `README_JA.md`の「10秒を5秒ずつ確認しながら作る」
3. `examples/workflows/MiniMax_H3_Continuum_V38x.json`
撮影開始前に、表示ラベル、標準Workflow、公開ノード数、Review/Take動作がこの台本と一致するか確認します。違いがある場合は、古い画面を撮影せず、先に台本を現在のUIへ合わせます。
+8 -7
View File
@@ -1,8 +1,8 @@
# V3.8 Release and Migration Policy
# V3.8X Release and Migration Policy
## Supported release
V3.8 is the current supported H3 Continuum product. Its package exports seven Node IDs:
V3.8X is the current supported H3 Continuum product. Its package version is `3.8.1` and it exports seven Node IDs:
```text
H3ContinuumSamplerV38
@@ -18,18 +18,19 @@ The assembler, loader, and Second Pass IDs are retained while their V3.8 display
## Saved workflows from older releases
Only the seven IDs listed above are exported by V3.8, including the retained Finalize, loader, and Second Pass IDs. Other public Node IDs from V3.7 and earlier are not exported. ComfyUI can therefore show an unknown node when a saved workflow refers to an ID outside this list. This is an intentional support boundary, not a request to replace the unknown node with a superficially similar V3.8 node.
Only the seven IDs listed above are exported by V3.8X, including the retained Finalize, loader, and Second Pass IDs. Other public Node IDs from V3.7 and earlier are not exported. ComfyUI can therefore show an unknown node when a saved workflow refers to an ID outside this list. This is an intentional support boundary, not a request to replace the unknown node with a superficially similar V3.8X node.
- Use tag `v3.7.0` for V3.7 workflows.
- Use tag `v3.6.0` for V3.6 workflows.
- Use tag `v3.8.0` for the prior V3.8.0 package and its supplied workflow.
- V3.4/V3.5 archives will be finalized during Release Preparation. Until then, use the matching historical commit or release asset already associated with that workflow.
Do not mix a historical workflow's private schema with the V3.8 package. Install the matching historical package, open and render the workflow there, or rebuild the graph explicitly with the V3.8 public nodes.
Do not mix a historical workflow's private schema with the V3.8X package. Install the matching historical package, open and render the workflow there, or rebuild the graph explicitly with the V3.8X public nodes.
## V3.8 workflow and external integration
## V3.8X workflow and external integration
The declared Registry payload and GitHub distribution use `examples/workflows/MiniMax_H3_Continuum_V38.json` and `examples/workflows/MiniMax_H3_Continuum_V38.zip`. The ZIP contains exactly the same JSON: one graph, not two variants. This is the user-supplied Spectrum workflow, not the former dependency-free Core template. It requires external Spectrum, rgthree, KJNodes, and ComfyUI-Easy-Use nodes, which Continuum does not bundle or install. Its saved default is the Spectrum path; users may switch the same graph to one task-matched LightX2V Turbo LoRA after disabling Spectrum, but all custom-node types remain in the graph.
The declared Registry payload and GitHub distribution use `examples/workflows/MiniMax_H3_Continuum_V38x.json` and `examples/workflows/MiniMax_H3_Continuum_V38x.zip`. The ZIP contains exactly the same JSON: one V3.8X graph, not two variants. This is the user-supplied Spectrum-capable workflow, not the former dependency-free Core template. It requires external Spectrum, rgthree, and KJNodes nodes, which Continuum does not bundle or install. ComfyUI-Easy-Use is no longer required. Spectrum and all Turbo LoRA entries are saved disabled; users may enable one task-matched path, but the external custom-node types remain in the graph.
The supplied JSON and ZIP are preserved byte-for-byte, including prompt, media filenames, custom titles, and settings. Select local files and disable unused inputs before rendering. A saved title such as `Save 3x5s Video` does not control duration; the Sampler settings do. The output path uses Core Video/Audio Decode, Finalize, Core Create Video, and Core Save Video (with the supplied Easy Use cleanup wrapper before Save). External latent processors and upscalers connect through H3 Continuum Second Pass; the old integrated Hi-Res Fix is not part of the V3.8 standard workflow. The supported processor, decoder, and accelerator boundaries are defined in [V3.8 Open Integration Contract](V38_OPEN_INTEGRATION_CONTRACT.md). Registry validate/pack and publication remain separate gates; a GitHub source commit does not claim they have run.
The supplied JSON and ZIP are preserved byte-for-byte, including prompt, media filenames, custom titles, and settings. Select local files and disable unused inputs before rendering. A saved title such as `Save 3x5s Video` does not control duration; the Sampler settings do. The output path uses Core Video/Audio Decode, Finalize, Core Create Video, and Core Save Video directly. External latent processors and upscalers connect through H3 Continuum Second Pass; the old integrated Hi-Res Fix is not part of the V3.8X standard workflow. The supported processor, decoder, and accelerator boundaries are defined in [V3.8 Open Integration Contract](V38_OPEN_INTEGRATION_CONTRACT.md). Registry validate/pack and publication remain separate gates; a GitHub source commit does not claim they have run.
Tests, runner/probe/diagnostic tools, internal development documents, Labs nodes, and historical workflows remain available in the GitHub source for development and audit purposes but are excluded from the Registry archive. The archive retains `tools/__init__.py` and `tools/p20_file_backed_tensor_poc.py`, which are runtime dependencies of the Production file-backed buffer path, plus `tools/verify_runtime.py` for verification. `MANIFEST.sha256` validates its declared source files; the staged archive instead carries `REGISTRY_MANIFEST.sha256`. These development assets are not part of the supported V3.8 searchable node surface.