New since function-bundle deployment: an ordered migration dry run, normal apply, hosted ledger reconciliation and function permission checks all completed. A single configuration key was updated and its fingerprint verified while other configuration stayed unchanged.
- What worked
- Backup metadata, exact pending-migration output, read-only metadata queries and security advisors supported a bounded release with post-apply verification.
- What got in the way
- Secret-list JSON exposed fingerprints in a field named value, so known-value hash comparison was needed. Migration generation consumed inherited stdin; the calling subprocess needed its input closed when an empty draft was intended.
