[AndyScherzinger]

The Rector job fails on main and therefore on every pull request branched after it, with a failure that has nothing to do with the changes under review:

[ERROR] Could not process "lib/Activity/SettingCheck.php" file, due to:
        "System error: "Class "Rector\PhpDocParser\PhpDocParser\PhpDocNodeTraverser" not found"
        ... On line: 183
[ERROR] Could not process some files, due to: "Reached system errors count limit of 50, exiting...".

Rector 2.8 removed Rector\PhpDocParser\PhpDocParser\PhpDocNodeTraverser. nextcloud/rector v0.5.2 imports that class in src/Rector/AnnotationToAttributeRector.php and instantiates it on line 183 — the line the error names. Every analysed file fails the same way, the run hits the 50-error limit and the job aborts.

The upgrade arrived as a side effect of an automated dependency bump, 8a6a7cb (chore(dev-deps): Bump nextcloud/ocp package), which re-resolved the whole bin lock: "rector/rector": "^2.7.0" allowed the walk to 2.8.3 and carried phpstan 2.3.4 with it. That is why a pull request branched before it, such as #3203, still passes with rector 2.7.0 while #3199 and #2538 fail.

Holding rector at ~2.7.0 alone does not fix it: phpstan 2.3.4 ships phpdoc-parser 2.4 and hands rector 2.7's scoped parser a FullyQualifiedNameNode it does not know, which fails with CallableTypeNode::__construct(): Argument #1 ($identifier) must be of type IdentifierTypeNode. Both have to move together, so the lock is restored to the set that last passed.

Verified against a clean clone of main at 4150d63, running what CI runs (composer i then composer rector:check):

Set	Result
main as is — rector 2.8.3, phpstan 2.3.4	63 PhpDocNodeTraverser errors, job aborts
rector ~2.7.0, phpstan left at 2.3.4	fails with the CallableTypeNode type error
rector 2.7.0 + phpstan 2.3.2 (this PR)	[OK] Rector is done!

This is a stopgap. The real fix belongs in nextcloud/rector, whose main branch still carries the removed import (last touched 2026-10-14, before rector 2.8 shipped on 2026-10-26). Once there is a release built against rector 2.8 the constraint can be widened again.

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not needed
• 🔙 Backport requests are created or not needed: /backport to stableX.X
• 📅 Milestone is set
• 🌸 PR title is meaningful (if it should be in the changelog: is it meaningful to users?)

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI