Local log monitor and install documentation assume an unwired file-log sink

[Calmingstorm]

Confirmed operator-tool/runtime mismatch

Reviewed master at 886c36d8ebe861aa987059a1744d45b78797baae (v4.7.0). Suggested priority: P3.

scripts/monitor.sh defaults local log viewing to data/logs/odin.log. The current entrypoint configures stream logging, the packaged service sends it to journald, and the file-handler helper is not wired into startup. The config registry explicitly says logging.directory is not a file-log sink, while installation/configuration tables still suggest log directories contain application logs.

The local monitor against a clean snapshot returns Log file not found .../data/logs/odin.log and asks for ODIN_LOG_FILE; source inspection confirms the default runtime does not create it.

Acceptance criteria

• Make the supported log-view command and installation/configuration documentation agree with actual stdout/journald behavior.
• Explain source-run versus packaged-service logs and preserve explicit ODIN_LOG_FILE overrides.
• Do not automatically change legacy log destinations merely to match stale prose.
• Test default-path messaging without requiring a live service.

This is an operational usability bug, not evidence of lost runtime logs. No service or source changes were made.

[Calmingstorm]

Fixed in v4.8.0 (PR #405): https://github.com/Calmingstorm/Odin/releases/tag/v4.8.0 — see the release notes for details.