62 lines
2.7 KiB
Markdown
62 lines
2.7 KiB
Markdown
# Claude QA Report — Period
|
|
|
|
```
|
|
Status: Current
|
|
Owner: _null
|
|
Last reviewed: 2026-08-18
|
|
Governs: the QA verdict — build SHAs, round summaries, the overall judgment
|
|
Review trigger: Any QA round run
|
|
```
|
|
|
|
> The QA verdict. Companion to [`ClaudeQACoverage.md`](ClaudeQACoverage.md)
|
|
> (what each pass reached) and [`ClaudeQAPlan.md`](ClaudeQAPlan.md) (the
|
|
> playbook).
|
|
>
|
|
> **Defects are issues, not entries here.** A defect found in a round is filed
|
|
> in the tracker with a severity label, where it can be assigned, closed by a
|
|
> commit, and counted. This file keeps the part a tracker is bad at: a judgment
|
|
> about whether the thing is fit to ship.
|
|
|
|
## Current run-state
|
|
|
|
- **Last QA round:** Round 2 — 2026-08-18, partial (A and B pass; C, D, E, G and H partial; F not applicable yet)
|
|
- **Last verified build SHA:** `19edf4c`
|
|
- **Last tested device / environment:** emulator `PeriodQA`, API 36, Pixel 6 profile, debug build
|
|
- **Overall status:** Three batches are done and the app is now a real product
|
|
you can use end to end: onboarding that ends in a forecast, a Today screen
|
|
whose six states each say something different and true, two-tap logging, a
|
|
calendar whose marks survive greyscale, and an Insights screen that mostly
|
|
declines to make claims it has not earned. The prediction engine is the one
|
|
§12 specifies and is measurably better than the prototype it replaced. What
|
|
the rounds keep showing is that this project's defects are found by opening
|
|
the app rather than by reading it — dark mode was broken for an entire batch
|
|
with 129 tests green, and the calendar's marks collided in a way only a
|
|
greyscale screenshot revealed. The gaps that matter now are the ones nothing
|
|
has touched: TalkBack has never been run, text has never been scaled up, and
|
|
nothing has run on a device at the minimum Android version this app claims to
|
|
support.
|
|
|
|
## Open defects
|
|
|
|
**Do not list them here, and do not read a defect count out of this file.** The
|
|
Command Center's docs report parses this document for open `P0` / `P1` / `P2`
|
|
counts, and under this convention they are always zero — the defects are in the
|
|
tracker, which is the whole point. The zeros here mean *this file does not hold
|
|
them*, never *there are none*.
|
|
|
|
Filed as issues in this repository's tracker, labelled by what they cost:
|
|
|
|
- **P0** — ships broken, or loses data
|
|
- **P1** — materially wrong, but shippable
|
|
- **P2** — cosmetic or low impact
|
|
- **release-blocker** — a release built today would be *wrong*, not merely
|
|
incomplete
|
|
|
|
Severity is what it costs, not how annoying it is to fix. Every defect needs the
|
|
build SHA it was found at — a finding that cannot be re-tested cannot be closed
|
|
— so put it in the issue body.
|
|
|
|
## Round notes
|
|
|
|
No rounds yet.
|