You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
#1199 stage 11: ltx2/chained-segments holds the look by default #1212
Stage of #1199, filed by model claude-opus-5-5 via provider anthropic. Already
built on feat/long-form-media (merged 3f8ed222). The authoritative spec is the
plan (docs/superpowers/plans/2026-11-03-long-form-media.md, task named below) and
the design record. If they differ, the design record says what shipped.
Built: a look_hold variable on templates/ltx2/chained-segments, default true,
wired to chain.look_hold (c8fe45b). The chain is otherwise unchanged: last_frame,
3 segments of 121 frames. The ltx-2.5 and long-form skills cap an LTX long take at
about 15-20 s.
Observe over MCP:
run_workflowtemplates/ltx2/chained-segments with defaults, and with look_hold: false.
get_job_workflow shows the chain block.
Acceptance intent:
The default realizes look_hold: true.
look_hold: false is the plain chain.
The wall time is about the same warm.
Bench evidence: S5 look_hold and the orbit arms 9331cd20fa39, 64641b316eed
(mini-ai:8766). Record: bench/records/ltx.md.
Breaking change: the default output of ltx2/chained-segments changes, though no
difference is visible by eye.
Verified on the mini-ai server (mps on mini-ai.lan, develop @ cac31945) by claude-opus-5-5 via anthropic.
Note on acceptance cases: the hand-off says "run every pending: #1212 case", but no suite file has one, and git log -S 1212 shows none was ever written. I tested against the issue's own acceptance intent instead.
What I ran:
get_workflow templates/ltx2/chained-segments variables_only=true: the variables include look_hold: true.
validate_workflow + run_workflow templates/ltx2/chained-segments {seed:1212} (job f26ff33457c4) succeeded. get_job_workflow is realized: variables.look_hold: true. The chain block reads continuity: last_frame, segments: variable:segments (3), trim_frames 2, crossfade_ms 80, look_hold: variable:look_hold, with num_frames 121. The description documents the default and says "pass false for the plain chain". It also states the 15-20 s cap.
run_workflow ... {seed:1212, look_hold:false} (job 7b07954b1934) succeeded with the same shots layout (121/119/119 frames, 359 total).
compare_outputs with the false run as baseline, at 2.0 s / 5.2 s / 10.2 s:
frame 48 (segment 1) is identical.
frames 125 and 245 (segments 2 and 3) differ: PSNR min 35.4 dB, SSIM min 0.944, mean abs diff up to 2.9. By eye there is no visible difference. So the default really applies look_hold to the later segments only, and false turns it off.
Wall time: per-pass 21.9 s (default) vs 21.8 s (false). Denoise took 528 s vs 521 s and decode 40.8 s vs 40.5 s. The default run was cold (load 30.8 s), and the false run was warm on the cached model. So the cost is about the same.
Adjacent case: validate_workflow with look_hold: "maybe" is refused at arguments.look_hold ("Cannot interpret 'maybe' as true/false").
All three acceptance points hold. Closing as verified on mps; CUDA has not seen this.
No suite case added: each arm is about 10 minutes on mps, and the stage was supposed to come with pending: cases that never got written. A spec gap for the lead to note if wanted.
Activity
dkackman commentedon Nov 7, 2026
Verified on the mini-ai server (mps on mini-ai.lan,
develop @ cac31945) byclaude-opus-5-5viaanthropic.Note on acceptance cases: the hand-off says "run every
pending: #1212case", but no suite file has one, andgit log -S 1212shows none was ever written. I tested against the issue's own acceptance intent instead.What I ran:
get_workflow templates/ltx2/chained-segments variables_only=true: the variables includelook_hold: true.validate_workflow+run_workflow templates/ltx2/chained-segments {seed:1212}(jobf26ff33457c4) succeeded.get_job_workflowis realized:variables.look_hold: true. The chain block readscontinuity: last_frame, segments: variable:segments (3), trim_frames 2, crossfade_ms 80, look_hold: variable:look_hold, withnum_frames121. The description documents the default and says "pass false for the plain chain". It also states the 15-20 s cap.run_workflow ... {seed:1212, look_hold:false}(job7b07954b1934) succeeded with the same shots layout (121/119/119 frames, 359 total).compare_outputswith the false run as baseline, at 2.0 s / 5.2 s / 10.2 s:falseturns it off.validate_workflowwithlook_hold: "maybe"is refused atarguments.look_hold("Cannot interpret 'maybe' as true/false").All three acceptance points hold. Closing as verified on mps; CUDA has not seen this.
No suite case added: each arm is about 10 minutes on mps, and the stage was supposed to come with
pending:cases that never got written. A spec gap for the lead to note if wanted.