docs: add polish, stability & performance sprint plan

[shuv1337]

Comprehensive audit-driven plan covering 24 work items across 5 tracks:
stability (thread safety, resource cleanup), performance (latency, CPU),
polish (error handling, user feedback), security (input validation),
and code health (refactoring, lint rules, types).

https://claude.ai/code/session_014aF5Xm3tzbcYRkxrZasxCc

Greptile Summary

This PR adds SPRINT-POLISH-STABILITY-PERFORMANCE.md, a comprehensive audit-driven sprint plan covering 24 work items across stability, performance, polish, security, and code-health tracks. The document is well-structured with concrete problem statements, proposed fixes with code examples, a prioritized execution table, and a definition of done.

Confidence Score: 5/5

Documentation-only change; safe to merge.

No code is modified — this is a planning document. The single P2 finding is a redundant boolean condition in a proposed code snippet inside the doc, which is a cosmetic clarification with no production impact.

No files require special attention.

Important Files Changed

Filename	Overview
SPRINT-POLISH-STABILITY-PERFORMANCE.md	Adds a well-structured 24-item sprint plan across 5 tracks (stability, performance, polish, security, code health); one proposed code snippet in item 3.5 contains a redundant condition.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Audio chunk received]) --> B{Circuit state?}
    B -- CLOSED --> C[Send to ASR backend]
    C --> D{ASR success?}
    D -- Yes --> E[Reset failure counter]
    E --> B
    D -- No --> F[Increment failure counter]
    F --> G{counter >= MAX_FAILURES?}
    G -- No --> B
    G -- Yes --> H[Enter OPEN state\nNotify user via overlay/waybar]
    H --> I{Cooldown elapsed?}
    I -- No --> J[Drop audio chunk]
    J --> I
    I -- Yes --> K[Enter HALF-OPEN state]
    K --> L[Allow one inference attempt]
    L --> M{ASR success?}
    M -- Yes --> N[Reset counter\nEnter CLOSED state\nNotify user: recovered]
    N --> B
    M -- No --> H

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: SPRINT-POLISH-STABILITY-PERFORMANCE.md
Line: 207

Comment:
**Redundant condition in proposed fix**

The `== 0` guard in the suggested condition is redundant: when `_dropped_chunks` is `0`, `0 % 50 == 0` is already `True`, so the `== 0` branch never contributes an additional match. The simpler equivalent is:

```suggestion
**Fix**: Change to `if self._dropped_chunks % 50 == 0`.
```

Using the shorter form avoids confusion when the item is implemented.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "docs: add polish, stability & performanc..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Redundant condition in proposed fix

The == 0 guard in the suggested condition is redundant: when _dropped_chunks is 0, 0 % 50 == 0 is already True, so the == 0 branch never contributes an additional match. The simpler equivalent is:

Suggested change

	**Files**: `shuvoice/audio.py:133-138`
	**Fix**: Change to `if self._dropped_chunks % 50 == 0`.

Using the shorter form avoids confusion when the item is implemented.

Prompt To Fix With AI

This is a comment left during a code review.
Path: SPRINT-POLISH-STABILITY-PERFORMANCE.md
Line: 207

Comment:
**Redundant condition in proposed fix**

The `== 0` guard in the suggested condition is redundant: when `_dropped_chunks` is `0`, `0 % 50 == 0` is already `True`, so the `== 0` branch never contributes an additional match. The simpler equivalent is:

```suggestion
**Fix**: Change to `if self._dropped_chunks % 50 == 0`.
```

Using the shorter form avoids confusion when the item is implemented.

How can I resolve this? If you propose a fix, please make it concise.