Came to say the same thing. In Rust, you can also have fluent interfaces that return different types as you build, which means that you end up being more typesafe throughout the construction process.
Static analysis is your friend here. TypeScript, Rust, and C# can all identify dead code and report errors or warnings from that, and can perform "find all usage" searches across a workspace.
At this point aren't you still hard coding commands, but using "links" rather than URLs? And doesn't the dependency on every link in the chain outweigh one - easily maintained - URL?
There are commercial products that you can leave running all the time to generate data from your packets on the fly, such as ExtraHop (http://extrahop.com). There are also continuous PCAP tools, but they need massive amounts of storage and in larger environments the lookback you get is limited.
This looks like something out of the design team for Windows 8 (in both good and bad ways). It is visually striking, a dramatic simplification of what currently exists, and it makes several assumptions about the real world of what app developers need and how they can plug into OS-provided UI surfaces. One of the most painful learnings for Microsoft with Windows 8 was that overly-standardizing things like content sharing and tagging leads apps into situations where the affordances don’t work.