fix: #3611841 Remove format property from ai_context_item content

Rajab Natshahrequested to merge
issue/varbase_ai_context-3611841:3611841-fix-varbase-ai into 1.0.x

Summary

drupal/ai_context 1.0.0-beta3 (released 2026-07-18) changed the ai_context_item base fields description, purpose and content from text_long to string_long. string_long only exposes a value property, no format, so the recipe's content import fails with "Property format is unknown." and the three starter context items are never created. Project Browser's activate endpoint returns HTTP 200 while carrying that error in its AJAX payload, so the failure is easy to miss.

This MR removes the now-invalid format: plain_text line (9 lines total) from the description, purpose and content fields of the three ai_context_item content files. No other change.

Issue: https://www.drupal.org/project/varbase_ai_context/issues/3611841

Verification

Reproduced and fixed on a live Varbase 11 site (Drupal core 11.4.4, drupal/ai_context 1.0.0-beta3). Before the fix: drush recipe / Project Browser activation reported 0 context items plus the "Property format is unknown." error. After applying this fix and running drush recipe:

Created content for Varbase AI Context recipe.
[OK] Varbase AI Context applied successfully

and the three items exist afterwards:

3 items: Varbase AI Editorial Rules ; Varbase AI Safety Guardrails ; Varbase Brand & Identity Guidelines

Open question for the maintainer (not addressed in this MR)

composer.json currently requires drupal/ai_context: ~1.0, which still allows pre-beta3 versions where these fields were text_long. After this fix the recipe only works correctly on beta3+. Worth deciding whether to tighten that constraint in a follow-up.

AI disclosure

AI-Generated: Yes (Used Claude Code to identify the root cause — the ai_context 1.0.0-beta3 field-type change — and remove the 9 now-invalid format: plain_text lines; verified by running the recipe on a live site.)

Checkpoints

  • File an issue about this project
  • Addition/Change/Update/Fix to this project
  • Testing to ensure no regression
  • Automated unit/functional testing coverage
  • Developer Documentation support on feature change/addition
  • User Guide Documentation support on feature change/addition
  • UX/UI designer responsibilities
  • Accessibility and Readability
  • Reviewed by a human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Update Release Notes
  • Release
Edited by Rajab Natshah

Merge request reports