local_embedded questions: port pinning, Knowledge Pages/fs mount support, standalone CLI upgrade path

[fanaticalfishing]

Running hindsight 0.9.0 in local_embedded mode (multiple profiles, each with its own embedded daemon) and hit a few things I couldn't find in the docs. Happy to split these up if you prefer.

1. Config port ignored — daemon binds a dynamic port

Each profile's config.json sets a port (e.g. 9817), but the embedded daemon binds a different, dynamically-assigned port (e.g. 9368), discoverable only from the log line "Daemon Started ( @ :9368)".

• Is the config port field honored at all in local_embedded, or vestigial?
• If I want a stable per-profile port (firewall rules, external health checks, a fixed hindsight fs mount target), what's the supported way to pin it?

2. Knowledge Pages / hindsight fs mount on local_embedded

The 0.9.0 Knowledge Pages feature is documented against server-mode banks. Does it work against a local_embedded per-profile bank?

• If yes: does hindsight fs mount need the daemon's runtime (dynamic) port, or is there a profile-aware invocation?
• Is there a minimum CLI version required to talk to a 0.9.0 daemon for fs mount?
• If it's server-only, a docs note would save local_embedded users some experimentation.

3. Standalone hindsight CLI binary — provenance and upgrade path

~/.local/bin/hindsight on my system is a ~3.6MB compiled ELF binary at version 0.8.2 — not pip/pipx-managed as far as I can tell — while the Python library in my venv is at 0.9.0.

• What's the canonical way to install/upgrade the standalone CLI?
• Does the CLI version need to stay in lockstep with the daemon's API version, or is it forward/backward compatible?