Preserve native Claude orchestration boundaries

[ItayCohen-Prog]

What changed

• remove adapter-authored Workflow retry and evidence-gate policy from the default system preamble
• keep the remaining preamble identity-only so Claude Code owns tools, agents, Workflows, retries, reviews, and completion
• add an inert child-only GPTCODE_ACTIVE=1 marker that downstream launchers can use to prevent provider-state leakage
• reserve the marker against ambient or configured overrides and document the isolation contract

Root cause

gptCode had accumulated behavioral Workflow guidance in its provider preamble, and a Tessera process launched from a gptCode session could inherit the isolated provider environment before starting what looked like regular Claude Code.

Impact

gptCode returns to the native-first product boundary: GPT supplies reasoning through Codex OAuth, while Claude Code remains the unmodified orchestration shell. The marker is inert and changes no prompt, model, tool, workflow, auth, or retry behavior by itself.

Validation

• npm run check — 101/101 tests, package verification, and install smoke pass
• secret-pattern scan — no credential-shaped additions
• live Tessera recovery verified stock Claude Code 2.1.212, Fable 5, Claude Max login, and no connection to the gptCode loopback proxy