[PercolatingStudio]

Final maintenance batch — no release

Process the two dependency proposals generated after the earlier maintenance merges, preserving both bot heads in the ancestry: #374 and #375. Module stays at 3.2.3; no new release/tag or replacement of published assets. #211 is untouched.

• VueQuill 1.2.1 still embeds Quill 1.3.7. The patch avoids duplicate registration of an existing Quill module; CSS/types/public API are unchanged. Allow ~1.2.0 patch updates rather than freezing one patch forever, but continue requiring Quill 1 and holding the incompatible >=1.3,<2 range.
• Vite 8.3.5 is compatible with plugin-vue 6 and the documented Node runtime. Explicitly preserve the previous Chrome87/Edge88/Firefox78/Safari14 build targets in both main and iframe configurations; do not silently adopt Vite 8's newer default browser baseline.
• Add builder regression checks for Vite/plugin/engine lock consistency and both target lists.
• Document intentional review of a compatibility-guard transition.

Validation

• 32 Node tests pass.
• Frozen Yarn, main and iframe builds pass on Node20.20.2. Package/version/manifest/dev-exclusion checks pass in isolated candidate builds.
• Separate branch Build release package workflow_dispatch and final local native/BO tests are being run before integration.

Expected trusted-base guard refusal

The current trusted main-base frontend guard asserts exactly VueQuill 1.2.0. It necessarily refuses both the bot's compatible 1.2.1 update and this candidate's ~1.2.0 constraint before module installation. This is an explicit, reviewed guard transition, not a module failure and not a green check. The replacement guard still enforces 1.2.x + Quill 1 and is reviewed/tested separately. The branch workflow_dispatch executes the actual new builder/test harness against the exact ZIP on PS8 and PS9, without publishing; its successful result is required before merging this maintenance candidate. No branch protection or check result is disabled/rewritten.

[PercolatingStudio]

Final review/validation complete on head e4f13870b8d6c031815a4714f337321eaa3e0c5d.

• Exact candidate builder + PS8/PS9 ZIP installation: SUCCESS. This runs the new 1.2.x/Quill1 guard, Vite target guards, and all packaged PHP file/date/cache/SCSS regressions. Publication is correctly skipped.
• 32 local Node tests and frozen main/iframe builds pass. The local ZIP passed fresh native installations; the final follow-up commit changes only test-stack cache ownership/documentation, excluded from the ZIP. The retained-stack path was rerun successfully and no non-www-data-owned cache entries remain.
• Both authenticated BOs on the Vite8/Quill1.2.1 bundle preserve bold/bullet lists and #123456 after save/reload. Popup sizing/stacking/closing remains correct. Both calendar controls retain the selected day, Monday start and explicit empty value through save/reload. PS8 has no JS errors; PS9 only has the previously known Symfony debug-toolbar 404s.

The trusted-base PR check remains a real failed check: main's old guard insists on the exact string 1.2.0 and rejects the reviewed ~1.2.0 constraint. Its earlier equivalent report was inspected and fails precisely on that assertion, before installation. No check/protection is disabled or rewritten. The separately reviewed replacement still rejects Quill2, and the successful exact-candidate workflow above supplies the actual new-harness installation evidence.

No module version bump, release/tag creation or release-asset replacement.