syntaqxA notification put away in the panel stays away: dismissing several quickly made one come back for a moment and go again. Each card hid itself only while its own Done, Snooze or Move back was in flight; once that settled it showed again until the panel's list reloaded without it, and each further dismissal put that reload off. A card that stepped out now stays out until the list drops it, coming back only if its request failed or the item itself changed. Checked: apps/web tsc -b.dc2c300History
- ..
- background-step.yml
- bare-event-with-settings.yml
- branches-and-ignore.yml
- call-input-type-missing.yml
- call-input-unexpected-property.yml
- call-output-value-missing.yml
- call-secret-unknown-key.yml
- caller-job-env.yml
- caller-secrets-word.yml
- concurrency-unknown.yml
- concurrency-without-group.yml
- container-unknown.yml
- credentials-unknown.yml
- defaults-run-unknown.yml
- defaults-unknown.yml
- dispatch-input-unknown-key.yml
- dispatch-unknown-key.yml
- environment-unknown.yml
- environment-without-name.yml
- g1t-not-mapping.yml
- g1t-not-under-strategy.yml
- job-id-case-duplicate.yml
- job-id-digit.yml
- job-id-dot.yml
- job-id-reserved.yml
- merge-key-list.yml
- merge-key.yml
- on-missing.yml
- permission-metadata.yml
- permission-unknown.yml
- push-branch-typo.yml
- push-inputs.yml
- push-types.yml
- root-true-key.yml
- runs-on-mapping-unknown.yml
- runs-on-missing.yml
- schedule-not-list.yml
- schedule-without-cron.yml
- service-unknown.yml
- shell-on-action-step.yml
- step-id-duplicate.yml
- step-id-invalid.yml
- step-uses-and-run.yml
- steps-mapping.yml
- strategy-unknown.yml
- unknown-event-in-list.yml
- unknown-event-in-mapping.yml
- unknown-event.yml
- unknown-job-key.yml
- unknown-root-key.yml
- unknown-step-key.yml
- uses-and-runs-on.yml
- uses-and-steps.yml
- wait-step.yml
- with-on-run-step.yml