# 14-Jul-2026 — fix+refactor(inbox+server): stabilise direct inbox routing [ref #307](https://github.com/nbarrett/ngx-ramblers/issues/307)

## [build 771](https://github.com/nbarrett/ngx-ramblers/actions/runs/29294965056) — [commit dd6b3ca](https://github.com/nbarrett/ngx-ramblers/commit/dd6b3ca9d3cdb1cae7bc7895078767cc05f5bf1d)

_____

## What's new

Direct inbox delivery now recognises the shared apex catch-all as a valid route without requiring redundant per-role Cloudflare rules. Inbox providers can be switched without losing an explicitly configured catch-all policy, and deployed email workers are generated with all required shared code included.

## At a glance

- Treat the active shared inbox router as successful direct delivery for apex mail.
- Preserve an existing Inbox, Forward or Drop catch-all choice when switching providers.
- Show clearer direct-delivery and worker update status in the administration screens.
- Use one consistent inbound signing secret across workers and the server.

## Technical changes

- Extract Cloudflare email-routing controllers from the route declarations.
- Inline shared worker template dependencies into self-contained deployed scripts.
- Copy all worker TypeScript assets required by runtime script generation.
- Add focused coverage for provider switching, shared catch-all detection and generated worker completeness.