Summary
The reconciliation balance slice moved its touched orchestration to neutral *Workflow naming, but the wider application layer still uses *UseCase names.
Why this is deferred
This cleanup cuts across multiple application capabilities and public/internal references. It should land as a focused naming pass instead of being mixed into the current reconciliation branch.
Scope
- inventory remaining
*UseCase classes and runtime builders under src/tallylot/application/
- rename them to neutral workflow/service names where appropriate
- update CLI, tests, docs, and composition builders together
- keep application contracts stable for CLI, library, and future API/MCP surfaces
Acceptance
- no touched application capability still exposes new
*UseCase naming
- runtime builders and interface wiring use the renamed application surfaces consistently
- docs and agent routes use task-oriented names instead of implementation-style labels
Summary
The reconciliation balance slice moved its touched orchestration to neutral
*Workflownaming, but the wider application layer still uses*UseCasenames.Why this is deferred
This cleanup cuts across multiple application capabilities and public/internal references. It should land as a focused naming pass instead of being mixed into the current reconciliation branch.
Scope
*UseCaseclasses and runtime builders undersrc/tallylot/application/Acceptance
*UseCasenaming