Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.
PR #65 Greptile review · 30 September 2026
Source: PR #65, reviewed head c19957a. Greptile raised five actionable findings. Fix commit 34d222c addresses them. Its re-review found one additional fallback issue, addressed by commit 8da572a. The review at c22665c found no remaining functional finding and raised one documentation reference issue, corrected before merge.
| Finding | Severity | Mitigation and focused evidence |
|---|
| Saved PR/review/audit snapshots can overwrite newer live data | P1 | Live data takes precedence over an in-flight saved fetch; a Node regression checks the race and saved fallback. |
| Brace-style Git renames corrupt heatmap module names | P1 | Destination paths are extracted from brace-style and full-path renames; a red/green test checks both and module aggregation. |
| Review table loses selected sort after refresh | P2 | Reapply the table's selected sort after replacing review rows; the Node regression checks it. |
| Reviews submitted after merge disappear from activity counts | P2 | Count all non-author review activity, while average turns to merge uses only pre-merge reviews; a red/green test checks the distinction. |
| A shared commit can duplicate Greptile check totals across PRs | P2 | Honor each check run's linked PR numbers and count a check-run ID only once; a red/green test covers two PRs sharing a commit. |
| Live-data precedence prevents a newer published fallback after a later refresh fails | P1 | Explicit fallback reloads may apply strictly newer snapshots; startup loads and older/equal/undated snapshots remain guarded. The Node regression checks all three views for these cases. |
| An audit reference used an issue number without its linked title | P2 | Link the existing architecture assessment task by its tracker title. |
At the fix commit, 25 focused Python tests, the dashboard race/sort Node regression, BFF/web type checks, and a headless browser smoke passed. The browser rendered 10 PRs, 8 merged, 39 review comments, 17 review turns, the Audits tab, and long-chart scrolling, then closed Chrome. The merge gate requires passing CI and disposition of all bot findings; the current gate status is available on the linked PR.