[E09] Downstream recalculation on accept

[IanMayo]

Epic

Part of E09: Provenance Graph

Problem

When an analyst accepts an updated reference value, all downstream calculations that depended on the old value are potentially invalidated. Currently there is no mechanism to automatically identify and re-execute affected downstream tools.

Proposed Solution

Leverage the existing PROV dependency graph to:

1. When an analyst accepts an updated reference value, identify all downstream Analysis Log entries that transitively depend on the changed input
2. Re-execute each affected tool in dependency order with updated inputs
3. Record new Analysis Log entries for each re-execution (maintaining full provenance)
4. This also applies when an analyst manually amends a tool parameter in the Analysis Log

This is the engine that connects reference data currency (Feature 1) to solution comparison (Feature 2).

Success Criteria

• Accepting an updated value triggers re-execution of all transitively dependent tools
• Re-execution follows correct dependency order
• New log entries are created with full provenance
• Manual parameter amendment in the Analysis Log also triggers downstream recalculation
• Handles diamond dependencies (tool depends on two changed inputs) without duplicate execution
• Integration tests cover multi-step recalculation chains

Dependencies

Requires #148 (currency change notification modal)

Complexity

High