v0.13.57: @newsroom.writer: who maintains the PHP you run, with the case and the commercial options

Who maintains the PHP you run?, updated at Dinis Cruz's request.

• The proposal first. The article now opens with what it proposes: versions signed off, cryptographically, by the people who maintain the platform, who help support and patch them; buyers who require that signature, so money flows down the chain; maintenance as many small purchases in proportion to each project's spend; and Gen AI scaling the work around the code, not writing it. OpenJS's partner programme is now framed as the best that exists today, not the model to copy.
• The maintainers are the town planners. A new section in the explorer, villager and town planner terms: the people who maintain PHP paid to read, maintain and sign off the code, pushing quality downstream, with links to insurance and a licence to operate (proposed).
• The case, up front. A new early section on the argument from open-source.sgit.ai: smaller, customised, maintained versions of the software, with a direct line between the people who maintain it and the people who use it, and RiskMandate as the company commercialising it, stated as a commercial interest.
• How we are thinking of selling it. A new section with RiskMandate's current options for making money selling open source software (paid to map, paid to engineer, a scoped custom version, retained to maintain, priced by criticality), applied to a PHP site, with a figure. The prices are marked as proposed.
• Wording. "That is the shape I want for PHP" is gone.