Merge pull request #9004 from Agoric/ta/remove-restart-vats

remove restart-vats from a3p

a3p-integration/README.md

@@ -54,6 +54,8 @@ For a chain software upgrade proposal, the `type` is `"Software Upgrade Proposal
 - `planName` is the "upgrade name" included in the proposal which must match the value in the upgraded chain software. In the `master` branch its value is `UNRELEASED_UPGRADE`. In the release branches, it's `agoric-upgrade-NN`.
 - `upgradeInfo` contains other details passed to the governance proposal. In particular, the info can have a `coreProposal` field which instruct the chain software to run other core proposals besides the one already configured in the chain software's upgrade handler (see `CoreProposalSteps` in `/golang/cosmos/app/app.go`). This field is likely not relevant for release branches.
 
+For an example, see `a:upgrade-next` in master.
+
 ### Core-eval proposal
 
 The `type` of a core-eval proposal is `"/agoric.swingset.CoreEvalProposal"`, and content is submitted from a `submission` subfolder.
@@ -62,6 +64,8 @@ If the proposal is planned to be executed after the chain software upgrade, and
 
 For core eval proposals executing before the chain software upgrade, the `submission` should be checked in, since bundles built from newer software may not be compatible with older chains.
 
+For an example, see https://github.com/Agoric/agoric-sdk/pull/8907
+
 ## Hooks
 
 <!-- TODO: Move this section over to synthetic-chain docs -->

a3p-integration/proposals/b:localchain/README.md

@@ -1,5 +1,3 @@
-A demonstration of how to declare a CoreEvalProposal
-
-The console output will show errors, because the `restart-vats` proposal is not well maintained.
+CoreEvalProposal to install vat-localchain
 
 The `submission` for the proposal is automatically generated during `yarn build` in `a3p-integration` using the code in agoric-sdk through `script/generate-a3p-submission.sh`.