fix: use Atom instead of Primitive for passables

[erights]

#endo-branch: master

Assumes current endo

closes: #XXXX
refs: endojs/endo#2791

Description

Security Considerations

Scaling Considerations

Documentation Considerations

Testing Considerations

Upgrade Considerations

[cloudflare-workers-and-pages]

Deploying agoric-sdk with    Cloudflare Pages

Latest commit:	04c38c8
Status:	🚫  Build failed.

View logs

[kriskowal]

@erights Since renaming this type creates churn in Agoric SDK, let’s consider creating an alias. I think the alignment in names with OCapN is going to be less important than keeping Agoric SDK development stable.

[erights]

I thought I already did: https://github.com/endojs/endo/blob/14ddadb5ffec4ee7d3bf5ccdd9008ac368d8f4aa/packages/pass-style/src/types.d.ts#L28C1-L40C1

/**
 * @deprecated Use `Atom` instead, which is also the ocapn name. Now that
 * ByteArray has been added, this category no longer corresponds to
 * JS primitives, We also expect to move  to a passable-symbol representation
 * as a JS object, not a JS primitive
 */
export type Primitive = Atom;

/**
 * @deprecated Use `AtomStyle` instead. See `Atom` vs `Primitive`.
 */
export type PrimitiveStyle = AtomStyle;

I did this so agoric-sdk could work across this endo change without needing adjustment. This agoric-sdk PR can be indefinitely postponed.

Does this preservation of the previous type name exports work for current agoric-sdk? If not, we should definitely fix that.