I havent seen further public discussion either. Does that presume the answer is - no they are not finalized?
I'm interested to know who/how the decision is to be made?
That said, and assuming discussion is still open -
If I understand that one aim is to limit the use of project boxes, I think the proposed limit of 2 boxes should be changed to a limit of one project box - namely the particular project under which a profile is protected (if it is protected), with any other project associations identified by Category links. Perhaps also project boxes would not be utilized on profiles until profile protection is granted, and the box would be added by the project itself.
I don't think ONS should be limited or restricted - but if the move is to reduce project box clutter, a uniform policy that does not single out any projects by name seems most sensible - reserving project boxes for protected profiles, or changing the way the profile protection box works such that the protecting project is identified there (much as a template has options, the protection box presumably could have options selected when applied?)
Happy to hear thoughts on this either +/-