Previously we often had two sets of events, one in the network
package, and then another in the events package. We now only
have one, in the events package. Events now have a public API,
with minimal deps. There's an implementation package which has
the dependencies. This allows the network package to generate
events, without have a circular dependency on the events
implementation package.
Allow xgress and links to be destinguished by ID suffix
If a link destination is missing, send a link fault
Add forget-link router debug agent op to allow testing invalid
destinations
* Add support for multiple terminators to services and sync model abstractions with edge
* Add Snapshot to db.Db
* Make API friendly errors
* Add association querying. Consolidate Entity* interfaces
Paul Lorenz