Docker headless deployment: Cloudflare Tunnel docs point users to unavailable Access Anywhere token UI

[RimuruW]

Describe the bug
Docker headless deployment cannot follow the documented Cloudflare account remote access flow. The remote access docs say to configure Cloudflare Tunnel by going to Mem Settings → Access Anywhere → Cloudflare account, then pasting the Public URL and Tunnel token. In Docker deployment, I can only access the web UI at /app, and there is no place to enter the Cloudflare Tunnel token.

The Docker docs also say the Docker image does not bundle cloudflared and recommends using a Cloudflare Tunnel sidecar, so the Docker and remote access docs feel inconsistent for this setup.

To Reproduce
Steps to reproduce the behavior:

1. Install Nowledge Mem using the official Docker deployment.
2. Open the web UI at http://<host>:14242/app.
3. Try to follow the Cloudflare account setup from the remote access docs.
4. Look for Settings → Access Anywhere → Cloudflare account, or any place to paste the Cloudflare Tunnel token.
5. Click the remote/local connection switch if shown.
6. The UI returns to the web login or connection flow, but still does not expose a Cloudflare Tunnel token input.

Expected behavior
Docker/headless users should have a documented way to configure Cloudflare Tunnel.

Expected options:

1. The remote access docs include a Docker-specific Cloudflare Tunnel section with a cloudflared sidecar compose.yaml example.
2. The docs clearly state that Docker supports remote access through API key and external tunnel/reverse proxy, but does not manage the Cloudflare Tunnel token inside the web UI.
3. The web UI explains that Access Anywhere tunnel management is unavailable in Docker/headless mode, instead of making it look like the token input is hidden somewhere.

Screenshots
I can provide a screenshot of the Docker web UI showing the remote/local connection flow, where no Cloudflare Tunnel token input is available.

Additional context
Relevant docs:

• Docker deployment: https://mem.nowledge.co/zh/docs/docker
• Remote access: https://mem.nowledge.co/zh/docs/remote-access

Docker docs say:

Bundled cloudflared. Use a Cloudflare Tunnel container as a sidecar if you need that pattern; the headless image is intentionally network-agnostic.

Remote access docs say to return to Mem Settings → Access Anywhere → Cloudflare account and paste the Tunnel token. That path does not seem available from Docker /app.

This may be a documentation/UX bug rather than a backend bug. The main issue is that Docker users are guided to a UI flow that does not exist in headless deployment.