From 77093aaffe6a2ccac40c77c32fa3fd1061d6fb12 Mon Sep 17 00:00:00 2001 From: Qwynn Marcelle Date: Thu, 13 Aug 2026 01:17:03 -0400 Subject: [PATCH] =?UTF-8?q?docs(review):=20record=20the=20actual=20cause?= =?UTF-8?q?=20=E2=80=94=20the=20Greptile=20trial=20ran=20out=20(GTM-45)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The withdrawal record said "emission on this repository is not dependable." That was accurate about the symptom and wrong about the cause, and the difference decides what anyone does next: a flaky app is waited out, an exhausted trial is topped up. Established 2026-08-13. Greptile posts, in place of a review: `qmarcelle` has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan. and emits no check run. That is why the check fired on #10 and #13 and then stopped at #14 — the credits ran out in between, not the app's emission becoming unreliable here. The prediction that follows was confirmed the same day. `workspacejson/standard` kept working only until its own next pull request: #37 reviewed the exact head 4f9e8f6f and emitted zero check runs, against exactly one each on #34, #35 and #36. It hit the identical deadlock and its requirement was withdrawn the same way. So the "next door still works" observation in the original evidence was true but temporary, and reading it as repository-specific would have sent the investigation somewhere there was nothing to find. Restoring the signal is a billing action. --- docs/review/calibration-2026-08.md | 24 ++++++++++++++++++++++-- docs/review/merge-policy.md | 13 +++++++++++-- 2 files changed, 33 insertions(+), 4 deletions(-) diff --git a/docs/review/calibration-2026-08.md b/docs/review/calibration-2026-08.md index 2c220f7..7511e80 100644 --- a/docs/review/calibration-2026-08.md +++ b/docs/review/calibration-2026-08.md @@ -244,8 +244,28 @@ Observed on PR #14 across four heads: | `be2e965` (merged head) | — | **0** | 8/8 pass | 0 | The same `statusCheck: true` in `.greptile/config.json` kept producing the check on -`workspacejson/standard` across PRs #34, #35 and #36 throughout the same window. The -configuration is not missing; emission on this repository is not dependable. +`workspacejson/standard` across PRs #34, #35 and #36 throughout the same window, so +the configuration was never the problem. + +**Root cause, established 2026-08-13 — this is not repository-specific.** The +Greptile trial account reached its credit limit. In place of a review it posts: + +> `qmarcelle` has reached the 50-credit limit for trial accounts. To continue +> receiving code reviews, [upgrade your plan](https://app.greptile.com/review/github). + +and emits **no check run**. That is why the check fired on `integrations` #10 and +#13 and then stopped: the credits ran out between them and #14, not the app's +emission becoming unreliable on this repository. + +The prediction that follows was confirmed the same day. `workspacejson/standard` +kept working only until its own next pull request — on #37 Greptile reviewed the +exact head `4f9e8f6f` and emitted **zero** check runs, where #34, #35 and #36 each +produced exactly one. `standard` hit the identical deadlock and its requirement was +withdrawn the same way; see that repository's `docs/repository-settings.md`. + +An earlier revision of this section read "emission on this repository is not +dependable." That was accurate about the symptom and wrong about the cause, and the +difference matters: a flaky app is waited out, an exhausted trial is topped up. **What this says about the calibration.** The seven criteria were the right bar and were honestly observed — the defect was caught, the revert was clean, the check was diff --git a/docs/review/merge-policy.md b/docs/review/merge-policy.md index 9608d00..7dd4a2b 100644 --- a/docs/review/merge-policy.md +++ b/docs/review/merge-policy.md @@ -251,8 +251,17 @@ requirement could not survive. The same `statusCheck: true` in `.greptile/config.json` continued to produce the check on `workspacejson/standard` throughout, so this was not a missing config -value. The mechanism is real; its emission on this repository is not currently -dependable. +value. + +**The cause is the Greptile trial credit limit, not this repository.** Established +2026-08-13: the account has reached its 50-credit trial limit, after which Greptile +posts a credit-limit notice in place of a review and emits no check run. +`workspacejson/standard` kept working only until its own next pull request — #37 +reviewed head `4f9e8f6f` and emitted zero check runs, against exactly one each on +#34, #35 and #36 — and its requirement was withdrawn the same way. Details in +[`calibration-2026-08.md`](calibration-2026-08.md). + +Restoring the signal is therefore a billing action, not a debugging one. **Change applied 2026-08-13**, measured before and after against the API: