allgpt-co/QuickVoice

Why: Release notes, changelog entries, version names, and known-limit sections can diverge during manual preparation. Scope: Add a Node script that accepts a candidate version. Confirm the changelog has the expected release heading before publish mode. Confirm the matching release-notes file exists and includes status, install requirements, known limitations, and verification. Provide a draft mode that passes while v0.1.0 remains explicitly unreleased. Acceptance criteria: Draft mode recognizes v0.1.0-draft.md without claiming a release exists. Publish mode fails if the changelog, filename, title, and candidate version disagree. Tests use temporary synthetic Markdown fixtures. The script does not create a tag, release, commit, or remote change. The release checklist documents the command. Effort: S Verification: node --test tests/<new-release-metadata-test>.test.mjs pnpm <new-release-check-command> -- v0.1.0 --draft Out of scope: Automatically publishing a release.

Why: The repository does not yet provide a Dev Container, so contributors need an optional, reproducible environment that is validated rather than implied. Scope: Add a minimal .devcontainer/devcontainer.json and any narrowly required supporting files. Base the environment on the documented Linux or WSL2 prerequisites without embedding credentials. Add a narrowly scoped workflow or test that parses and builds the configuration. Parse the resolved configuration with the Dev Container CLI. Verify Node, Python, Docker Compose, Corepack, pnpm, and Go Task versions in the built container. Do not start the full application or external provider integrations. Acceptance criteria: The container setup documents its supported host assumptions and resource requirements. The check runs only when Dev Container or setup files change, unless maintainers choose a scheduled run. Feature references resolve and the container builds on the selected CI architecture. Version output proves Node satisfi

Why: Setup docs list providers, but evaluators need one factual table showing which workflows can be inspected locally and which require their own accounts. Scope: Add docs/setup/provider-boundaries.md. Cover LiveKit, Twilio, Telnyx, speech/model providers, Pinecone, S3-compatible storage, Stripe, OAuth, and email. Ground every row in a tracked env template and current code path. State whether a local substitute exists, such as Mailpit for SMTP. Acceptance criteria: Every provider row cites a repository path. The table distinguishes service startup from successful provider-backed behavior. No row claims a partnership, certification, SLA, or included account. Examples use variable names only and never credential values. README setup boundaries link the matrix. Effort: M Verification: rg -n "LIVEKIT_|TWILIO_|TELNYX_|STRIPE_|PINECONE_|SMTP_|AWS_" \ .env.dev.example apps/server/.env.dev.example apps/ai/.env.dev.example Out of scope: Provider pricing comparisons or account setup

Why: macOS ships Bash 3.2 while QuickVoice orchestration uses Bash 4+ features. Scope: Add docs/setup/macos.md. Explain how #!/usr/bin/env bash resolves Bash from PATH. Document checks for modern Bash, Node, Corepack, Python, Docker Compose, and Go Task. Include Intel and Apple Silicon path notes only where verified. Acceptance criteria: A contributor can confirm which Bash the scripts will use. The guide avoids replacing /bin/bash or editing protected system files. Commands do not assume paid providers or production configuration. The root README links the guide. A maintainer records the macOS version used for verification in the PR. Effort: S Verification: command -v bash bash --version task doctor Out of scope: A native GUI installer or support for Bash 3.2.

Why: The README identifies WSL2 as the Windows path but does not yet provide a focused troubleshooting runbook. Scope: Add docs/setup/windows-wsl2.md. Cover Docker Desktop WSL integration, Linux-filesystem clone location, line endings, port conflicts, and checking Compose availability. Show only diagnostic commands that do not reveal environment values. Link the guide from the README and setup issue form if the issue-form schema supports the link cleanly. Acceptance criteria: The guide distinguishes WSL2 from native PowerShell. Commands are tested in an Ubuntu WSL2 shell. The guide explains when not to install a second Docker daemon. The guide includes a redaction warning before log-sharing instructions. All relative links pass the repository docs check, if available. Effort: S Verification: bash --version docker compose version task doctor Out of scope: Supporting native Windows orchestration or publishing Docker Desktop credentials.