Ramnique Singh d0018daad3 refactor(x): one ModeFlags schema behind all three composition shapes ... The app-toggled mode flags were hand-mirrored in three places (the resolver's CompositionOverrides zod schema, CapabilityContext, and ComposeSystemInstructionsInput) and copied field-by-field with '?? false' defaults — so a mode missed at one site compiled clean and silently never composed. Now capabilities/types.ts declares one zod ModeFlags schema with defaults: the wire shape (all-optional, what turn files carry), the resolver's concrete parse output, and the composition context all derive from it; CompositionOverrides just extends it with the resolver-only keys, the composer takes {instructions, notes, workDir} & ModeFlags with a rest-spread (no copy list), and the legacy call site passes explicit false for the modes it never composes. Adding a mode = one schema key + one record; anything less is a compile/parse error. New resolver test pins historical-composition compatibility (sparse, null-heavy, unknown-key, and garbage compositions all compose exactly as before). Golden snapshots unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-10 08:43:24 +05:30
..
core	refactor(x): one ModeFlags schema behind all three composition shapes	2026-07-10 08:43:24 +05:30
shared	refactor(x): one delivery path for turn events — chat, channels, deltas	2026-07-09 15:47:21 +05:30