chore: update CODEOWNERS [AIS-591]

[Jared Jolton (jjolton-contentful)]

Summary

Updates ownership references to @contentful/group-applied-ai-solutions in CODEOWNERS, catalog-info.yaml, and contributor docs.

Test plan

• CODEOWNERS validation on this PR (automatic)

Summary by Bito

This PR transfers repository and catalog ownership to the applied AI solutions group. It updates both GitHub review ownership and the Backstage component metadata so the two ownership systems remain aligned.

Detailed Changes

• Changes the wildcard ownership rule in CODEOWNERS to route repository reviews to the applied AI solutions group.
• Updates the Backstage component owner in catalog-info.yaml to the matching applied AI solutions group identifier.

[bito-code-review]

Code Review Agent Run #70b86c

Actionable Suggestions - 0

Review Details

• Files reviewed - 2 · Commit Range: 8d62ad7..8d62ad7

  • .github/CODEOWNERS
  • catalog-info.yaml
• Files skipped - 0
• Tools

  • Whispers (Secret Scanner) - ✔︎ Successful
  • Detect-secrets (Secret Scanner) - ✔︎ Successful

---

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

• /review - Manually triggers an incremental AI Review.

• /review full - Manually triggers a full AI Review.

• /pause - Pauses automatic reviews on this pull request.

• /resume - Resumes automatic reviews.

• /resolve - Marks all Bito-posted review comments as resolved.

• /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Default Agent You can customize the agent settings here or contact your Bito workspace admin at jared.jolton@contentful.com.

Documentation & Help

• Customize agent settings
• Review rules
• General documentation
• FAQ

AI Code Review powered by

[bito-code-review]

Changelist by Bito

This pull request implements the following key changes.

Key Change	Files Impacted	Summary
Other Improvements - Update Repository Ownership References	CODEOWNERS, catalog-info.yaml	Reassigns repository code ownership and Backstage component ownership from the developer experience team to the applied AI solutions group.

[bito-code-review]

Functional Validation by Bito

Source	Requirement / Code Area	Status	Notes
AIS-591	Preserve untouched CODEOWNERS lines without introducing whitespace-only changes during the ownership transformation.	✅ Met	The existing CODEOWNERS line is changed in place without whitespace-only churn; the untouched structure and content of .github/CODEOWNERS are preserved.
AIS-591	Migrate CODEOWNERS ownership for all grant-ready repositories that were not already migrated through the taste-test changes.	🟡 Partial	The diff migrates ownership in .github/CODEOWNERS from @contentful/team-developer-experience to @contentful/group-applied-ai-solutions, but the provided diff covers only this repository and does not verify migration for all grant-ready repositories not already covered by taste-test changes.
catalog-info.yaml	Updated the Backstage catalog ownership metadata in catalog-info.yaml from group:team-developer-experience to group:group-applied-ai-solutions, which is not explicitly covered by the CODEOWNERS migration requirements.	⭕ Out of Scope	Updated the Backstage catalog ownership metadata in catalog-info.yaml from group:team-developer-experience to group:group-applied-ai-solutions, which is not explicitly covered by the CODEOWNERS migration requirements.

[bito-code-review]

Impact Analysis by Bito

Interaction Diagram

sequenceDiagram
participant Contributor as Contributor
participant GitHub as GitHub Repository
participant Owners as CODEOWNERS<br/>🔄 Updated | ●●● High
participant Catalog as catalog-info.yaml<br/>🔄 Updated | ●●● High
participant Backstage as Backstage Catalog
participant OldTeam as team-developer-experience
participant NewTeam as group-applied-ai-solutions
Note over Owners, Catalog: Repository governance metadata routes ownership and discovery
Contributor->>GitHub: Open pull request with ownership changes
GitHub->>Owners: Read repository review rules
Owners-->>GitHub: Resolve updated default owner
GitHub->>NewTeam: Request review from group-applied-ai-solutions
NewTeam-->>GitHub: Provide ownership review
GitHub->>Catalog: Read component ownership metadata
Catalog-->>Backstage: Expose updated owner field
Backstage->>NewTeam: Route component ownership and service visibility
NewTeam-->>Backstage: Confirm catalog ownership
Backstage-->>Contributor: Display updated repository ownership
alt [existing ownership references]
GitHub->>OldTeam: Stop default review routing
OldTeam-->>GitHub: No longer selected by CODEOWNERS
else [new ownership references]
GitHub->>NewTeam: Apply new default review routing
NewTeam-->>GitHub: Accept future review requests
    end
GitHub-->>Contributor: Complete pull request ownership workflow

Loading

---

This MR modifies the CODEOWNERS governance layer and the Backstage catalog metadata to transfer repository ownership from team-developer-experience to group-applied-ai-solutions. The change affects review routing and service discovery rather than runtime data transformation, persistence, or external API behavior, and cross-repository searches found no direct consumer behavior changed by these metadata updates.

Cross-Repository Impact Analysis

What Changed	Impact of Change	Suggested Review Actions
The repository-wide GitHub CODEOWNERS team changed from @contentful/team-developer-experience to @contentful/group-applied-ai-solutions.	- No cross-repo consumers found for @contentful/team-developer-experience: The old GitHub team identifier was removed from this repository's CODEOWNERS file. Organization-wide search found no remaining indexed references to the old identifier, so no additional repository configuration was identified as requiring a coordinated update.	- Verify that @contentful/group-applied-ai-solutions is an existing GitHub team with permission to review this repository. - Open a test pull request or use GitHub CODEOWNERS validation to confirm the new team is requested as an owner. - Confirm that any required branch-protection review rules still recognize the new team.
The Backstage catalog owner changed from group:team-developer-experience to group:group-applied-ai-solutions.	- No cross-repo consumers found for group:team-developer-experience: The previous Backstage owner identifier was removed. Organization-wide search for the exact old identifier found no indexed references outside the reviewed change, but the repository metadata consumer itself was unavailable in the dependency graph lookup.	- Confirm that group:group-applied-ai-solutions exists in the Backstage catalog and is resolvable as a group entity. - Run the catalog ingestion or metadata validation check to ensure the component remains indexed. - Verify that ownership-based alerting, catalog views, and escalation workflows route to the intended team.

Code Paths Analyzed

Impact:
This is a repository metadata and ownership transfer only. No production Java source, public SDK behavior, runtime dependency, API endpoint, persistence schema, or build configuration is changed. GitHub review ownership and Backstage component ownership are redirected to group-applied-ai-solutions.

Flow:
GitHub pull request path: .github/CODEOWNERS → GitHub owner/requested-reviewer resolution. Backstage path: catalog-info.yaml spec.owner → catalog ingestion → component ownership and related operational metadata routing.

Direct Changes (Diff Files):
• .github/CODEOWNERS [1] — Replaces the repository-wide CODEOWNERS team from @contentful/team-developer-experience to @contentful/group-applied-ai-solutions.
• catalog-info.yaml [12-15] — Replaces the Backstage component owner from group:team-developer-experience to group:group-applied-ai-solutions.

Repository Impact:
• GitHub pull-request review routing: Future changes matching the wildcard CODEOWNERS rule will request review from the new team.
• Backstage catalog ownership: The component's displayed owner and ownership-driven workflows will resolve to the new group.
• Operational ownership and escalation: Ownership metadata may influence alert routing, service catalog views, ownership reports, and team escalation processes.

Cross-Repository Dependencies:
• Organization-wide GitHub ownership conventions: The new owner group is already referenced in CODEOWNERS files in create-contentful-app, agents-api, and extensibility-api, indicating that the identifier is used as an organization-wide GitHub team name.
• Backstage catalog and ownership services: The catalog-info.yaml owner field is consumed by repository catalog infrastructure, but the exact catalog service repository was not available in the indexed dependency lookup.

Database/Caching Impact:
• None

API Contract Violations:
• No application API or SDK contract is changed.
• Potential metadata contract risk: the new Backstage owner must exist and be resolvable as group:group-applied-ai-solutions.
• Potential GitHub contract risk: the new team must exist and have repository access for CODEOWNERS review requests to work.

Infrastructure Dependencies:
• GitHub CODEOWNERS evaluation and branch-protection review rules.
• Backstage catalog ingestion and group-entity resolution.
• Ownership-based alerting or operational routing associated with the catalog owner.
• No CI workflow, deployment manifest, runtime version, database migration, or application environment variable is modified.

Additional Insights:
• Change scope: The supplied diff contains only two metadata changes and does not require Java compilation or application regression testing.
• Repository dependency graph: The BitoAIArchitect repository lookup could not resolve the repository name contentful-management.java, so a complete incoming/outgoing dependency graph could not be retrieved. Cross-repository conclusions are therefore limited to exact organization-wide search results and confirmed CODEOWNERS examples.

Testing Recommendations

Frontend Impact:
• None.

Service Integration:
• Create or inspect a test pull request and confirm GitHub requests review from @contentful/group-applied-ai-solutions under the wildcard CODEOWNERS rule.
• Run the repository's Backstage catalog validation or ingestion check and confirm catalog-info.yaml remains valid with owner group:group-applied-ai-solutions.
• Verify that ownership-based alerting and catalog ownership views resolve to the new group.

Data Serialization:
• Validate catalog-info.yaml as YAML and confirm the spec.owner value is exactly group:group-applied-ai-solutions.

Privacy Compliance:
• None.

Backward Compatibility:
• Confirm branch-protection rules do not depend on the removed team team-developer-experience.
• Confirm any external ownership dashboards or automation that consume the old owner value are updated or continue to resolve the new group.

OAuth Functionality:
• None

Cross-Service Communication:
• Verify that GitHub team resolution and Backstage group resolution both recognize group-applied-ai-solutions independently; success in one system does not guarantee success in the other.

Reliability Testing:
• None

Additional Insights:
• No Maven, Java, unit, or integration test is required for the changed application code because no application code was modified.
• Perform a manual ownership handoff check with the new team before merge, including review notification and escalation visibility.

_{Analysis based on known dependency patterns and edges. Actual impact may vary.}

[bito-code-review]

✅ Review Settings Overridden

Status: Overridden Successfully

Guidelines:

• Accepted:

  • General : Review Posture, Repo Truth And Alignment, Domain Invariants

Note: Extra guidelines beyond 3 general purpose guidelines and 1 language specific guideline per language are not processed. Guidelines are fetched from the source branch.