ADR-025 — Plugin Rename (obeliOmed Brand Alignment)
Status: Approved | Date: 2026-06-20 | Scope: Three core plugins
Context
Three plugins carried legacy names from the "Oftalmol" era before the obeliOmed brand was established. This created confusion in GitHub, docs, and cross-plugin references.
Decision
Rename the three affected plugins:
| Old name | New name | GitHub repo |
|---|---|---|
| OftalmolBase | ObelioCore | obeliOmed/OftalmolBase (physical rename post-Javi merge) |
| OftalmolAgenda | ObelioScheduling | obeliOmed/OftalmolAgenda (physical rename post-Javi merge) |
| Oftalmol | ObelioOphthalmology | obeliOmed/Oftalmol (physical rename post-Javi merge) |
Table prefix migration (planned, post-merge day):
| Old prefix | New prefix |
|---|---|
oft_patients | obelio_core_patient |
oft_appointments | obelio_scheduling_appointment |
oft_* | obelio_<plugin>_* |
Strategy
Strategy C — leverage in-progress v2 refactors. Rather than a dedicated rename migration that touches all tables at once, each table is renamed incrementally as the corresponding v2 feature is implemented and audited (34b audit). Physical repo rename (GitHub) happens last, after all active PRs in those repos are merged by Javi.
Consequences
- Documentation, ADRs, session logs, and new code use the new names immediately
- Old repo URLs redirect automatically (GitHub handles this on rename)
- No developer workflow breakage since physical rename is coordinated with Javi's merge days
- Legacy table names (
oft_*) remain valid until each plugin's v2 migration lands