Availability was the decision, not a footnote

This week's verified coverage repeatedly split a large announcement into parts at different release stages. Google Cloud's Gemini Robotics ER 2 is a public preview, while GitHub's Agentic Workflows are generally available. SAP began a phased Joule Studio rollout but placed its Enterprise AI Gateway in the first quarter of 2027. IBM similarly separated generally available agent-identity controls from preview discovery and containment functions.

Cloudflare's Private Origins announcement created a sharper conflict: the company called the feature generally available while its public documentation still labeled it a closed beta. The practical lesson is to confirm the control in the account, the plan requirement and the regional or endpoint scope before making a new capability a production dependency.

Security and infrastructure changes required operational work

AWS's Brotli bulletin showed why a vendor fix is not always the end of the task. Supported Lambda runtimes receive staged updates, but teams using containers, layers or bundled libraries may need to rebuild and redeploy. Mistral Large 4 added another form of operating constraint: downloadable weights do not erase the separate license condition for some model-hosting services.

Together, those stories favor a short change record that captures the affected runtime, required action, rollout date and evidence of completion. The same record should include the license or commercial condition when a model moves from an API evaluation to self-hosting or a customer-facing service.

Acquisitions and product scope still leave integration questions

Salesforce's agreement to buy Rune Technologies could extend Missionforce into logistics designed for unreliable connections. The transaction is not closed, and the issuers did not publish combined-product pricing, a technical integration schedule or a customer-migration plan. That makes the announcement useful for roadmap questions, not evidence of a purchasable integrated product.

CGH perspective: for each proposed change, record whether it is available, who can use it, what it costs, what must be rebuilt and what remains an issuer claim. This digest synthesizes selected CGH stories verified live during ISO week 2026-W44; it is not exhaustive, and CGH has not independently tested the products.