Tests: journal replays reproduce File Info's dates; the MCP connect test holds its own port

[bflatastic]

Fixes three tests that failed at random in CI, two caused by File Info's clock dates (#77) and one by a port race, and a fourth that was silently skipping cases whenever the clock ticked.

• M4.55: a journal replay reproduces File Info's dates.
  • Cause: file.new and saves read their dates from the clock. A journal replayed a second later therefore rebuilt a different document, which failed journal_replay_reproduces_document, rich_fixture_satisfies_invariants_and_undoes_to_blank and, latently, known_bugs::bug_nested_commands_double_journal.
  • One approach: a date is a command input that defaults to now, and the journal records the value actually used.
    • file.new {created?}, plus document.save and file.saveAs {modified?}: Unix seconds, or null for no date. They are read by cmd::date_param and resolved and recorded by cmd::clock_date.
    • The save date is stamped inside M4: Save As format chooser, Save keeps its format, Save a Copy, Revert, templates, File menu details (M4.14–M4.17) #89's single save path (SavePlan.modified), so every save stamps the same way. Save a Copy and templates leave the dates alone.
  • Actions: recorded actions use Session::journal_for_action, which leaves these dates out (REPLAY_ONLY), so playing an action later dates the document then.
  • Test fixtures: fixture documents get a fixed date (fixtures::CREATED).
  • A hidden skip: mcp/tests/protocol_props.rs::run_command_sequences_match_local_session used to skip any case where the clock ticked. It now dates its local document like the headless one, and every case is compared.
• M1.9: remote_connect_fails_fast holds its own closed port.
  • Cause: the test bound a port and dropped it, so another process could take it.
  • Fix: it now holds a bound but not listening socket, so connections are refused and nothing else can bind the port. It also checks the failure comes within 5 s.
  • New dependency: this needs socket2 0.6 (MIT OR Apache-2.0), as a test-only dependency of vectorcraft-mcp.

Known limit: a file.new or save inside command.batch doesn't get its date recorded, the same existing limit as the recorded preference values.

Checks

Rebased onto 53f4279 (#90). cargo xtask ci passes all 7 steps (fmt, clippy, test, assets, brands, layers, wasm): 2,334 tests, 0 failed.

• Each flake reproduced first:
  • a forced 1.1 s sleep failed the clock tests every time;
  • re-binding the port failed the MCP test.
• After the fix:
  • journal replay passed 25 runs × 96 cases;
  • the MCP suite passed 100 runs.
• Nothing dropped:
  • every test name on main still exists, with five added in tests_journal.rs;
  • command ids, UI_COMMANDS, menu entries and MCP tools are unchanged.
• Changed test bodies: remote_connect_fails_fast and run_command_sequences_match_local_session.

🤖 Generated with Claude Code