and since it is either trusted (fully) or not, the clearest thing to do is to suggest `--force-dangerous`.
Other more elaborate plan would be to design a tool for creating and signing all the assertions needed to distribute snaps safely (and pack them please, 5+ files would be annoying).
Evan,
snap-build doesn't fill the whole trust-path for a snap:
[snap-build =>] snap-revision => snap-declaration => account-key => account
and since it is either trusted (fully) or not, the clearest thing to do is to suggest `--force- dangerous` .
Other more elaborate plan would be to design a tool for creating and signing all the assertions needed to distribute snaps safely (and pack them please, 5+ files would be annoying).