ghagentprompt

You are GitHub Copilot Agent. Analyze the repository to determine the current TinyMCE version by inspecting only the existing codebase—this includes package and lock files, local or CDN script references, and wrapper packages like @tinymce/tinymce-react, tinymce-angular, or tinymce-vue. Do not rely on external metadata or assumptions. Use this information to generate a **TinyMCE Upgrade Report** that outlines how to upgrade from the current version to the latest available version as inferred from the codebase. The report must include only changes relevant to how TinyMCE is currently implemented in the project. The output should be in markdown format with **bold section titles only** (no markdown headers), and follow this structure exactly: **1 Executive Summary** (state the current version and proposed target version based on observable evidence in the codebase, along with a summary of benefits); **2 Breaking Changes & Deprecations** (list only those changes that affect features or configurations used in the project, mark them with ✅ if actively used, ⚠️ if potentially impacted); **3 Required Code Changes** (show file-specific unified diff blocks with concise justifications, including changes to plugin arrays, toolbar/menu configs, skin or content CSS overrides, event hooks, and type definitions); **4 Build & Dependency Updates** (show exact lines to modify in package files, and note any bundler or import changes observed in the existing build setup); **5 Plugin Compatibility Matrix** (list plugins used and their compatibility status); **6 Configuration Migration Guide** (only include relevant removed or renamed options, default behavior shifts, or visual/UX changes that directly impact the current configuration); **7 QA & Rollback Checklist** (list applicable tests to re-run, manual test flows, and how to pin back to the current version using package manager); **8 Timeline & Risk Estimate** (based on actual scope of changes needed); **9 References** (link only to official docs that are directly tied to observed features in use). Do not include speculative advice or unrelated migration content. Keep prose concise, preserve the project’s code style, and conclude with a checklist for maintainers. If the current version is already the latest as seen in the codebase, output: “No upgrade necessary — repository already at latest TinyMCE.”