reloadSelf() override never calls super.reloadSelf(), so a reload reports success without reloading anything

[wisdommen]

Symptom

/ul reload (or the framework's own reload path) reports that this module's configuration was reloaded, but nothing is re-read: config entities keep their old values, the language catalogue is not re-created, and @ConditionalOnConfig drift is never reported.

Cause

src/main/java/com/ultikits/plugins/mail/UltiMail.java:34 overrides UltiToolsPlugin.reloadSelf() without calling super.reloadSelf():

    public void reloadSelf() {
        getLogger().info(i18n("UltiMail 配置已重载！"));
    }

The framework's reloadSelf() is what performs the reload — getConfigManager().reloadConfigs(this), then re-creating the language catalogue, then ConditionalRegistrationEvaluator.reportDrift(this) — and its javadoc states that an override which skips super loses all of it. This override keeps only the log line, so the success message is printed for work that did not happen.

Fix

Call super.reloadSelf() first, then log. Pin it with a test that fails when the call is removed and passes when it is restored — the same shape as the fixes already merged for the identical defect in UltiKits/UltiLogin#18 and UltiKits/UltiWorlds#16.

Context

One of nine modules with this exact override shape, measured 2026-09-06 across all sixteen module repositories. Tracked together, with a proposal to close the defect class in the framework itself, at UltiKits/UltiTools-Reborn#419. Not part of Phase 13 of the 6.3.0 milestone by maintainer decision (that phase closes the defects the ecosystem acceptance pass found; this one was found by a sweep afterwards).

[wisdommen]

Scope widened as part of UltiTools-Reborn's Phase 16 "Lifecycle hook contract" root-cause group
(D-04), alongside framework issues
#419 and
#455.

Framework-side change now decided: both UltiToolsPlugin.reloadSelf() and
UltiToolsPlugin.unregisterSelf() become final, each gaining a new protected hook —
onReload() and onUnregister() respectively — with an empty default body. onReload() runs
after the framework's own three reload steps (reload configs, recreate language, report
@ConditionalOnConfig drift); onUnregister() runs before the framework unregisters this
module's commands and listeners. The framework itself now logs one INFO line per module on reload,
after its own steps and before onReload() fires.
This module's reload override (reloadSelf(), log-only —
getLogger().info(i18n("UltiMail 配置已重载！"))): the framework's new per-module reload log
line makes this redundant. Delete the override entirely — do not rename it to onReload() —
and remove the lang key if it becomes dead everywhere else in the module.

This module's unregister override, same change (unregisterSelf(), log-only — no functional
cleanup): may be deleted, or moved to onUnregister() only if it should say something the
framework's own unregistration path doesn't.

Milestone 6.3.0, Phase 17 (module-side execution).