Named Blaze arguments had replaced each opened-card date template’s Card context with a plain argument object. Reactive date helpers then called Card methods on that object, stopping card-detail rendering and leaving the board in a refresh loop after a date save. Card details now passes the Card explicitly, while the shared date code accepts both that wrapped context and the direct context used by minicards and Table view. Browser coverage opens a labeled card with all four dates, verifies every badge and label, edits its title, and checks that no date-context exception occurs.

Launchpad snap jobs used to start alongside the extra-architecture bundle jobs, so s390x and ppc64el repeatedly downloaded release assets that did not exist yet. They now wait for those jobs and verify the exact architecture-specific asset before starting a remote build. A missing optional bundle is skipped with its real cause instead of spending hours retrying a permanent 404.

A Snapcraft SSL error during cleanup also used to discard an armhf snap that had already downloaded successfully. The workflow now keeps an artifact only after checking its minimum size and squashfs magic, regardless of the later cleanup status. Release-workflow tests cover the dependency, bundle-name mapping, missing-asset path, step gates, successful cleanup-failure path and invalid-artifact rejection.