Show verified H3 continuation capability and strategy in Video Gen
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, react
- Domain
- backend-api-design, full-stack
Research direction
Start with client/src/components/videoGen/AdvancedParamsPanel.jsx, then trace the model/capability projection and existing parameter helpers, queue/history details, and their tests. Read the blocker #13671 and inspect the socket update patterns before mapping the requested and effective strategy fields across client and server. Done means the acceptance criteria pass, including parity tests, persisted context and backend identity, and visible refusal for unverified capabilities.
Written by the indexing model from the issue text.
Description
Current evidence: AdvancedParamsPanel.jsx shows a Continuity picker only for runtimes in the client window-support mirror; history/queue surfaces cannot explain requested versus effective H3 temporal context.
Chosen fix: expose the server-derived runtime capability and explicit refusal reason in the model picker/advanced continuation control. Offer temporal context only when the pinned backend has verification evidence, retain an explicit last-frame choice, and show requested/effective strategy plus actual context length in queue/history. A stale or unverified capability must remain visibly unavailable rather than silently degrade. Reuse shared form/error and socket update patterns; add no polling.
Acceptance criteria:
- Rendered interaction covers verified temporal, explicit last-frame opt-out, and unavailable-pin refusal/disclosure.
- Queue/history details display persisted requested/effective strategy, actual context and backend identity; they never claim a history window for still-only output.
- Model switches do not accidentally submit a hidden stale temporal request; exact submitted options remain inspectable.
- Server/client parity tests agree on capability and no UI duration rule borrows LTX stride for H3.
Scope: client/src/components/videoGen/AdvancedParamsPanel.jsx, model/capability projection, queue/history details and existing parameter helpers/tests.
Dispatch: medium capability for routine coordinated UI/API integration; high effort for state transitions, backward compatibility and honest disclosure.
Blocked by #13671
Part of #13614
After shipping, check this slice in #13614. If this is its last open child, post a summary of all delivered children and close #13614; otherwise leave the epic open.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 32
- Avg merge
- 44m
- Merged PRs (30d)
- 990
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from atomantic/PortOS
-
area:media blocked cuda effort:high enhancement help wanted model:medium plan windows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
atomantic/PortOS#13683 · 1 comment ·
Maintainers usually reply within 1 day
-
apple-silicon area:media blocked effort:high enhancement help wanted macos model:heavy plan
Difficulty 5/5 Over a week Newbie friendliness 20/100
atomantic/PortOS#13682 · 1 comment ·
Maintainers usually reply within 1 day
-
area:media blocked cuda effort:medium help wanted model:medium plan windows
Difficulty 3/5 1-2 days Newbie friendliness 35/100
atomantic/PortOS#13681 · 1 comment ·
Maintainers usually reply within 1 day
-
apple-silicon area:media blocked effort:medium help wanted macos model:medium plan
Difficulty 4/5 3-5 days Newbie friendliness 28/100
atomantic/PortOS#13680 · 1 comment ·
Maintainers usually reply within 1 day
-
area:media blocked effort:xhigh model:heavy plan planner:gpt-6-1-sol
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in atomantic/PortOS
Similar issues
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
good first issue tests
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day