Why WOULD he release it at all?
I worked several years within Apple in one core engineering roll, in a sizeable team, and being ethical and moral was a _huge_ part of the engineering culture (at least), both when Steve Jobs was there and after.
As a long time an app developer (mostly Android, but I've seen my iOS coworkers deal with Apple, and I released one somewhat popular Mac app while refusing to get a developer account), I find it very disrespectful how Apple tries its best to forcibly insert itself between the users and the developers and then acts like they totally played an important role in forming that relationship. Then there's the fact that the app store policies ruin the internet as a whole. Because Apple, in its infinite wisdom, not only reviews apps on their technical merits, but if the app is for an online service, it also reviews service itself. They would totally reject a client app for something that they don't like ToS of.
Speaking of the Mac app I made, Apple is making it harder with every macOS release to run apps from "unidentified" developers. No good technical reason for that. No good technical reason for taking away the "all developers" option from the security settings either (I know that it still can be set with a terminal command). A system can be made reasonably secure without the whole security model being centralized around one self-appointed unquestionably trusted party yet Apple chose the centralized approach.
The whole EU DMA thing... I don't even know where to start. This "core technology fee" is absolutely ridiculous. The fact that every binary that is to be "sideloaded" has to go through Apple is also ridiculous. It's pretty clear what the EU regulators meant with this act, yet Apple keeps trying to work around it to keep as much of its rent-seeking as possible. All while acting like a kicked puppy.
Then there's their stance on adversarial interoperability, see Beeper.
Then there's also this whole parts pairing thing on iOS devices. Again, no good technical reason. Maybe it's to prevent stolen iPhones used for parts, but stolen iPhones are still used for parts. I'm a software guy, but for lots more complaints about artificially created hardware-related problems see Louis Rossmann: https://www.youtube.com/@rossmanngroup
At the same time it'll incur a non trivial amount of reputational and professional risk.
For example, schematics of Apple devices would help people fix them on a deeper level than Apple wants (Apple doesn't do board-level repair, one 3-cent component fails and you're getting your entire motherboard replaced). Diagnostic software would help with that too. Documentation about any artificial limitations Apple imposes on these devices for its own profit, like part pairing, would make these limitations easier to bypass. Documentation about software or proprietary network protocols would help with adversarial interoperability. Even documentation on manufacturing techniques might be useful for someone building hardware — if not to copy, then to learn from it.
