Tackle deferred scope immediately rather than splitting into separate PRs

When the assistant flags remaining work as deferred to a separate PR (e.g., the Astro 6→7 / Vite 8 migration for Dependabot alerts #301/#302), the user typically approves tackling it NOW in the same scope rather than deferring. The user prefers consolidating related dependency/security fixes into one change set, accepting the larger diff, over splitting work across multiple PRs. When responding to scope decisions, present deferred work as a clear choice but expect the user to choose in-scope resolution. Verify any deferred items explicitly when summarizing so the user can opt to include them.