We need group the files. Let's analyze. Files: company branding form CSS, JS, service, twig templates, plus a shared button loading JS. The dedicated files all about company branding form. The _button_loading.js might be a small utility change likely used by the form? Need decide if include or separate. Could be independent. Given it's modified and not directly tied? Let's see name: metahuman-standard/components/_button_loading.js, likely a reusable button loading component. It may have been changed to support the branding form's submit button loading state. But no evidence. We can group it with company branding if related, or standalone. Since instructions: semantically related clusters. The company branding files include service, css, js, templates. The _button_loading.js is a component likely used globally; could be separate if unrelated. But maybe changed to accommodate the branding form JS. Let's inspect paths: public/js/metahuman-standard/components/_button_loading.js vs public/js/company_customization/company-branding-form.js. The latter may import the former? It's likely a shared component, but no direct path relation. To be safe, group all together? But "every file must appear in exactly one group". We need decide. If the button loading change is part of a broader shared component update, it might be unrelated. However given the small change and context, probably it's used by the company branding form. But no explicit relation. Let's create two groups: one for company branding feature with the 5 files, one for the button loading component. But if it's a consumer/producer relation, it should be same group. Let's think: The changed files are only 6. The company branding form JS likely has loading state. The button_loading.js may be a utility that the form uses. If the form JS was modified heavily (+326/-14) and button_loading changed slightly, could be part of the same feature to improve loading button behavior. Grouping them together is reasonable if they work together. But the button_loading.js path is under metahuman-standard, a shared library, so it may be changed independently. The task says "Files in the same group typically belong to the same module/feature; have producer/consumer relationships; share same directory". The button_loading.js doesn't share directory, but could be consumer. Without evidence, I'd probably group the company branding files together and put button_loading.js as its own group. But let's examine names: _button_loading.js with leading underscore suggests a partial component/utility. It may be a generic button loading indicator. If the company-branding-form.js uses it, then it is a dependency. The change might be a fix to support multiple buttons or something. Since we don't know, we can rely on semantic relation. Given the change is small and likely needed by the form JS, grouping all together is plausible. Need output JSON array with label and files. Let's choose one group for company branding with all 6? Or two groups. Let's reason from typical code review grouping: If a shared component changes, reviewers of the feature need to see it if it affects the form. But if it's an independent change, separate. The prompt doesn't provide commit message. We have to infer from file names. The company branding form files are strongly related. The button_loading.js is not obviously related. I'd put it separate to be safe, as it belongs to a different module (metahuman-standard). Then the main group has 5 files. That satisfies "Maximum 10 files per group". Let's produce two groups: 1. Company branding form customization: files: - public/css/company_customization/company-branding-form.css - public/js/company_customization/company-branding-form.js - src/Service/CompanyBrandingService.php - templates/company/components/_company_branding_form.html.twig - templates/company/my_company.html.twig 2. Button loading component: - public/js/metahuman-standard/components/_button_loading.js But maybe the my_company.html.twig is about the company page, not necessarily the branding form? It includes the form component. Yes related. Let's output JSON.