IONOS(activity): NC32 fork release (NSW-946)

[printminion-co]

Summary

NC32 IONOS activity line: upstream v32.0.14 + rebased IONOS patches.

• Integration branch ionos-dev-v32 = vanilla v32.0.14.
• This PR adds the IONOS commits on top.

Reconciliation against v32.0.14

IONOS commit	Outcome
ca3cd2e IONOS(admin-settings): convert to delegated setting	kept — upstream still declares implements ISettings at v32.0.14, so the delegation patch is not redundant

The cherry-pick applied cleanly. #[\Override] was added to the two new IDelegatedSettings methods to match the attributes NC32 introduced on the other methods in this class.

Commit hashes are unformatted so GitHub auto-links them.

Consumed by IONOS-Productivity/ncw-server via a submodule bump after merge + tag.

Jira: NSW-946

[printminion-co]

The two Cypress failures (runner 1, runner 2) are base failures, not introduced by this PR.

Verified with a control PR — #3 — containing bare upstream v32.0.14 and zero file changes.
It fails the same two jobs with the same counts:

	runner 1	runner 2
#2 (with IONOS delta)	fail	fail
#3 (bare v32.0.14)	fail	fail

The delta here touches only lib/Settings/Admin.php; the failing spec (cypress/e2e/settings.cy.ts)
exercises the user notification page at /settings/user/notifications, rendered by
lib/Settings/Personal.php — a class this PR does not touch.

Per the fork-upgrade guide, a red check whose cause is unchanged from the vanilla base is not fixed
in the delta. Control PR now closed.

[printminion-co]

Why most checks are stuck queued

These are not failures and they will not clear on their own.

These forks inherit the upstream Nextcloud workflows, most of which pin runs-on: ubuntu-latest-low
— a runner label that exists in the nextcloud org but not in IONOS-Productivity
(repos/.../actions/runners reports 0). Those jobs queue indefinitely; only the ubuntu-latest
ones ever execute.

Fork	ubuntu-latest-low	ubuntu-latest
nc-activity	30	22
nc-bruteforcesettings	32	17
nc-password_policy	26	16

This is pre-existing, not caused by these PRs: nc-bruteforcesettings has never had a successful
PHPUnit run in its history — the single attempt, on kh/dev/delegate-admin-settings in Feb 2026
(the branch that produced the very commit cherry-picked here), was cancelled. Worth its own ticket;
out of scope here.

Judge these PRs on the checks that can run. Psalm is among them, and it is the check that would
catch a broken IDelegatedSettings implementation.

On this PR the runnable checks are: static-psalm-analysis ✅, php-cs ✅, stylelint ✅,
init ✅. The only red is Cypress runner 1/runner 2, already established above as a base
failure via control PR #3.

[printminion-co]

Upstreaming of this patch is now in flight — see #4 (internal review) and nextcloud#2885 (upstream). Tracked in Jira as NSW-808, parked in the "Waiting for NC/Collabora" sprint.

This PR still needs to merge as-is: the fork keeps carrying the patch on the NC32 line until Nextcloud merges and releases the upstream change. Server PR: IONOS-Productivity/ncw-server#324.