v0.7.0

Changed

• Breaking: MIGRATION_WALK_ORDER is renamed MIGRATION_ORDER and
  WALK_STOPPING_ERROR_NAME is renamed MIGRATION_STOPPING_ERROR_NAME. Their
  values are unchanged. A run of migrateBundle is a migration; the readers'
  lazy entry iteration is the entry cursor, space-archive's term (WBU-11).
• A descriptor recipient entry that names a recovered generation but fails its
  AES-KW check (was-client's IntegrityError) is a tamper signal, not a
  generation the migration skips as a non-recipient. In the current epoch the
  generation is dropped and the collection opens with the rest; the report's new
  generationCauses counts the dropped generations by error name. When no
  generation survives, the collection stops under IntegrityError with every
  Resource counted as unopenable. In an older epoch the error is the Resource's
  cause, and no older generation is tried. A sealed index schema whose epoch
  entry fails the check is not handed on, and the report's new
  indexSchemaCause names the error. Both report members are optional and
  additive. Pinned by tests; before, the same entry was reported as
  KeyUnwrapError (WBU-9).
• Requires @interop/was-client 0.99.1 (peer range bumped). Update to latest
  storage-core, space-archive, vh-resource-log and wallet-core deps.
• A corrupt older-epoch entry costs one unwrap per collection, not one per
  Resource under that epoch: was-client 0.99.1 remembers the failed check on the
  cipher. Nothing changed here; a migration test over several Resources under
  such an epoch counts the key-agreement derivations (WBU-10).