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: @turbolent, EM: @j1010001
Approver	@dete
Consulted	@roham, @Kay-Zee
Informed	Flow engineering team

Bugs

Preview Give feedback

No tasks being tracked yet.

Tech-Debt

Preview Give feedback

1. Add CI automation to verify storage iteration #2688
   Chore +1

Clean-up open Flips

Preview Give feedback

1. Import Aliasing flips#314
   flip: cadence +1
   

Stretch goals

Preview Give feedback

1. Runtime needs to support importing Attachment and TypeValue of AttachmentType #3114
   Feature Technical Debt +2
2. Split typing from rest of type checker #2630
   Feature Feedback Technical Debt +3
3. Refactor string interpolation to separate parsing logic #3624
   Good First Issue Technical Debt +2