Stack List “Updated at” should reflect last applied run, not any run

On the Stacks → All Stacks page, the Updated at column updates whenever a run finishes—no matter whether it applied successfully, failed, or was discarded after a plan‑only run. As a result, simply kicking off a speculative/plan‑only run bubbles that stack to the top of the list, even though the live infrastructure never changed.

Why it’s a problem

• I use the column to spot which stacks have had real infrastructure changes or gone the longest without them.

• If a plan‑only (speculative) run finishes, its stack’s Updated at timestamp becomes “just now.” When you sort the stack list by that column, those speculative stacks jump to the top. The genuinely changed stacks—whose last apply happened earlier—get pushed lower in the list, so you don’t see them at a glance.

• Auditing recent production changes becomes noisy.

Requested change
Have Updated at reflect the timestamp of the most recent run that entered the Apply phase, regardless of outcome:

I’m neutral on whether this is handled by a single ‘Updated at’ field (showing any run that reached Apply) or by separate fields for ‘Last apply attempt’ and ‘Last successful apply.’ I mainly need to exclude plan‑only runs from the default sort.

Benefits

• Quickly surfaces stacks whose resources were recently touched—or whose apply just failed and needs attention.

• Keeps speculative plan noise out of day‑to‑day monitoring and audits.

• Aligns “Updated at” with real‑world impact