[Juliusolsson05]

Summary

Removes orchestration context inheritance from the active MCP behavior because the cloned/resumed transcript path is too unstable for child-agent work.

Children now start from clean provider conversations. The parent agent must include required context directly in the prompt. The old inheritParentContext schema field is still tolerated for stale MCP tool caches, but the implementation forces it off.

Refs #259 for bringing context inheritance back with a more stable design.

Changes

• Stop advertising inherited parent transcripts as the default orchestration behavior.
• Force inheritParentContext: false through the MCP/main/renderer creation path.
• Comment out the renderer clone/translate resume implementation with the reason it is disabled.
• Update the orchestration bootstrap prompt to explicitly tell children they start clean.
• Update the focused orchestration MCP test expectations.

Verification

• npm run test:orchestration-mcp -- --runInBand
• npm run build:app

Note: npx tsc --noEmit -p tsconfig.web.json is not usable directly in this checkout because the repo expects referenced .tsc-out/node declaration outputs to exist first; it fails with TS6305 before checking this change.