Files

Michael Chihlas 5bee264d70 fix(suggested-fix-pending): apply PR #156 review fixes

- Page-level Resolve patches applied_pending → applied_success before
  opening the resolution flow, so resolved sessions don't carry a
  provisional pending fix.
- Page-level Escalate intercept now catches applied_pending in addition
  to verifying/partial; intercept copy generalized from "Verifying state"
  to "still needs an outcome."
- PendingBanner gains a Dismiss action, matching the PR body and the
  backend's allowed pending → dismissed transition.
- resolution_note_generator and escalation_package_generator system
  prompts no longer include real-looking pending examples (anti-parrot
  guardrail compliance).

Verified via Docker: prompt anti-parrot 2/2, suggested-fix outcome suite
21/21, frontend tsc -b clean, npm run build clean.

Co-Authored-By: Codex <noreply@openai.com>

2026-04-30 23:02:46 -04:00

CURRENT_TASK.md

fix(suggested-fix-pending): apply PR #156 review fixes

2026-04-30 23:02:46 -04:00

DECISIONS.md

docs(ai): refresh handoff for PR #156 — pending-verification feature

2026-04-30 17:37:08 -04:00

HANDOFF.md

fix(suggested-fix-pending): apply PR #156 review fixes

2026-04-30 23:02:46 -04:00

PROJECT_CONTEXT.md

fix(ai): correct stale role-hierarchy and file-listing claims

2026-04-24 15:09:22 -04:00

README.md

chore(ai): migrate to dual-agent handoff system

2026-04-24 14:50:41 -04:00

SESSION_LOG.md

fix(suggested-fix-pending): apply PR #156 review fixes

2026-04-30 23:02:46 -04:00

TODO.md

fix(handoff): bound escalation assessment latency

2026-04-27 20:03:14 -04:00

README.md

.ai/ — dual-agent handoff system

ResolutionFlow uses two coding agents: Claude Code (primary) and OpenAI Codex (resume when Claude hits session or weekly limits). This directory holds the shared state that lets either agent start a session with full context.

Files

File	Holds	Written when	Read when
PROJECT_CONTEXT.md	Stable repo truth: stack, structure, SaaS shape, ConnectWise, coding standards, frontend patterns, critical lessons	Only when the repo's shape changes	Every session start
CURRENT_TASK.md	The single active task: goal, DoD, assumptions, out-of-scope	On task start; status updates during work	Every session start
HANDOFF.md	Exact resume point: branch, where you left off, next steps, blockers	On session end / context-window limit	Every session start (most important)
TODO.md	Backlog of work NOT currently active	When deferring or queueing work	Only when `CURRENT_TASK.md` is `complete`
DECISIONS.md	Append-only architectural decision log	When an architectural choice is made	Skim top entries each session
SESSION_LOG.md	Append-only chronological history	On session end	Only when broader context is needed

Agent-specific tooling lives at the repo root:

../CLAUDE.md — Claude Code's tooling (GitNexus, gstack slash commands, Claude trailer)
../AGENTS.md — OpenAI Codex's tooling (grep/rg fallbacks, Codex trailer)

Both root files contain an identical shared-protocol block. If you edit one, edit the other.

The handoff ritual

At session end (limit hit, task complete, or user stop): update HANDOFF.md to reflect the new resume point, update CURRENT_TASK.md status if it changed, append to DECISIONS.md if you made an architectural call, append a session entry to SESSION_LOG.md, and WIP-commit any dirty working tree with wip(handoff): <one-line> unless told otherwise. Don't push.

How to invoke a resume

Tell the agent:

Read CLAUDE.md (or AGENTS.md) and follow its instructions.

The agent will read its root file, which directs it to .ai/PROJECT_CONTEXT.md, .ai/CURRENT_TASK.md, and .ai/HANDOFF.md before doing anything else.

Recovery

The previous monolithic CLAUDE.md is recoverable via:

git show pre-ai-handoff:CLAUDE.md

(Tag pre-ai-handoff on commit e110fed — the snapshot taken before this migration.)