fix(suggested-fix-pending): apply PR #156 review fixes

- Page-level Resolve patches applied_pending → applied_success before
  opening the resolution flow, so resolved sessions don't carry a
  provisional pending fix.
- Page-level Escalate intercept now catches applied_pending in addition
  to verifying/partial; intercept copy generalized from "Verifying state"
  to "still needs an outcome."
- PendingBanner gains a Dismiss action, matching the PR body and the
  backend's allowed pending → dismissed transition.
- resolution_note_generator and escalation_package_generator system
  prompts no longer include real-looking pending examples (anti-parrot
  guardrail compliance).

Verified via Docker: prompt anti-parrot 2/2, suggested-fix outcome suite
21/21, frontend tsc -b clean, npm run build clean.

Co-Authored-By: Codex <noreply@openai.com>

backend/app/services/resolution_note_generator.py

@@ -84,7 +84,7 @@ that actual resolution, not just the failed attempt.
 - applied_partial: Note that the fix was partially applied. If partial_notes \
 are provided, include them. Then describe the final resolution path taken.
 - applied_pending: Note that the fix was applied and verification is pending. \
-If pending_reason is provided, include it (e.g. "awaiting client power-cycle"). \
+If pending_reason is provided, include it as the provided waiting reason. \
 Frame the resolution as provisional — the fix is in place but not yet \
 confirmed. Do not write closure language.
 - dismissed: Treat the fix as considered and set aside. Do not center the note \