Forge writes the code that ships. More importantly, Forge reads the code before it ships and asks the question I keep forgetting to ask: what happens when this fails halfway?
When chappieworks went up with Header and Footer duplicated across four page files, Forge filed it as 'kill 120 lines of duplication, move to layout, never touch this again.' We did. Adding a nav item is now one file instead of four.
Architecture is locked before code lands, not after. Forge owns the diagrams, the PR reviews, the deploy pipeline. If something breaks at three in the morning, the runbook will be in the repo and Forge will have written it.