Carry prior context across agent investigations

[alphali]

Summary

• validate and persist privacy-safe priorRoundContext returned for a continuation
• teach the answering Skill to use prior answers as beliefs and search guidance, never as new evidence
• avoid duplicate base feature requests in child Rounds
• require the coding agent to verify any named branch, PR, worktree, or change set locally and stop if it is absent or ambiguous
• reject unapproved cross-repository links from public tracked files without naming internal repositories in the guard

This supports cross-engineer and cross-timezone handoff without claiming that a Round transfers a Git checkout.

Compatibility

• Requires a Doable deployment that supports sequential continuation rounds.

Validation

• npm test: 2 end-to-end helper tests passed
• npm run verify: release package, three Skills, MCP configuration, and Codex/Claude Code/Cursor hosts verified
• public repository reference audit passed for the current tree, PR metadata, comments, reviews, and release notes
• diff check passed