Letting a research run outlast its browser sessions

Close the session, not the whole run#

A research run can need another observation from a source after its current browser session finishes. The original transition table made COMPLETED permanent for that source's checkpoint, leaving an active run with no valid next state.

The change keeps the completed revision closed and appends a new session to the same run and source. Research MCP Service resolves the saved brief and predecessor; the domain validator then checks the transition. The next session must advance its sequence and use fresh query and result fingerprints. Duplicate checkpoint identities, reused session details and writes to a finished run are rejected.

Resume the search that was actually paused#

An access pause needs a different kind of continuation. Replacing a missing tab should restore the same research position, so recovery preserves the query, filters, sort order, position, counts, fingerprints, limits and expiry. Fresh access information, human confirmation and revision details are the permitted changes.

The checkpoint stores research state, not a browser session. It carries no cookies or browser profiles, doesn't bypass an access check, and can't extend an expired pause. That lets a replacement tab continue the recorded work without treating lost browser state as permission to start something else.

Check the two paths independently#

Unit tests cover fresh sessions, repeated sequences and fingerprints, finished runs, changed recovery checkpoints and expired pauses. An integration test follows a completed checkpoint accepting new work while its parent run remains open. Together the definitions distinguish legitimate continuation from replaying old work or changing a paused search; they were inspected, not rerun for this note.