AI support copilot Phase 3: content edits on Nova-managed records#3582
Merged
bernardhanna merged 1 commit intoJun 23, 2026
Merged
Conversation
Lets the support copilot make editorial text changes to allowlisted content records through the same dry-run -> APPROVE -> execute -> report pipeline. Records are Nova resources, so a human can also review/tweak them there. Disabled by default (SUPPORT_AI_CONTENT_ENABLED=false). - ContentActionRegistry: allowlist of editable content models (pages, slides, FAQ items, menus, events, podcasts, partners, ...). Page singletons resolve automatically; other records by id or a unique lookup field. - ContentFieldResolver: editable columns resolved at runtime to string/text columns minus a structural deny-list (URLs, slugs, flags, relations, identifiers, SEO/keyword/category) and minus non-string casts. No per-model column list to maintain. - ContentUpdateService: text-only value guards (rejects URLs, www refs, HTML/ markup, over-length), protects Laravel translation-key fields, computes an exact before/after diff for the approval email, and re-validates at execution time rather than trusting the stored payload. - Triage gains the content_update case type (only offered when enabled) plus content_model/content_identifier/content_changes/content_summary. - Wired into diagnostics (before/after preview), approval email (diff), execute job, and completion email; setup-check reports content status; allowed_write_actions includes content_update. - Unit tests for value guards, registry, and pre-DB plan validation; docs. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #3578 (Phase 2). Adds Phase 3: the copilot can make editorial text changes to allowlisted content records (Nova resources) through the same dry-run → APPROVE → execute → report pipeline. Because they're Nova resources, a reviewer can also tweak them by hand. Disabled by default (
SUPPORT_AI_CONTENT_ENABLED=false).ContentActionRegistry): pages, homepage slides, FAQ items, menus, events, podcasts, partners, etc. Page singletons resolve automatically; other records by id or a unique field.ContentFieldResolver): editable columns resolved at runtime to string/text columns minus a structural deny-list (URLs, slugs, flags, relations, identifiers, SEO/keyword/category) and minus non-string casts (bool/array/date/int). No hand-maintained per-model column list.ContentUpdateService): rejects URLs,www.refs, HTML/markup, and over-length; protects Laravel translation-key fields (e.g.hackathons.hero.title).content_updatecase type (only offered when enabled).setup-checkreports content status;allowed_write_actionsincludescontent_update.Review notes
ApproveSupportApprovalaction (dispatches the execute job for any action type, including this one) — no Nova changes needed.Test plan
vendor/bin/phpunit tests/Unit/Support/ContentUpdateServiceTest.php(9 tests) greenSUPPORT_AI_CONTENT_ENABLED=true: a copy-fix ticket triages ascontent_update; dry-run email shows the field-level before→aftercontent_updateis never offered and the service fails safeMade with Cursor