contract upgrade test of KREAd

[turadg]

What is the Problem Being Solved?

#8329 is the Deployment test of #8280

We also need "Upgrade test" of the contract upgrading in place.

Description of the Design

We have several ways to test this:

• swingset test
• bootstrap test
• chain test

Now that we have the deployment test, that's a high fidelity way to do the chain test. Let's do that.

https://github.com/Agoric/agoric-sdk/blob/master/packages/builders/scripts/vats/restart-vats.js#L24 shows how to write build a proposal that restarts all vats. we only need to restart contracts and specifically just two,

• https://github.com/Kryha/KREAd/blob/develop/agoric/contract/src/index.js
• https://github.com/Kryha/KREAd/blob/develop/agoric/contract/src/kreadCommitteeCharter.js

#8361 or a new branch off that is where the work should go #8361

From bootstrap space gather,

• kreadKit - restarting a governed contract
• kreadCommitteeKit

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[turadg]

Passing now with a manual edit to the KRead contract: renaming start to prepare to satisfy the Zoe in MN-u11.

When it comes time to actually upgrade, their updated contract can use prepare or if MN has #8045 then it can continue to use start.

There is more to do to make this kind of test parameterized but for now the requirement is satisfied: we have tested contract upgrade in a repeatable manner.