2.6 KiB
2.6 KiB
HANDOFF.md
Last updated: 2026-05-01 (session 7 — backlog/Gitea issue validity audit)
Active task: None. Pick next from .ai/TODO.md or roadmap.
Just-reviewed: .ai/TODO.md, inline code TODOs, and open Gitea issues were checked against current main.
Where this session ended
Review-only audit completed; no source code changes were needed. Key findings:
.ai/TODO.md: pytest-xdist item is stale/resolved; lint cleanup is still valid but now 24 warnings, not 23; selector hardening, ResourceWarning filter audit, transactional rollback, testmon,currentChatRefobservability, peer-tech escalation, and Escalation Mode mobile follow-up are still valid.- Gitea open issues: #58, #60, #128, #129, #130 are still valid. #66 is partially resolved by
.rfflowexport/import; only template packs/marketplace remain. #127 is mostly resolved by assistant empty-state copy plus prompt boundaries; close or rewrite if an always-visible badge is still desired. - Open Gitea PR #124 (
feat/cockpit-harness) is stale/unmergeable against currentmainand overlaps/supersedes newer/pilotwork. - Inline TODOs still valid: post-session feedback prompt, FlowPilot analytics domain/time-entry TODOs, prompt-cache verification note unless live
anthropic.cacheevidence is confirmed,ProposalDetailmodify-on-editor-save, and procedural ghost-step accept/dismiss handlers.
Resume point — DO THIS NEXT
Pick a still-valid task from the audit above. Highest cleanup leverage: remove/update stale TODO/Gitea items before implementing new work, especially .ai/TODO.md xdist and Gitea #66/#127.
Environment notes (carry-forward)
- This code-server LXC has bun + docker but no native
python/node/npm. Usedocker exec resolutionflow_{backend,frontend} …for all build/test commands. Documented in.ai/PROJECT_CONTEXT.md. - Headless Chromium (used by
/qa/browse) needsCONTAINER=1in the env that launches the browse server, otherwise it aborts atsandbox/linux/services/credentials.ccdue to the LXC namespace constraint. The browse server is currently running with that env set; restarting it manually requiresCONTAINER=1 $B statusagain. - Code-server's
/etc/hostshas100.64.78.44 docker-01so the headless browser can resolve the bake-inVITE_API_URL. Persistent — no need to re-add unless the container is rebuilt. - Multi-head alembic state on
main(heads070,c0f3a4b7e91d,024) is pre-existing. Usealembic upgrade heads(plural) ifheadcomplains.