Files
resolutionflow/.ai/CURRENT_TASK.md
Michael Chihlas 1e3a6cfa01
All checks were successful
Mirror to GitHub / mirror (push) Successful in 12s
CI / frontend (pull_request) Successful in 5m43s
CI / backend (pull_request) Successful in 10m21s
CI / e2e (pull_request) Successful in 11m23s
fix(e2e): harden card selectors for session resume
Co-Authored-By: Codex <noreply@openai.com>
2026-04-25 16:42:33 -04:00

1.4 KiB

CURRENT_TASK.md

Task: Land consolidated CI-recovery PR #150 and lock reliable CI gates on main.

Status: in-progress

Definition of Done:

  • PR #150 (fix/ci-workflow-config) merged. CI / backend (pull_request), CI / frontend (pull_request), and CI / e2e (pull_request) show success before merge.
  • CI / backend (pull_request) added to required status checks on main in Gitea branch protection (frontend is already required).
  • Optional: CI / e2e (pull_request) confirmed clean across at least one PR run and added to required checks.

Assumptions:

  • The 8-core homelab Gitea Actions runner can support -n auto (8 xdist workers). If memory pressure shows up in CI, drop to -n 4.
  • pytest-cov's xdist support continues to handle the coverage merge and --cov-fail-under=50 check correctly.
  • The per-worker DB creation in conftest.py is idempotent and racing workers on first import won't all try to CREATE DATABASE simultaneously — postgres serializes that, but if it surfaces issues, wrap with an advisory lock.

Out of scope:

  • Frontend lint warnings (23 remain after #149).
  • The 23 react-hooks/exhaustive-deps warnings.
  • RLS test suite (gated behind RUN_RLS_TESTS=1; not in default CI).
  • Per-test transactional rollback (would shave another 30-40% off backend time but is a much bigger refactor — capture in TODO if interested).