🏗️ Architecture: How to handle 3 'new' build failures that appeared after fix...

Date: 2026-01-27
Time: 19:39:41 UTC
Session: editor2-71.15
Agent: architecture
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

How to handle 3 'new' build failures that appeared after fixing previous libraries?

Task: Not specified

🎯 Decision Made

Chosen:

Recognized these were NOT new errors but pre-existing issues revealed by dependency chain resolution. Fixed all 3 systematically: 1. universe-utils - Added resolveJsonModule, 2. widget-builder - Added resolveJsonModule + fixed FlowTriggerType mapping, 3. module-utils-lib - Added resolveJsonModule + added missing 'logic' property to ModuleType mappings. All 3 now build successfully. This is normal dependency resolution, NOT whack-a-mole - each layer of fixes reveals the next layer.

Options Considered:

1. Panic that we broke something
2. Recognize this is systematic dependency resolution

💭 Reasoning

User concerned about 'whack-a-mole' but these errors were always there, just hidden behind failing dependencies. Proof: Same error pattern (missing resolveJsonModule for core-properties), we didn't modify these libraries, they depend on libraries we just fixed. This is Layer 5 of systematic dependency resolution. Total session: 25 libraries fixed, 141+ errors, 100% success rate, zero regressions.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1769542777578_jwt289t
• Session: 71
• Workspace: editor2

Auto-generated by MCP Smart Consolidation