# CLI 0.0.3

- Animated activity status now works in direct commands such as `li convert`, as well as the interactive menu. Displays the current artifact/operation, retry attempt where applicable, provider status, and elapsed time.
- Shows waiting-for-output versus receiving-output status. Every 30 seconds, readable progress updates are written to the console and configured log file. Redirected/dumb terminals receive plain text without animation; completion, errors, and Ctrl+C stop the indicator cleanly.
- Adds deterministic nested solution/project dependency scanning across shared projects, project references, assembly candidates, imports, packages, explicit source items, and schema references. Full JSON/Markdown reports preserve unresolved and ambiguous findings.
- Adds `li dependencies --source <directory> --output <directory>`, with optional `--root`, `--include`, and `--exclude` source-relative paths. This inspection command does not invoke AI or require activation.
- Separates the complete source inventory from migration evidence. Unconnected nested projects are omitted from evidence; shared and ambiguous dependency candidates are retained for review. `migration.sourceSelection` and per-batch-entry overrides let users select roots and explicitly exclude unrelated files without deleting them.
- Retains application binding evidence and inventories MSI/DLL files. DLLs are not decompiled; nested MSI files are not extracted by the dependency scanner. Existing batch MSI-input extraction remains available. No dedicated BizTalk Deployment Framework parser or group-binding selector is included.
- Prevents reuse of an incompatible recorded discovery scope after source selection changes. Use a fresh generated workspace and rerun discovery/planning when requested; existing source and outputs remain intact.
- Handles interrupted and malformed Ollama response streams without leaving the activity indicator running.

The activity indicator means a request is pending, not that the CLI can prove server progress. Received character counts are not token counts or completion percentages. Existing stage-end token reports are unchanged.

Static dependency scanning is not MSBuild execution, runtime dependency verification, or binary reconstruction. Provide application-specific bindings, source implementations, dependencies, and rules. Dynamic references and assembly identity compatibility still require review.

Verification: 131 automated CLI tests, TypeScript compilation, lint, and production build pass. No real migration, provider purchase, activation, or usage-counter reset is performed by updating. Full clean-machine Windows/macOS/Linux qualification remains separate from these checks.