Epic (eve track): session adoption, Drop in, Resume and Adopt on the agents board #596

Eve track of barelyworkingcode/relay#525. The story, the cross-repo contract and the merge order live there. This parent holds eve's batch list.

User story

As the owner, I want Drop in, Resume and Adopt on the agents board, so that I can take over any session from my phone.

Acceptance criteria

• A headless idle session shows Drop in; a working one shows Take over after this turn (eve#592).
• An ended outside session in a registered project shows Resume (eve#593).
• An idle live outside session in a registered project shows Adopt (eve#597).
• All three share one row-action model and one refusal-reason line.

What I'd notice

One set of buttons on the board. The one that applies is the one I see.

Children

• eve#592: Drop in from an idle headless session (existing)
• eve#593: Resume an ended outside session in a terminal (existing)
• eve#597: Adopt an idle outside session
• eve#598: close child (eve)

Notes

eve#592 and eve#593 were filed as standalone stories. Under this epic their PRs target epic/596-session-adoption, and the planner amends their contracts for that. eve#593 needs barelyworkingcode/relay#524.

Contract

Eve's file ownership per child is in the child. The relay pin moves in its own PR before each child that needs a new relay door. See the owning parent for the merge order and the joint close task.