[Education] Normalize adapter naming metadata#7
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the adapter map configuration files for both antigravity and codex platforms by adding a canonical route and introducing a new naming block with normalized metadata. The review feedback points out significant redundancy between the newly added naming block and the existing app block, which could lead to configuration drift, and suggests consolidating these blocks or deprecating the redundant fields.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| "naming": { | ||
| "policy": "securedme.education.name-pattern.v1", | ||
| "suite": "SecuredMe Education", | ||
| "canonical_slug": "ffed-qlc", | ||
| "display_name": "FfeD-QLC", | ||
| "repository_name": "FfeD-QLC-MVP", | ||
| "repository_full_name": "SeCuReDmE-main-dev/FfeD-QLC-MVP", | ||
| "adapter_prefix": "securedme-ffed-qlc", | ||
| "codex_adapter": "securedme-ffed-qlc-codex-adapter", | ||
| "antigravity_adapter": "securedme-ffed-qlc-antigravity-adapter", | ||
| "public_route": "https://securedme.ca/education/apps/ffed-qlc/", | ||
| "canonical_domain": "ffed-qlc.securedme.ca", | ||
| "legacy_or_internal_names": [ | ||
| "FfeD-QLC-MVP" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
The newly added naming block introduces significant redundancy with the existing app block:
canonical_slug(line 15) duplicatesslug(line 5)display_name(line 16) duplicatesname(line 6)repository_name(line 17) duplicatespath(line 7)public_route(line 22) duplicatescanonical_route(line 9)canonical_domain(line 23) duplicatescanonical_domain(line 8)
This duplication increases the risk of configuration drift. If the schema allows, consider consolidating these blocks or deprecating the redundant fields in the app block to maintain a single source of truth.
| "naming": { | ||
| "policy": "securedme.education.name-pattern.v1", | ||
| "suite": "SecuredMe Education", | ||
| "canonical_slug": "ffed-qlc", | ||
| "display_name": "FfeD-QLC", | ||
| "repository_name": "FfeD-QLC-MVP", | ||
| "repository_full_name": "SeCuReDmE-main-dev/FfeD-QLC-MVP", | ||
| "adapter_prefix": "securedme-ffed-qlc", | ||
| "codex_adapter": "securedme-ffed-qlc-codex-adapter", | ||
| "antigravity_adapter": "securedme-ffed-qlc-antigravity-adapter", | ||
| "public_route": "https://securedme.ca/education/apps/ffed-qlc/", | ||
| "canonical_domain": "ffed-qlc.securedme.ca", | ||
| "legacy_or_internal_names": [ | ||
| "FfeD-QLC-MVP" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
The newly added naming block introduces significant redundancy with the existing app block:
canonical_slug(line 15) duplicatesslug(line 5)display_name(line 16) duplicatesname(line 6)repository_name(line 17) duplicatespath(line 7)public_route(line 22) duplicatescanonical_route(line 9)canonical_domain(line 23) duplicatescanonical_domain(line 8)
This duplication increases the risk of configuration drift. If the schema allows, consider consolidating these blocks or deprecating the redundant fields in the app block to maintain a single source of truth.
Summary
namingblock with the name-pattern policy, canonical slug, display name, repository name, public route, canonical domain, and legacy alias.Validation
Notes
This is metadata-only. It does not rename the repository or change runtime code.