[D] P3 backlog: Incomplete or fragile logic #67
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Priority: P3 (grouped, split out when picked up)
record-play/ui/GroupWizard.tsx:72"TODO: Error handling" (file is dead per B-04).print()calls (calendar/service.py,games/router.py,integrations,discord_oauth.pyprints raw token-exchange response text on error) bypassloggingand can leak provider responses.PERF_AUDIT.md(indexes were partly addressed by migration V51). Re-triage and track as one issue.Dockerfileruns Python 3.11 while local dev artifacts are 3.14. Align them. The image has noHEALTHCHECK(compose defines one). The three build workflows are copy-paste, so use one parameterised workflow.Source:
AUDIT_FINDINGS.md(audit 2026-10-11).