Aha, good to know…
I mean, this is just postponing jhack’s inevitable overtake of the world, but I can see the point.
is snapd/state.json guaranteed to be up to date?
it’s up-to-date, but it’s not intended to be consumed by outside snapd itself, so I would be -1 on that system-files access. I see two path forwards: either making jhack classic or waiting for snapd-observe.
If the alternates are either confinement: classic or granting snapd-control, I would prefer to +1 snapd-control and when snapd-obvserve is ready we can revoke snapd-control in favour of snapd-observe.
Classic does have the advantage of requiring --classic to install which alerts the user to the power of the snap, so perhaps in this case we do snapd-control but no auto-connect. Could jhack alert the user that they’re required to connect it just for jhack charm vinfo ?
I concur with @dclane’s choice of snapd-control over classic. I support the use of snapd-control temporarily, but we should reduce privileges once snapd-observe is available, and it should be without auto-connect. +1