Sufficient durability / upgradability of Vat contracts for launch

[warner]

This is an umbrella ticket to track the pieces needed for upgrading individual contracts and core pieces of the chain.

• Vat Upgrade:
  • kernel API for upgrading vats #1848
  • design better vat-facing upgrade protocol (buildRootObject()? upgrade()?) #4382 unscheduled
  • bundlecaps to name bundles:
    • implement bundlecaps, bundle device #4372
    • controller.installBundle() #3269
    • maybe merge devices.bundle and devices.vatAdmin #4566
    • device errors should not (always) kill the kernel #4326
    • raw devices: maybe remove deviceSlots, reenable promises, merge companion vat #1346 unscheduled
    • promise that fires once a bundle is installed #4521
  • bundlecaps to load bundles:
    • createVat should take bundlecap, not bundle #4373
    • remove E(vatAdminService).createVat(bundle), only allow bundlecap #4486 unscheduled
    • fully validate bundles during controller.validateAndInstallBundle #4719
    • install-bundle transaction message #4396
  • zoe using bundlecaps to name contracts:
    • add zoe.installBundleID(bundleID) #4563
    • change all dapp deploy scripts to install by hash bundle, not source bundle #4564 V+1
    • Remove Zoe support for full-source bundles in favor of hash bundles #4565 V+1
  • vat upgrade gets contract bundlecaps:
    • implement device "hooks" to invoke kernel endowments with dref-kref translation #4726
    • slots in vatAdmin terminate/createVat are not translated correctly #4588
    • allow bundlecaps in vatParameters #4381
• durable objects/collections so upgrade retains behavior:
  • decide+implement API for durable virtual objects/collections: makeDurableKind? #4495
  • how to expose the Virtual/Durable Collection API? global? module import? #4255
  • virtual collections: range queries, sort options, indices #2004
  • "baggage":
    • "baggage": prepare for vat upgrade, deliver durable objects to successor  #4325
    • tolerate vatstore syscalls during vat startup #2910
  • makeKind upgrade
    • vat upgrade by replacing virtual-object behavior record #3062
• Liveslots upgrade:
  • upgrading liveslots: controller.setLiveslotsBundleID() #4376
• Kernel upgrade:
  • upgrading the kernel itself: controller.setKernelBundleID() #4375?
• make contracts durable:
  • non-Inter precious state is reachably durable #4511
• contract upgrade:
  • design contract behavior upgrade semantics / API / UX #3272
• zoe upgrade:
  • store Zoe state in durable/virtual objects/collections #4383
  • don't drop adminNode needed to upgrade Zoe #5013

[dckc]

From a PSM slog, I have this list of vats; I wonder to what extent they're covered by existing issues:

• "v7": "board", all vats that will be deployed in Vaults Release must be upgradable #6553
• "v8": "chainStorage", all vats that will be deployed in Vaults Release must be upgradable #6553
• "v15": "bank", make vat-bank upgradeable #6849
• "v6": "zoe", store Zoe state in durable/virtual objects/collections #4383
• "v1": "bootstrap", Bootstrap ocaps are stored durably in vat-bootstrap #4548
• "v4": mailbox vattp make vat-vattp upgradable #5667
• "v2": "vatAdmin", make vat-admin upgradable #5669
• "v3": "comms", "is transcriptless, so it's already taken care of."
• "v5": "timer", make vat-admin upgradable #5669

vats that are contracts:

• "v9": "centralSupply", all vats that will be deployed in Vaults Release must be upgradable #6553
• "v10": "mintHolder: USDC_axl", all vats that will be deployed in Vaults Release must be upgradable #6553
  • "v11": "mintHolder: AUSD", all vats that will be deployed in Vaults Release must be upgradable #6553
  • "v14": "mintHolder: BLD", all vats that will be deployed in Vaults Release must be upgradable #6553
• "v12": "psmCharter", use Durable objects for governance #5200
• "v13": "committee.econ", use Durable objects for governance #5200
• "v17": "governor: PSM(USDC_axl)", use Durable objects for governance #5200
  • "v18": "governor: PSM(AUSD)", use Durable objects for governance #5200
  • "v19": "governor: ?", use Durable objects for governance #5200
• "v16": "walletFactory", make Smart Wallet contract durable #5894
• "v20": "PSM(USDC_axl)", verify by end-to-end test a contract on-chain can be upgraded #6099
  • "v21": "PSM(AUSD)", verify by end-to-end test a contract on-chain can be upgraded #6099
• "v22": "provisionPool" all vats that will be deployed in Vaults Release must be upgradable #6553

[turadg]

@warner I went through the open items in the description task list with @dckc . We struck out the ones that aren't scheduled for Vaults release. All that were left were already done so I'm closing this.