Felipe Coury 0ed34eb9ce Ensure side-chat policy reaches the first model request (#60067) ...

## Why

An inherited turn can suppress a fork's configured developer instructions, leaving the first side-chat request without its developer policy.

## What changed

- Move shared side-conversation instructions and the history boundary into `codex-context-fragments`.
- Inject the developer policy before the user-role boundary when creating a TUI side-chat fork, while retaining the configured instructions.
- Distinguish attached and temporary policies, applying the worktree restriction only to temporary side chats.
- Add guidance to set up recurring monitors in the main chat or a new chat because temporary side chats cannot run scheduled updates.

## Testing

Add a TUI integration test that checks the first side-chat model request contains the policy and boundary. Add a core request-history snapshot covering an attached side chat that preserves inherited context, policy, and its prior answer after resuming from disk.

GitOrigin-RevId: 889cb317dc3327457cd9ef0879ec9f77dbfaeeba

2026-11-07 05:59:44 +00:00

..

src

Ensure side-chat policy reaches the first model request (#60067)

2026-11-07 05:59:44 +00:00

BUILD.bazel

chore: extract context fragments into dedicated crate (#26122)

2026-06-03 12:25:21 +02:00

Cargo.toml

Support typed content in contextual prompt fragments (#54776)

2026-10-17 04:02:21 +00:00