null
/
Privacy-Period-Tracker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Privacy-Period-Tracker/docs/qa/ClaudeReport.md

2.2 KiB
Raw Blame History

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: None — no round has been run
  • Last verified build SHA: none
  • Last tested device / environment: none
  • Overall status: No QA round has been run, because there is nothing to run one against yet — this repository currently holds the product specification, the documentation tree and a Kotlin project skeleton, and the first buildable version of the app is what Batch 01 produces. The two things that will decide whether this product is trustworthy are already known and already testable in principle: whether the forecast stays personal for a user whose cycle is not 28 days, and whether the lock screen keeps quiet in Discreet mode. Neither has been measured.

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.