Surface setup error state instead of console.warn in useSetup

Docs/Tasks.md

@@ -484,6 +484,8 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
 
 **Goal:** Replace the `console.warn` with `setError(err instanceof Error ? err.message : "Unknown error")` so that the error is surfaced to the consuming component via the hook's public interface. Remove the `console.warn` entirely — the hook already has an `error` state for this purpose.
 
+**Status:** Completed.
+
 **Possible traps and issues:**
 - Verify that `SetupPage.tsx` (or whatever consumes `useSetup`) already renders the `error` state. If it does not, add an error message display (a Fluent UI `<MessageBar intent="error">`) so the surfaced error is actually visible to the user.
 - `console.warn` in hooks that ship to production will produce console noise for end users and may appear in error monitoring tools as unexpected warnings. The rule is to handle errors in state, not in the console.