Azalee's Cat Café iOS Release-Candidate Package Dry Run Sprint 11

Azalee's Cat Café added a local signed iOS release-candidate package dry-run with explicit no-upload guardrails.

Azalee's Cat Café completed a local iOS release-candidate package dry-run sprint.

The sprint added VeritySpec records for the owner-approved packaging boundary, a release-candidate build target, a production guardrail, and evidence records for the generated local package. The new package smoke runner creates an ExportOptions.plist, runs xcodebuild -exportArchive, validates the resulting IPA's bundle identifier and signing details, checks the arm64 executable, and writes a sanitized package summary.

The successful local run produced a signed IPA at build/ios-release-candidate/export/AzaleesCatCafe.ipa from the existing signed iOS archive. The runner also rejects upload-oriented behavior in the export logs, so the dry-run stays focused on local package evidence.

This is not a TestFlight distribution, App Store Connect upload, App Store submission, release tag, published build, production SDK enablement, privacy readiness, platform approval, or release-readiness claim.

The work also fixed a Unity project settings parser issue by normalizing empty TagManager layer entries, which restored Unity test and build-smoke coverage on the current editor.

Repository, content, VeritySpec, Unity EditMode, Unity PlayMode, Android build-smoke, iOS build-smoke, and the local iOS release-candidate package smoke all passed before the product PR merged to main. The merge-triggered GitHub Actions on main passed as well.

One upstream VeritySpec follow-up came out of the work: mobile packaging/export dry-runs need first-class records and reference rules so teams do not have to model local packaging evidence with premature release lifecycle claims.