Reduced rebranding: internal, non-breaking naming only (CP-17)

[konradmichalik]

Target: v3.0 · Decision record for the reduced rebranding scope

Decision

The original "fully remove xima from everything" programme is reduced to internal, non-breaking changes only. Repository, TER key and Composer package name stay xima….

Explicitly dropped from the original programme:

• CP-18 new composer package name
• CP-19 PHP namespace rename (public event FQCNs would break)
• CP-21 repository transfer
• CP-22 persisted-identifier migration (tables, columns, extension key, config namespace)

Kept as xima… (unchanged, on purpose)

• xima/xima-typo3-content-planner (composer package)
• xima_typo3_content_planner (extension key / TER), incl. all LLL:EXT:… paths and the $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['xima_typo3_content_planner'] config namespace
• Xima\XimaTypo3ContentPlanner\* (PHP namespace, incl. public PSR-14 event FQCNs)
• tx_ximatypo3contentplanner_* tables/columns
• ximatypo3contentplanner_cache cache identifier and the clearCachePostProc hook key

In scope (internal, non-breaking)

• CP-20 (Rename internal JavaScript module specifiers (CP-20) #322) — rename the internal JavaScript module specifiers (@xima/ximatypo3contentplanner/*). Non-breaking; anyone importing them is doing internals work.
• README keeps the XIMA authorship acknowledgement.

Rationale

Since the external identity stays xima…, a breaking rename of the public PHP API (event FQCNs) or a persisted-data migration would create integrator pain and an inconsistent state (package xima, namespace not) for no external-identity gain. Only genuinely internal, non-breaking cosmetics are worth doing.

Acceptance criteria

• No change to public PHP API (FQCNs), persisted schema, extension key or config namespace
• Only internal, non-breaking identifiers changed (see CP-20, Rename internal JavaScript module specifiers (CP-20) #322)
• README acknowledgement of XIMA authorship retained