docs-quickstart-installer-path

Evidence & signatures

Verified by exact grep against `~/README.md` (final state, line numbers from `cat -n`):

| AC | Check | Result |
|----|-------|--------|
| 1 | Step 3 runs `bash install.sh` | `17: bash install.sh` ✓ |
| 2 | `bash deploy.sh` absent from Quick Start step code blocks | 0 matches in lines 5–27 ✓ |
| 3 | `deploy.sh` appears only in the distinguishing note | lines 24, 27 (blockquote) ✓ |
| 4 | `install.sh` described as the fresh-host installer | `19: 'install.sh' is the fresh-host installer. It installs system dependencies (via apt)...` ✓ |
| 5 | Script roles match docs — `deploy.sh` uses `scp` (3 hits), `install.sh` installs/`systemctl enable --now` (2 hits) | ✓ |
| 6 | Markdown well-formed: 6 code fences (balanced), `deploy.sh` mention is `>`-quoted | ✓ |

Edge cases tested: (a) an existing `deploy.sh`-only installation flow would now correctly stop at step 2 → the note explicitly routes users to `install.sh` first; (b) grep for `bash deploy.sh` in the Quick Start section returns 0, so no stale invocation remains; (c) blockquote formatting verified so the note renders as a callout, not a step; (d) fence balance confirmed so the step-3 code block doesn't swallow the description text. `bash -n deploy.sh && bash -n install.sh` both pass, and both scripts keep their exact original behavior.

{"model": "deepseek-v4-flash", "problem_class": "docs-quickstart-installer-path", "result": "passed", "tests": 6}