fix(messaging): restore router agent auto-heal in React settings

[pascalandr]

Summary

• Fixes [Bug]: SlackBot not properly stabilizing connection to workspace #1138 by restoring the router-agent auto-heal behavior in the current React settings flow.
• Replaces the messaging placeholder in apps/app/src/react-app/shell/settings-route.tsx with the real MessagingView wired to live OpenWork router state.
• Ports the missing controller/state layer into apps/app/src/react-app/domains/settings/state/messaging-view-state.ts, including the old auto-heal path that creates .opencode/agents/opencode-router.md when messaging is enabled and the agent file is missing.

Testing

• git diff --check upstream/dev...fix/1138-router-agent-autoheal OK
• git diff --cached --check -- apps/app/src/react-app/domains/settings/state/messaging-view-state.ts apps/app/src/react-app/shell/settings-route.tsx OK while resolving the merge
• pnpm --filter @openwork/app typecheck could not provide a clean signal in this environment due local TypeScript install issues (react-router-dom, lucide-react, zustand, @tanstack/react-virtual missing) plus an existing streamdown / React types mismatch

Notes

• This is a larger React re-port than the original one-file Solid fix because the current React shell was still rendering a placeholder for the messaging tab.
• Kept as draft because this should get a real functional pass through the messaging settings flow before merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	Apr 30, 2026 8:19am

[vercel]

@pascalandr is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

[src-opn]

Requesting changes.

Code issue:

• apps/app/src/react-app/domains/settings/state/messaging-view-state.ts:826: the polling effect depends on refreshAll, but refreshAll depends on state that it mutates (refreshing, messagingEnabled, agent state) and the effect immediately calls refreshAll({ force: true }). Each refresh can change the callback identity, re-run the effect, clear/recreate the interval, and immediately start another forced refresh instead of waiting for the 10s poll. On a connected settings page this can turn into a continuous config/router/file refresh loop. Please make the polling effect stable so refresh state changes do not retrigger an immediate forced refresh.

Verification run:

• pnpm install --frozen-lockfile passed.
• pnpm --filter @openwork/app typecheck passed.
• pnpm --filter @openwork/app build passed, with the existing large chunk warning.
• pnpm --filter @openwork/app test:health passed.

[pascalandr]

Stabilized the messaging refresh poll so state changes no longer retrigger immediate forced refreshes.