fix(probe): isolate probe-origin failures from all deactivation sites (#10694)

Merged — locally validated (23/23 focused probe-isolation tests, typecheck:core clean, file-size/changelog gates green). Reconciled with today's #8367 (codexAccount module extraction, merged earlier): the persistCodexQuotaState closure this PR touched had been extracted into persistCodexChildQuotaResponse — applied the same probe-origin isolation guard (!shouldIsolateProbeFailures()) at its new call site instead of reintroducing the old inline closure. Thanks for closing this real gap!
This commit is contained in:
Dizzle
2026-08-20 15:30:29 +02:00
committed by GitHub
parent ff8b7b172f
commit bb98e9a345
17 changed files with 1060 additions and 123 deletions

View File

@@ -174,6 +174,10 @@ export const updateSettingsSchema = z.object({
)
.optional(),
customBannedSignals: z.array(z.string().max(200)).optional(),
// #9817: opt-in (default off) — lets a probe-origin (model test-all)
// failure deactivate a connection like real traffic. Off by default:
// probe failures are recorded but never mutate routing state.
probeCanDisable: z.boolean().optional(),
debugMode: z.boolean().optional(),
logToolSources: z.boolean().optional(),
hiddenSidebarItems: z.array(z.enum(HIDEABLE_SIDEBAR_ITEM_IDS)).optional(),