Municipal Citizen App Store Deployment Automation Generator

Role: Senior Civic Tech Release Engineer specializing in municipal digital services delivery.

Context

• Municipality or public entity: {{municipality_name}}
• App bundle identifier: {{app_identifier}}
• Storefront deployment targets: {{target_storefronts}}
• Accessibility standard: {{accessibility_compliance_standard}}
• Staging environment endpoint: {{staging_environment_url}}
• Key management provider: {{signing_credential_vault}}

Task

Write an end-to-end Fastlane deployment script and configuration file that securely pulls signing assets, validates civic accessibility markers, tests staging connectivity, and uploads release artifacts to Apple App Store Connect and Google Play Console for {{municipality_name}}.

Method

1. Initialize environment parameters, referencing {{signing_credential_vault}} to safely retrieve non-exportable signing keys and API authentication tokens.
2. Define pre-flight lanes to verify package metadata, ensuring {{app_identifier}} aligns across all native configuration files.
3. Integrate automated checks confirming the build output adheres to {{accessibility_compliance_standard}} UI audit criteria prior to binary bundling.
4. Script an automated sanity check against {{staging_environment_url}} to guarantee backend service readiness before store dispatch.
5. Implement a lane for compiling native release builds with strict release-mode flags and zero test-telemetry leaking.
6. Configure store submission actions for {{target_storefronts}}, setting up proper release notes, public safety categorizations, and staged rollout percentages.
7. Add post-build cleanup routines that purge temporary keystores and send status payloads to municipal monitoring endpoints.

Constraints

• MUST produce syntactically valid Ruby Fastlane script code alongside necessary Appfile/Fastfile declarations.
• MUST NOT hardcode any secrets, API keys, or municipal passwords in the generated code.
• All error handling branches MUST abort the build immediately on certificate or compliance test failure.
• Code comments must clearly indicate where public sector compliance hooks are injected.
• The script must remain compatible with standard Linux and macOS CI runners.

Output format

1. Environment Setup & Prerequisites
2. Complete Fastfile (Executable script with lanes: before_all, lint_compliance, build_release, upload_store, error)
3. Appfile Definition
4. CI Execution Command Sequence

Self-review

• Verify that every variable from {{app_identifier}} to {{signing_credential_vault}} is actively referenced in the code.
• Confirm that release flags enforce production configurations without developer debug symbols.
• Check that staged rollout parameters are correctly declared for both iOS and Android stores.