Not sure if I should cry or laugh 🤣

This should never have been possible and must be fixed. Tethered nodes are considered an integral part of their parent and thus must not be disabled separately

Many people disagree with you (and me) - see discussion in the linked ticket

I'm referring to 9.0 where it was decided this way iirc

Okay a compromise would be to implement the suggested configuration from neos/neos-ui#3004

'Some.Package:Some.NodeType':
  childNodes:
    'childnode1':
      type: 'Some.Package:Some.NodeType'
      hideable: true

and depending on this hideable option allow - on a cr level - to hide a tethered node.

Buuut we should rather call it canBeDisabled or the like to fit the disabled naming.

I think if this turns into a discussion we should by all means merge it with the other thread

okay yes makes sense not to split it up to heavily ;)

As discussed here neos/neos-ui#3004 (comment) we want to implement constraint checks in neos 9 to disallow this for once and for all.

@nezaniel and me discussed how this change will be affected by the introduction of the subtree tags feature. As disabled is just a tag itself. We came to the conclusion that the argumentation, that a tree should never be invalid, despite which exclusion is configured via the VisibiltiyConstraints and that will include any custom tag.

So it will NOT be possible to tag a tethered node blog with a blog tag for example.

(Additionally we discussed that we have to prevent DisableNodeAggregate but also EnableNodeAggregate.)