Parent/specification: #2083
Repository: Capsize-Games/airunner. Work type: Operator acceptance; a small-model session prepares scenarios, not fabricated results.
Outcome
On the approved 16 GB and higher-VRAM NVIDIA matrix switch art/chat/STT/TTS/embedding workloads, schedule memory jobs, cancel, idle-unload and recover from OOM without lost user state or orphan processes. This is an operator/manual acceptance issue. An ordinary small-model agent prepares the script/results template only; real GUI/model work requires the operator to run it.
Prerequisites
Read/change boundary
release-planning/linux-v1/feature-matrix.mdrelease-planning/linux-v1/acceptance/ (new)
Paths marked new are deliverables. The companion/ module is introduced by B01; release evidence files may be introduced by prerequisite issues. Directory entries identify a subsystem, not permission to refactor it. Normally limit implementation to five production files plus directly relevant tests; if more is needed, return a proposed split with exact files and do not omit requirements.
Acceptance
Validation
Deliver the named document/results artifact with a checklist, source references, reviewer/operator fields and explicit pending results. No new app tests needed just to mirror prose. The issue remains open until its specified acceptance evidence/review exists. Never claim manual, legal or safety efficacy checks passed from static analysis.
Guardrails / handoff
Linux + NVIDIA 16 GB minimum; retain Qt and offline core; no Electron/Windows work. Preserve existing features and user data. Do not co-install the two airunner_services implementations. No private policy vocabulary, credentials, customer content or sensitive test imagery in source, issues or logs. No GUI/model launch, paid API call, live DB change or deployment in an ordinary coding session. Read applicable repository instructions; preserve unrelated edits. One issue per session; no subagents, automatic follow-on issues or model escalation. Return behavior change, files, exact checks/results and unresolved facts. Do not close until required review/acceptance is complete.
Parent/specification: #2083
Repository: Capsize-Games/airunner. Work type: Operator acceptance; a small-model session prepares scenarios, not fabricated results.
Outcome
On the approved 16 GB and higher-VRAM NVIDIA matrix switch art/chat/STT/TTS/embedding workloads, schedule memory jobs, cancel, idle-unload and recover from OOM without lost user state or orphan processes. This is an operator/manual acceptance issue. An ordinary small-model agent prepares the script/results template only; real GUI/model work requires the operator to run it.
Prerequisites
Read/change boundary
release-planning/linux-v1/feature-matrix.mdrelease-planning/linux-v1/acceptance/ (new)Paths marked new are deliverables. The
companion/module is introduced by B01; release evidence files may be introduced by prerequisite issues. Directory entries identify a subsystem, not permission to refactor it. Normally limit implementation to five production files plus directly relevant tests; if more is needed, return a proposed split with exact files and do not omit requirements.Acceptance
Validation
Deliver the named document/results artifact with a checklist, source references, reviewer/operator fields and explicit pending results. No new app tests needed just to mirror prose. The issue remains open until its specified acceptance evidence/review exists. Never claim manual, legal or safety efficacy checks passed from static analysis.
Guardrails / handoff
Linux + NVIDIA 16 GB minimum; retain Qt and offline core; no Electron/Windows work. Preserve existing features and user data. Do not co-install the two
airunner_servicesimplementations. No private policy vocabulary, credentials, customer content or sensitive test imagery in source, issues or logs. No GUI/model launch, paid API call, live DB change or deployment in an ordinary coding session. Read applicable repository instructions; preserve unrelated edits. One issue per session; no subagents, automatic follow-on issues or model escalation. Return behavior change, files, exact checks/results and unresolved facts. Do not close until required review/acceptance is complete.