Here are some ideas:

• Debugging: figuring out why a variable or object property has an unexpected value

• Finding relevant code, possibly during onboarding of new devs

• Security: see where insecure values end up at runtime

• Telling BE devs what endpoint is used for a specific part of the UI

The architecture could also enable a few other features, like pausing when a particular value is encountered anywhere in the code.

That one is huge for me. So often coming into a new codebase (especially in the case where some of the libraries or underlying frameworks are new to me) I just want to know "How the F was that value populated??"

Kudos, would be super useful in my opinion.

Being able to highlight a part of the dom and click through the stack of where it came from would be awesome! And it would work with just about any framework out there!

By the time you're no longer a "new dev," you're a "new dev" to the code you wrote when you started the job :) so it's a pretty universal need!