All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Soundlab Dialogue Cleanup Layered Transitions Design BlueprintUse when a solution needs a coherent structure before implementation or production for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preser...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means the failure is bounded by observations, one testable hypothesis, and a safe next ste...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means the proposed change is compared with a baseline, regression risk is ...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Sound design and sound effects: dialogue cleanup for layered transitions. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permiss...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use perm...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline,...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means the review names relevant hazards, permissions, controls, evidence gaps, and...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, ch...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Layered Transitions Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Sound design and sound effects: dialogue cleanup for layered transitions. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Capture source, license, owner, tags, technical metadata, and edit history for each library item. Success means each critical requirement maps to a reproducible check and a truthful pass, fai...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permissioned inpu...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Design BlueprintUse when a solution needs a coherent structure before implementation or production for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a base...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use pe...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means the proposed change is compared with a baseline, regression risk is visible, ...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Sound design and sound effects: dialogue cleanup for loudness targets. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permissioned inp...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned ...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline, check cu...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means the review names relevant hazards, permissions, controls, evidence gaps, and approval...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, check curre...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Loudness Targets Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Sound design and sound effects: dialogue cleanup for loudness targets. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Measure integrated/peak levels and note the exact delivery requirement and metering method. Success means each critical requirement maps to a reproducible check and a truthful pass, fail, or unk...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permiss...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Design BlueprintUse when a solution needs a coherent structure before implementation or production for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, prese...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means the failure is bounded by observations, one testable hypothesis, and a safe next st...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means the proposed change is compared with a baseline, regression risk is...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permis...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use per...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means the review names relevant hazards, permissions, controls, evidence gaps, an...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, c...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Multichannel Delivery Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Sound design and sound effects: dialogue cleanup for multichannel delivery. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Verify channel order, sample rate, bit depth, downmix, and playback on the target delivery path. Success means each critical requirement maps to a reproducible check and a truthful pass, fa...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Sound design and sound effects: dialogue cleanup for product interactions. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means the prepared result is reproducible, reviewable, and within the approv...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Design BlueprintUse when a solution needs a coherent structure before implementation or production for Sound design and sound effects: dialogue cleanup for product interactions. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permi...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Sound design and sound effects: dialogue cleanup for product interactions. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means the failure is bounded by observations, one testable hypothesi...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Sound design and sound effects: dialogue cleanup for product interactions. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means the proposed change is compared with a baselin...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Sound design and sound effects: dialogue cleanup for product interactions. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means options are compared on user-approved criteria with uncertainty and trade-o...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Sound design and sound effects: dialogue cleanup for product interactions. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means requirements have priorities, evidence, owners, and measurable acceptanc...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Sound design and sound effects: dialogue cleanup for product interactions. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Sound design and sound effects: dialogue cleanup for product interactions. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means the review names relevant hazards, permissions, contro...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Sound design and sound effects: dialogue cleanup for product interactions. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, p...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Product Interactions Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Sound design and sound effects: dialogue cleanup for product interactions. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Test ambient-loop boundaries for clicks, level changes, stereo shifts, and plausible variation over repeated playback. Success means each critical requirement maps to a reproducible check an...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means the prepared result is reproducible, reviewable, and within the approved sc...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Design BlueprintUse when a solution needs a coherent structure before implementation or production for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permission...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means the failure is bounded by observations, one testable hypothesis, an...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means the proposed change is compared with a baseline, re...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means options are compared on user-approved criteria with uncertainty and trade-offs s...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means requirements have priorities, evidence, owners, and measurable acceptance con...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, pre...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means the review names relevant hazards, permissions, controls, e...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preser...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Rights And Provenance Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Sound design and sound effects: dialogue cleanup for rights and provenance. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Retain consent and license evidence for field recordings, samples, voices, and synthetic or transformed sources. Success means each critical requirement maps to a reproducible check and a t...Votes: 0GitHub stars: 2
- Soundlab Dialogue Cleanup Room Scale Realism Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Sound design and sound effects: dialogue cleanup for room-scale realism. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Compare dialogue intelligibility before and after processing using an approved reference and a listening check. Success means the prepared result is reproducible, reviewable, and within the approved scope....Votes: 0GitHub stars: 2