v3.41.4

## Fix

- **`agentdb_pattern-store`/`agentdb_pattern-search` now surface `degraded: true`** whenever the response comes from anything other than a healthy `reasoningBank` controller (the `bridge-fallback` and `memory-store-fallback` paths alike), instead of only in a note string a caller has no structural reason to check. Fixes #3288.

Includes a follow-up correction (`b9ca64f80`) after review caught that the initial fix only handled the case where the controller registry is entirely absent, missing the more common case where the registry exists but ReasoningBank itself is unusable (`controller: 'bridge-fallback'`) — the degraded flag is now applied at the `result.controller === 'reasoningBank'` boundary in both handlers rather than per fallback-label, so it can't be reopened by a future fallback label. See #3323 for the full discussion.

This does not address why `vectorBackend`/`reasoningBank` fail to activate in a given deployment — that's tracked separately in #1228 (ADR-053) and #2296.