Figure out a way to prevent steps depending on "opaque" steps

[benjie]

e.g. $pgSelectSingle -> $pgSelectSingle.record() when requested through a non-@dataplan/pg class, to avoid user confusion.

Alternatively, make opaque steps even more opaque, e.g. create an opaque wrapper object that has hidden non-enumerable key containing the actual data.

[benjie]

This should also be used when handing from plan-space to resolver-space; e.g. if you have a const $user = users.get({ ... }) and then you have a resolver on the User type then you should be given the full User record rather than a meaningless tuple.

[benjie]

Punted to V6.