#316 fix(projects): take --volume-size back out of upgrade-instance

Summary

Disk resizes are admin-only. Provisioned disk is not billed, so customers can't grow it themselves. This reverts the --volume-size part of PR 315, which is merged but has not been released (npm latest is 0.2.8).

• projects upgrade-instance <instanceType> is back to taking only an instance type. risk-registry.ts and UpgradeInstanceBody match the code from before 315.
• projects update --storage-size stays hidden and fails before login or any API call with "Disk size changes go through InsForge support." Released versions shipped this flag, and it only saved a number.
• UpgradeInstanceResult drops previous/newVolumeSizeGiB. The customer endpoint no longer returns them.

Companion backend PR: the customer upgrade-instance route rejects volumeSizeGiB and silent.

Testing

manage.test.ts checks that update --storage-size 20 exits before requireAuth and updateProject, and that the error names support. Removing the early throw turns it red. Full vitest run passes (839), and eslint and build are clean.

🤖 Generated with Claude Code

---

Summary by cubic

Reverts the unreleased --volume-size disk resize support, since provisioned disk is not billed and disk resizes go through InsForge support.

• projects upgrade-instance <instanceType> takes only an instance type again; --volume-size is removed and the result no longer includes volume sizes.
• projects update --storage-size still errors, but now fails before authentication with "Disk size changes go through InsForge support."

Summary by CodeRabbit

• Updates
  • Instance upgrades now change the instance type only. The command requires an instance type and confirms that the change may restart the instance and affect billing.
  • Disk-size changes are no longer available through the project update or instance upgrade commands. The project update command directs you to contact InsForge support for disk-size changes.