Privacy-Period-Tracker/docs/qa/ClaudeReport.md

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 (what each pass reached) and 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 1 — 2026-08-18, partial (passes A and B; C, D and H partial)
• Last verified build SHA: adc5075
• Last tested device / environment: emulator PeriodQA, API 36, Pixel 6 profile, debug build
• Overall status: The Batch 01 foundation works end to end on a device — log a period, see a forecast with an honest window and confidence, edit it and watch the forecast move — and the first partial QA round found two defects that 70 passing unit tests could not: tapping the app's primary button twice crashed it, and two date APIs on the recalculation path would have crashed every device below Android 14. Both are fixed, with regression tests. That ratio is the honest summary of where this project stands: the logic is well covered and the product has barely been used, so the next round matters more than the last one. Nothing has been tested 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.