feat(web): add configurable queue/steer follow-up behavior #1479

1 issue identified (18 code objects reviewed).

• Merge Base: a60daa1
• Head: a2754fa

✅	File Path	Comments Posted
❌	`apps/server/src/orchestration/Layers/QueuedFollowUpReactor.ts`	1
✅	`apps/server/src/orchestration/Layers/QueuedFollowUpReactor.test.ts`	0
✅	`apps/web/src/providerModels.ts`	0
✅	`packages/shared/src/model.ts`	0
✅	`packages/shared/src/model.test.ts`	0
✅	`apps/web/src/components/ChatView.browser.tsx`	0
✅	`apps/server/integration/OrchestrationEngineHarness.integration.ts`	0
✅	`apps/server/src/orchestration/Layers/ProjectionPipeline.ts`	0
✅	`apps/web/src/components/ChatView.tsx`	0

apps/web/src/components/ChatView.tsx

line 3722: In onEditQueuedFollowUp, the follow-up is removed from the server queue (line 3722-3728) before the composer state is updated. If hydratePersistedAttachmentForDraft throws (e.g., a queued attachment lacks a previewUrl or the fetch fails), the catch block sets an error and returns, but the follow-up has already been deleted from the server queue. The user's queued follow-up is effectively lost — it's neither in the queue nor in the composer. [ Failed validation ]