Composer patch for Drupal Canvas breaks dependent project installs (relative path)
## Problem/Motivation
`composer.json` declares a dependency patch for Drupal Canvas with a **relative** path:
```json
"patches": {
"drupal/canvas": {
"3575644 - Skip StringLongItemOverride regex for ai_context_item": "patches/canvas-3575644-string-long-regex-ai-context-item.patch"
}
}
```
`cweagans/composer-patches` resolves relative paths against the **consuming project's root**, not the module directory, so every fresh install of a project depending on AI Context aborts:
```
The "patches/canvas-3575644-string-long-regex-ai-context-item.patch" file could not be downloaded:
Failed to open stream: No such file or directory
```
Projects that never opt in to the patch fail too — allow-lists filter after the resolver has already tried to fetch the file. Patch source: [Drupal Canvas #3575644](https://www.drupal.org/project/canvas/issues/3575644).
## Steps to reproduce
1. `composer require drupal/ai_context` in any Composer-managed Drupal project.
2. Install fails while "Resolving patches from dependencies", before any package installs.
## Proposed resolution
Two options — one of the two to merge, maintainer's call:
- **Option 1 — !221:** reference the patch by an absolute, publicly fetchable URL (`https://git.drupalcode.org/project/ai_context/-/raw/1.0.x/patches/…`). The patch keeps shipping with the module.
- **Option 2 — !222:** remove the patch declaration and the `patches/` file from the package. Consumers that need the Canvas workaround manage it in their own patch set.
## Remaining tasks
- [x] Addition/Change/Update/Fix to this project
- [ ] Testing to ensure no regression
- [x] Reviewed by a human
- [ ] Code review by maintainers
## User interface changes
None.
## API changes
None.
## Data model changes
None.
## Release notes snippet
Fixed the Drupal Canvas dependency patch declaration in `composer.json` so projects depending on AI Context can install.
issue