Address tech-debt (Q1 2025)

[j1010001]

Why (Objective)

Being able to efficiently add new code to the existing codebase with minimal risk.

Aside from technical debt, we also need to ensure we address any stale FLIPs. It puts us in a bad light if we ask the community for input, but then let proposals get stale. We should be good citizens in the community.

How will we measure success (Key Results) ?

Completing the Bugs, tech-debt & Flips task-lists for this cycle.

DACI

Role	Assigned
Driver	Technical: @fxamacker, EM: @j1010001
Approver	@dete
Consulted	@roham, @Kay-Zee
Informed	Flow engineering team

Bugs

Preview Give feedback

1. FVM Programs cache invalidation 🆕 #6507
   Bug Execution Performance +3
   

Tech-Debt

Preview Give feedback

1. Refactor and reduce technical debt atree#464
   Execution Technical Debt +2
   

Clean-up open Flips

Preview Give feedback

No tasks being tracked yet.

Stretch goals

Preview Give feedback

1. Add CI automation for storage health checks
2. [FVM] Remove FVM context settings from scaffold.go and put them into DefaultFVMOptions #5249
   Preserve Tech Debt good first issue +3