[kirillDevPro]

Docs

docs/ARCHITECTURE.md — crate verified: moon-core (most commits since the file was last touched). Its sections on report replication, report readers, the station trade tape, the order-trace archive and settings/strategy backups match the code (constants, function names and flow order spot-checked).

Stale: the Crates list described moon-remote only as preparing a Linux server for moon-station. Since #1104/#1105 it also installs a MoonBot core moved onto such a server (moon-remote core_move: check, install, start, finish, remove through remote/moonbot-move.sh), called from the terminal's Connections card and from the moon-remote core-move* commands. The line now says so.

Verified against crates/moon-remote/src/core_move.rs, crates/moon-remote/src/main.rs and the terminal callers in crates/moon-ui-gpui/src/backend/core_move*. tools/tour/README.md was read first and is current.

Reviewer: Codex. It disputed a parenthetical saying the new core always starts only after the old one is seen down (core-move-start --old-stopped skips that observation); the claim was dropped.

Quiet jobs

• Leftovers: no open lane pull requests.
• Advisories: cargo deny check advisories bans sources green on origin/main.
• Fix: every open auto-found issue carries needs-human.
• Review: 70ff57f (fix(core-status): treat a mirrored API expiry date as remaining days #1121), 1a29637 (fix(station): walk the tape file in chunks and name the phase in memory lines #1091) and 213844a (chore(deps): pin moonproto to 73b3b4ef, keep a zero RTT as no reading #1103) reviewed against their callers; no demonstrable defect.