R19 — status_check.yml's API-37 comment is falsified by the branch and is not on the branch's correction list #28

Closed
opened 2026-08-23 03:44:49 +00:00 by JMR-dev · 0 comments
JMR-dev commented 2026-08-23 03:44:49 +00:00 (Migrated from github.com)

Finding R19 from the overnight max-effort review (Fable lead, Opus sub-agents). Full report: scratchpad/overnight/REVIEW.md.

R19 — status_check.yml's API-37 comment is falsified by the branch and is not on the branch's correction list

severity: medium
verdict: CONFIRMED
where: .github/workflows/status_check.yml:207-213
scenario: The comment is the first thing read when asking "why no API 37 row": "every test fails there no matter what this app does" (branch measures 47/49 passing under swangle_indirect) and "the row needs api-level 37.0" (37.1 exists, same abort). The branch's correction-owed list covers CLAUDE.md only.
evidence: Comment read; branch :226-227 and :166-173 read.
fix: Add the workflow comment to the branch's correction list, or update it in the branch. Decide whether the docs-only branch should touch a workflow file (a follow-up listing is enough if not).
risk: Widening a docs branch into workflows; listing as follow-up avoids it.


Cut: below — held for manual review: product decision, CI/workflow, hardware, or PLAUSIBLE verdict.

🤖 Generated with Claude Code

_Finding **R19** from the overnight max-effort review (Fable lead, Opus sub-agents). Full report: `scratchpad/overnight/REVIEW.md`._ ### R19 — status_check.yml's API-37 comment is falsified by the branch and is not on the branch's correction list severity: medium verdict: CONFIRMED where: .github/workflows/status_check.yml:207-213 scenario: The comment is the first thing read when asking "why no API 37 row": "every test fails there no matter what this app does" (branch measures 47/49 passing under swangle_indirect) and "the row needs api-level 37.0" (37.1 exists, same abort). The branch's correction-owed list covers CLAUDE.md only. evidence: Comment read; branch :226-227 and :166-173 read. fix: Add the workflow comment to the branch's correction list, or update it in the branch. Decide whether the docs-only branch should touch a workflow file (a follow-up listing is enough if not). risk: Widening a docs branch into workflows; listing as follow-up avoids it. --- **Cut:** `below` — held for manual review: product decision, CI/workflow, hardware, or PLAUSIBLE verdict. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: JMR-dev/LibreMediaConverter#28