[officialsuyogdixit]

Fresh installations still select 0.3.2 after publication and acceptance of the 0.3.3 security update. Promote the verified multi-platform application image through stable metadata and update the current self-hosting examples. The installer and commit-pinned Compose bytes stay unchanged; existing installations keep their saved image pin.

Validation:

• Runtime source 82b425d4bdd216b9fd155da8aed628a7eca95377 passed all six exact-main CI jobs. The public 0.3.3 release passed seven checksums and all 1,137 source-file hashes after fresh anonymous downloads.
• Both native image architectures passed container checks. Public source/version labels, parsed SBOM/provenance, index digests and actual anonymous pulls passed. Candidate image: softinator/feedbacks@sha256:730d6b05e44bedb97b3e39bd2bf9d2e0e2fc0017fa6be6552e5664ae6ced5bf0.
• One fresh installation passed all twelve installer, authentication, private screenshot and persistence checks. Only its own two containers were recreated; owner/project/thread/screenshot bytes and both named volume identities survived.
• The published image separately passed twelve isolated real-S3/auth/pairing/MCP/board/cleanup checks. Raw operational receipts stay private.
• Installer regressions 10/10, harness/catalog/docs, website build, release and diff checks passed locally. Required PR CI and automatic main website deployment remain separate gates.

No migration, runtime behavior, dependency, permission, extension or installer-code change. Preserve existing database and storage identities during operator-managed upgrades.