[mastacontrola]

#1647 marked these deprecated and said they would go in a later release. FOGProject/fog-plugins#36 is what made that release this one — location and ou each shipped a group tab doing the same push, so removing only the core cards would have left two plugin tabs doing the exact thing the ADR removes. With both converted to HOST_MASSEDIT_*, nothing is left depending on a group-page push.

Seven controls, not the six that carried a notice

The group Active Directory card pushes five hosts columns through Group::setAD() and was missed when the notices were added in #1647. This found it by looking for what writes to members rather than for what was marked.

Removed:

Control	Where it lives now
Image tab + post handler	mass edit image
Active Directory tab + post handler	useAD, ADDomain, ADOU, ADUser, ADPass
Printer Configuration card + printerLevel push	printerLevel
Display Manager card	resolution (row-backed)
Auto Logout card	autologout (row-backed)
Enforce Hostname card	enforce
General tab: kernel, args, init, primary disk, product key, both exit types	the matching mass edit fields

Nothing is lost, and that was checked rather than assumed — mass edit already carries every one of those.

The General tab keeps the group's own fields: name, description, order. Those are not pushed anywhere. Its no-clobber alert goes with the pushes, because there is no longer anything on the form that could clobber.

Power Management stays. It creates tasks rather than copying a value, which is the distinction the whole decision turns on.

One thing worth knowing

groups.groupKernel, groupInit, groupPrimaryDisk and groupBuilding are now written by nothing and read by nothing — a grep finds only the field map itself. They were always write-only: the push went to hosts, never to the group. I've left the columns and their API surface alone here rather than dropping them in the same change.

Proof

The deprecation gates from #1647 are inverted rather than deleted — "the notice is present" and "the control is absent" are statements about the same migration, and the second is the one worth keeping.

Two of the new checks pin over-deletion: groupPowermanagement surviving, and the grant tabs still rendering. A sweep that took too much would otherwise pass as success.

Proven by mutation, each turning it red:

Mutation
Restore the deprecation notice	red
Restore groupImage()	red
Leave a dispatch arm without its handler	red
Let setDisp creep back into groupModulePost()	red
Delete groupPowermanagement (over-deletion)	red
Gut a grant tab (over-deletion)	red
Leave a JS handler bound to an id nothing renders	red

Full suite 300/300, phpstan clean on both configs, phpstan-baseline.neon unchanged — the two dead private methods it flagged were removed rather than baselined.

The group page loses ~1000 lines and its JS ~265.

Depends on FOGProject/fog-plugins#36 (merged).

🤖 Generated with Claude Code

https://claude.ai/code/session_0166dqQEjAs9fhqUw5zCjvxM