summaryrefslogtreecommitdiff
path: root/CLAUDE.md
diff options
context:
space:
mode:
Diffstat (limited to 'CLAUDE.md')
-rw-r--r--CLAUDE.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/CLAUDE.md b/CLAUDE.md
index 4faa0f4..b5e4e5e 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -54,6 +54,7 @@ with `adb shell monkey`. Use the shared wrappers, which report from exit codes,
and a logcat capture started before launch:
```
+/workspace/devtools/bin/go-verify /workspace/listen/server
/workspace/devtools/bin/gradle-test /workspace/listen -- --rerun-tasks
/workspace/devtools/bin/gradle-report /workspace/listen detekt
/workspace/devtools/bin/android-launch-check org.terst.listen \
@@ -83,6 +84,16 @@ claims three separate times across these repos.
## Quality gate — every commit
+0. **Server** — `/workspace/devtools/bin/go-verify server` passes: gofmt clean, builds, vets,
+ and every test runs. First because it is the fast one, ten seconds against several minutes.
+
+ It had no gate at all until 2026-10-31. Twenty-five server commits went in on somebody
+ remembering to type `go test` and reading the output — the exact habit the Gradle wrappers
+ exist to replace, in the half of the repo nobody had wrapped. `go-verify` reports from exit
+ codes and parsed `go test -json`, and catches the two failures that look like success in a
+ terminal: a package whose tests fail to compile (the count silently drops) and a run where
+ nothing executed at all.
+
1. **Build** — `./gradlew compileDebugKotlin` succeeds.
2. **Tests** — `./gradlew testDebugUnitTest` passes in full.
3. **Static analysis** — `./gradlew detekt lintDebug` clean: zero lint errors, zero new detekt