task: #3620192 Remove the canvas_override install and requirement, as we moved it to the Varbase Canvas Base recipe

#3620192

What this does

Removes two lines, and nothing else:

• canvas_override out of the install: list in recipe.yml.
• "drupal/canvas_override": "1.0.x-dev" out of require in composer.json.

Both now live in Varbase Canvas Base (#3620177, merged, 1.0.x-dev released and packaged).

What this deliberately does NOT do

Every Drupal Canvas permission grant stays in this recipe — all 17 of them, across content_editor, content_admin, seo_admin and site_admin: create / edit / delete canvas_page, publish auto-saves, administer folders, administer patterns, administer components, administer content templates, administer page template, edit canvas global regions.

A Canvas page is content and these are content roles, so the grants belong with the roles. More concretely: Educare, Horizon Aid and RightUp apply this recipe directly, not through Varbase Starter, and they do not require Varbase Canvas Base. Each carries 58-80 canvas.component / canvas.content_template config keys. An earlier revision of #3620177 did move the grants out, and it was reverted precisely because it would have stripped those three products' editor permissions.

Ordering — read before merging

Land the Varbase Starter change (Starter applying varbase_canvas_base) first, or both together. If this merges alone, a fresh Varbase Starter build installs no canvas_override at all until Starter catches up.

Testing

Fresh drush site:install varbase on a clean Varbase 11 DDEV build, with this change plus the pending Varbase Starter change overlaid. After install:

• canvas and canvas_override both enabled — canvas_override now via varbase_canvas_base, applied by Starter.
• content_editor, content_admin and site_admin carry exactly the same Canvas permission list as a stock build, granted by this recipe as before.

drupal/varbase_canvas_base:1.0.x-dev confirmed resolvable by Composer at the merged 8c36612.

Not done: no browser testing of the Canvas editor itself, and no upgrade-path test on an existing site — this only changes which recipe declares the module, not any configuration.

AI-Generated: Yes

Checkpoints

• File an issue
• Addition / Change / Update / Fix
• Automated unit testing coverage
• Automated functional testing coverage
• Testing to ensure no regression
• UX/UI designer responsibilities
• Readability
• Accessibility
• Performance
• Security
• Developer Documentation
• User Guide Documentation
• Reviewed by a human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Release notes snippet
• Release