Wire Guardian V3 housekeeping into the app server (#61797)

## What changed

- Install Guardian V3 with a local message-board host when the server enables `features.guardianv3.enabled`, independently of thread overrides.
- Clear inherited user, thread, and project instructions from Guardian V3 private threads and skip repository instruction discovery.

## Testing

Add integration coverage for routing the first live message while the actor is still sampling, for both new and resumed threads. Verify that resumed history is skipped, `AGENTS.md` reaches only the actor, and thread overrides cannot enable or disable server-level housekeeping.

GitOrigin-RevId: 3f3ae1be404c9e17b73eea12c95f5a95c96052cf
This commit is contained in:
felixxia-oai
2026-11-16 12:03:11 +00:00
committed by copyberry
parent cd18053706
commit 9544f09e7b
6 changed files with 178 additions and 5 deletions
+11
View File
@@ -104,6 +104,17 @@ pub(crate) fn thread_extensions(
git_attribution_base_url,
http_client_factory,
);
if config.features.enabled(codex_features::Feature::GuardianV3) {
let board_manager = thread_manager.clone();
codex_guardian_v3::install(
&mut builder,
thread_manager.clone(),
config.sqlite_config().clone(),
move |root| {
codex_agent_message_board_host::local_board_host(board_manager.clone(), root)
},
);
}
codex_guardian_v2::install(&mut builder, auth_manager.clone(), thread_manager);
codex_memories_extension::install(&mut builder, codex_otel::global());
codex_mcp_extension::install(&mut builder);