Ramnique Singh efeaae1e19 refactor(x): workspace-context loading gets one trait-gated chokepoint ... The workspaceContext trait was consulted separately at every assembly site before loading agent notes / work dir — a convention each caller had to re-remember, where a forgotten check either leaks the user's agent-memory into non-copilot prompts or silently omits it for the copilot, and neither fails loudly. The loaders move out of the legacy runtime file into agents/workspace-context.ts, and loadWorkspaceContext() applies the trait gate INSIDE: both engines now call it (the resolver keeps its loader test-seams by injecting them through), so a future assembly site structurally cannot skip the gate. Tests pin the gate: non-workspace agents get nulls even when the loaders would yield values. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-10 08:45:58 +05:30
..
core	refactor(x): workspace-context loading gets one trait-gated chokepoint	2026-07-10 08:45:58 +05:30
shared	refactor(x): one delivery path for turn events — chat, channels, deltas	2026-07-09 15:47:21 +05:30