CLI Abyss tracker asks for cargo instead of the wallet #48

Parent

#38

What to build

The terminal Abyss tracker works out profit the same way as the desktop app. It asks for the filament, then for each run asks:

• cargo before, defaulting to the previous run's cargo after (the Tracker's latest-cargo-after lookup), or no default on a session's first run
• cargo after
• time left

It logs the run as a cargo run. The per-run summary shows cargo after instead of "New total". It no longer asks for a starting wallet.

Acceptance criteria

• Starting the CLI asks for the filament and not for a wallet
• Each run prompts for cargo before (with the default shown and accepted on Enter), cargo after and time left
• The logged run has profit = after − before, the same as the desktop app
• The run summary shows cargo after
• Bad input is re-prompted rather than crashing (non-numeric cargo, invalid time left)
• The CLI no longer calls the wallet-based logging method
• Tests that drive the CLI with scripted input against a temp database cover the prompts, the default and the logged profit
• Full test suite green

Blocked by

• Log abyssal runs from typed cargo before / cargo after #45