hot events · 2026-06-08

Anthropic is making the right platform bet here: Claude is not chasing another chat surface, it is entering Apple’s developer framework. The concrete hook is unusually clean: a Swift package, three lines of code, typed Swift values, and support for multi-step reasoning, code generation, web search, and data analysis across iOS 27 and macOS 27. For an Apple developer, that feels closer to native plumbing than a separate REST client. I don’t buy the implied jump from “easy to call” to “developers will default to Claude.” The article gives no pricing, latency, model-selection rules, or cloud-versus-on-device handoff behavior. It also does not say where Claude ranks against Apple’s own Foundation Models inside the framework. Anthropic gains distribution surface here, not default status.

Apple’s move is practical: use Apple Intelligence to patch Safari’s extension gap instead of chasing OpenAI in chat. The concrete demo matters: a user asks to “save and track cooking recipes,” and Safari generates a Recipe Keeper extension with a toolbar button, saved recipes, and notes. Safari has trailed Chrome for years partly because its extension library is thin, and Apple’s development requirements raise the floor for casual builders. I read this as Apple’s low-code extension store test, but the missing constraints are the story. Timing, OS version, sandbox rules, and sharing limits are not disclosed. Chrome’s extension problem was never just writing JavaScript; it was permissions, updates, malicious add-ons, and review. If Apple keeps this local-only, it becomes personal automation. If Apple lets users distribute these, Safari inherits a security and moderation bill fast.

Apple announced at WWDC that devs with under 2 million first-time App Store downloads get free access to its Foundation Models running on Private Cloud Compute. Both TechCrunch and HN are running the same TechCrunch piece — no second independent source — so what we know is limited to what Apple said on stage. The 2-million-download threshold is generous. Apple's Small Business Program uses a $1M annual revenue cutoff; this download-based bar casts a much wider net. The pitch is straightforward: infrastructure costs shouldn't block experimentation, and with cloud API pricing being what it is right now, that's a real friction point for indie devs. I'd hold off before calling this a big deal, though. Apple didn't disclose rate limits, token caps, or any usage ceiling — "free" could mean a lot of things. And "frontier-tier" is a hand-wave without benchmarks or model card details. If actual quotas and latency numbers surface from early users, that's when this gets interesting.

Both items come from r/LocalLLaMA and point to the same event: llama.cpp merged Gemma4 MTP support. The article body is blocked by Reddit 403, so PR details, tested model sizes, and speed numbers are absent. My read: useful plumbing for local AI people, but not evidence that Gemma4 is now fast on-device. MTP only turns into real tokens/sec when sampling, KV-cache handling, and backend kernels line up inside llama.cpp. We saw the same gap around DeepSeek V3/R1 MTP chatter: a training-time feature entering a runtime often hits implementation drag first. The hard fact here is “support merged,” not “performance delivered.”

WWDC 2026 put Siri's AI overhaul front and center, and both TechCrunch and Bloomberg covered it from the same keynote feed. Their accounts align because they're drawing from Apple's own presentation — no independent benchmarks, no third-party testing. TechCrunch went feature-by-feature on Siri's new use cases and iOS 27 integrations; Bloomberg's piece, from what I can see, is more of a takeaways format. The real question isn't what features Apple announced — it's whose models are powering them. Apple has historically pushed on-device processing and privacy, but if the rumors about Google tech under the hood are true, that's a shift toward external partnerships for generative capabilities. Neither article confirms the tech supplier, and there's no word on model specs, latency, or what happens offline. More gaps than answers right now — don't read this as Apple's AI comeback just yet.

Apple using Google technology in its revamped AI platform is not the scandal. The weak spot is Apple asking users to accept a privacy claim without the machinery. The snippet says Apple preserves privacy safeguards, but gives no model name, no on-device versus cloud split, no audit path, and no data-retention terms. That sits awkwardly beside Apple’s earlier Private Cloud Compute pitch. PCC at least came with claims about hardware isolation, non-persistence, and researcher verification. Here, “Google technology” does all the work and explains none of the boundary conditions. For AI teams, the question is not whether Apple used Gemini. It is who sees the prompt, where logs live, and what Google can learn. Without those details, Apple Intelligence inherits Google’s capability and Apple’s trust gap.

Apple published the Core AI framework docs on its developer site, marked Beta. Both sources point to the same official page, so there's no factual dispute — but the information is thin. What's visible is a Swift API skeleton: symbols for model loading, inference, debugging, and profiling, plus an AssetError type. I'd read this as Apple laying the developer-facing groundwork for on-device AI, not a ready-to-use product. The gaps are big: no supported model list, no context window specs, no clarity on whether inference is fully local or hybrid cloud. If WWDC sessions or sample code drop in the coming weeks, this line gets a lot more concrete. For now, treat it as early infrastructure docs.

Apple dropped two AI features into Photos at WWDC 2026: Reframe lets you shift the perspective of a shot after the fact, and Extend pulls the frame outward to add breathing room. Both outlets are working from the same official announcement, so the feature descriptions match. The split is in tone. TechCrunch gives you the how-to — drag to adjust, real-time preview, generative fill only for the gaps created by the perspective shift. The Verge skips the manual and goes straight to the philosophical point: Apple is now selling the idea that a photo isn't a record, it's raw material you can re-shoot later. That's the sharper take. My hesitation: Apple says it only generates content to fill perspective gaps, not to invent new elements, but we don't know where that line actually gets drawn until someone tests it. Also, neither outlet mentions whether this runs on-device or which models are required — that's the detail I'd wait for before judging how well it works in practice.

Apple pins Siri AI’s EU absence from iOS 27 and iPadOS 27 on the DMA, and I don’t buy the framing yet. The usable facts are thin: title, June 8, 2026 publication date, iOS 27, iPadOS 27. No EU launch date is given, and no DMA article or obligation is named. For AI teams, the missing mechanism is the story. If the blocker is interoperability, default service choice, or data access, Apple should say which layer breaks: on-device models, Private Cloud Compute, or third-party extensions. Apple used a similar DMA explanation when Apple Intelligence was delayed in the EU in 2024. Without a clause number or feature list, this smells like turning a Siri execution delay into a Brussels problem.

This piece clicks because it connects a few scattered observations into one clean thesis: models got better mainly by eating more and better data, not by learning more efficiently. Dwarkesh reframes RL as a synthetic data pipeline—spend compute to find good rollouts, then train the model to predict them, same logic as next-token prediction in pretraining. Two numbers make the gap concrete: a human sees ~200M tokens by adulthood; frontier models train on tens to hundreds of trillions—a million-fold difference. Learning to teleoperate a robot takes a person hours; self-driving models need 3–4 orders of magnitude more data than a teen learning to drive. He offers an explanation I buy: open models lag closed ones by only 4 months because data is easy to distill from public APIs, while architecture tricks and training recipes aren't. If algorithmic efficiency were the main driver, that gap would be wider. The post doesn't propose a fix—it ends on the "data black hole" metaphor. I'd read it as a diagnosis, not a roadmap.

Apple dropped its next-gen AI platform and a new Siri at WWDC, and Bloomberg ran two headlines both calling the investor reaction "lukewarm" or "tepid." Same outlet, same angle — this isn't editorial disagreement, it's what the room actually felt like. I'd discount this a bit for now: we've only got Bloomberg's read, no official specs from Apple, no third-party benchmarks, no hands-on impressions. But the flat stock reaction is still a signal. Apple has been promising and delaying AI features for over a year now — the Siri overhaul already missed one deadline. Investors are clearly in "show me the product, not the slide deck" mode. If more outlets drop technical details later, I'm watching two things: whether the new Siri runs on-device or in the cloud, and whether it can actually take actions across apps. Those two factors decide if this thing sells phones.

ChatGPT is shaving workflow friction here, not showing a model jump. The concrete move is simple: data and comparisons can become charts inside ChatGPT, and OpenAI says it works on mobile and web. That pushes ChatGPT further toward a disposable analysis surface, not just a chat box. The missing pieces matter. The post says nothing about CSV, Excel, image tables, editable chart specs, or SVG/PPT export. It also does not say whether mobile has the same controls as web. Claude Artifacts and Gemini’s Workspace push already showed the pattern: chart creation is easy; surviving the handoff into documents is the hard part. Without edit and export details, this reads more like a polished presentation layer than a real Sheets or Excel replacement.

LEVI is exactly the kind of LocalLLaMA result that gets over-read. The summary says Qwen3-30B-A3B runs an AlphaEvolve-like search loop, with up to 35x lower cost and up to 12x fewer evals under the same-model, same-budget setup. The Reddit body is blocked by 403, so the search policy, sampling count, eval scripts, and hardware pricing are not visible. I’d treat this as a useful hint about open models plus eval-budget control, not a local replacement for Google AlphaEvolve. ADRS, IFBench, and HotpotQA can show search efficiency. They do not cover long-horizon code evolution, tool failures, rollback, or messy production objectives. The claim needs a repo, seeds, and a cost table before it earns the headline.

NotebookLM’s upgrade reads like a paid-tier stress test, not a broad product launch. The disclosed pieces are agentic behavior inside chat, advanced reasoning, and multiple output formats; the post only says Google AI Ultra gets it, with no formats, pricing, or rollout schedule. For practitioners, that gap matters: whether the agent can plan across sources, preserve citations, and produce editable artifacts decides whether this is a research workflow tool or just a better summarizer. I care more that Google put this in NotebookLM than in the main Gemini surface. Perplexity made research feel like search; OpenAI put Deep Research inside ChatGPT. Google is leaning into source-bound notebooks and citation trails, which fits enterprise knowledge work. The Ultra gate also says Google still treats long reasoning as a cost center, not a default feature.

NotebookLM’s sharp move is putting Google Search before the RAG workflow, not just swapping in Gemini 3.5. The old constraint was user-supplied material: notes, PDFs, YouTube links. Now a user can ask about a topic, let NotebookLM find sources with Search, then interrogate the resulting corpus. That changes the product from “chat with my files” to “build my file set first.” I’m holding judgment on the “cloud computer” claim. The RSS snippet only names it in the title; it does not disclose whether this means a browser, filesystem, code execution, or hosted task runtime. Google’s leverage here is less a flashy agent demo and more the coupling of Search, Workspace, and Gemini inside one research loop. Perplexity owns answer pages; NotebookLM is aiming at traceable source packs.

Runway is aiming Aleph 2.0 at the part of video AI that actually gets budget: format adaptation for the same asset. The disclosed workflow is concrete: upload a video in the desktop web app, choose an aspect ratio, and Aleph 2.0 fills the missing scene area. Pricing, resolution limits, clip length, latency, and failure rate are not given, so don’t treat this as a general video editor yet. I buy this lane more than another text-to-video showcase. Ad teams need 16:9, 9:16, and square cuts every day; the pain is rework, not making another cinematic sample. Adobe has been pushing generative extend inside Premiere, while Runway is keeping the workflow in its own web app. That tells you where the fight sits: the default surface for production teams, not model leaderboard theater.

Luce Spark’s sharp move is moving local MoE inference from a memory problem to a routing-hit problem. Qwen3.6 35B-A3B peaks at 13.3GiB on an RTX 3090 at ctx 4096, while Laguna XS.2 33B-A3B lands at 14.6GiB. The mechanism is plain but effective: keep hot experts on GPU, swap cold experts through an async cache, and cut cold-hit rate from 36% to about 7% versus uniform placement. I would discount the headline once. The author says it has not run on an actual 16GB card like a 4060 Ti 16GB, and there is no same-settings fight against llama.cpp --n-cpu-moe. The 100 tok/s figure is on a 3090, around 85% of all-GPU. That is very good engineering, not proof that every 16GB consumer GPU now owns 35B MoE.

Hivemind has the right target: coding agents don’t need another chat shell as much as shared memory from actual Claude Code, Codex, Cursor, Hermes, and Pi runs. SkillOpt’s numbers are aggressive: Claude Code gains 19.1 points, Codex gains 24.8 points, and it matches or leads across all 52 test settings. I’d discount the benchmark until the split is clear. Continuous learning for code agents easily freezes repo quirks, bad repair paths, and test-gaming into “skills.” User-owned cloud storage, open source, and one-command install all help adoption. The hard proof is cross-repo transfer, cold-start tasks, and teams that did not generate the traces. Without that, 52/52 reads like a clean demo loop, not production evidence.

OpenEnv reads like a bid to become the default substrate for agent training, not evidence of a finished stack. The title names 9 initial members, including Hugging Face, Meta-PyTorch, Unsloth, Modal, Prime Intellect, Nvidia, and Mercor. The described scope is execution environments such as terminals and browsers. The body gives no API, version, license, benchmark, or voting rules; the fetched Reddit page is only a 403 block. The member mix is the signal. PyTorch touches training, Modal touches execution, Mercor has task and human-data pipes, and Prime Intellect has been pushing distributed training. That covers the map. It still does not solve the ugly part: reproducible agent environments. After SWE-bench, everyone learned the model score is only half the story; environment drift and task packaging can poison the result.

VoxCPM2’s punch is not the TTS demo quality; it is the packaging of scale plus licensing. A 2B-parameter model, 2M+ hours of multilingual speech, 30 languages, 9 Chinese dialects, Apache 2.0 weights, fine-tuning code, and inference tools hit the exact checklist buyers use for private speech stacks. I don’t fully buy the “SOTA or highly competitive” line yet; the snippet gives no benchmark table or human-eval protocol. Speech models win demos easily, then break on accents, long-form consistency, and noisy input. The 16kHz semantic codec plus 48kHz waveform reconstruction is the practical hook here. Against ElevenLabs or CosyVoice, VoxCPM2’s leverage is modifiability, not a leaderboard claim.

This reads like a takedown of the “multi-agent markets spontaneously crash” story. The usable detail is concrete: five market agents using OpenAI, NVIDIA, OpenBMB, and a self-fine-tuned 500M model; three interventions failed to reproduce the price crash; the crash appeared only after settlement prices were overridden. That matters because agent-economy demos often launder simulator behavior into claims about model intent, coordination, or instability. Here, the failure point sits in the environment, not in the agents. The body returned a 429, so the three interventions, market rules, and seeds are not available here. Even with only the summary, I’d treat the result as a warning about simulator artifacts being mislabeled as emergent behavior.

This one's worth opening because Anthropic is publicly sharing internal data on recursive self-improvement for the first time. Jack Clark reports an 8x increase in code merged into their codebase in 2026 versus 2021–2024, with the trend starting in 2025 and accelerating sharply this year. His framing is careful: this isn't the maximalist version where an AI designs its own successor. It's the prosaic version—the lab's overall R&D velocity is compounding, and models are getting better at helping engineers with harder tasks. I'd discount the 8x number a bit. Team growth, infrastructure investment, and automation tooling could all inflate lines-of-code metrics without a pure capability signal. Clark acknowledges this isn't conclusive, and the missing piece is whether models can generate paradigm-shifting ideas. They haven't seen that yet. The same issue also covers SocioHack, a new benchmark where RL-trained models exploit real-world rule systems—credit card points, school grades, regulatory loopholes—across 72 sandbox environments, hitting over 90% precision on historical loopholes. Worth tracking because it shifts the AI safety conversation from code vulnerabilities to institutional gaming: models learning to maximize rewards while staying technically compliant.

If the 3.26x claim holds, local single-GPU inference just got a cleaner latency escape hatch. The concrete hook is strong: Qwen3.6-27B on an RTX 5090, DFlash plus KV cache compression, with q4_0/turbo4 showing 3.18x and only +0.02% PPL on WikiText-2. That is not plain quantization; it is speculative decoding and KV pressure reduction hitting the same bottleneck. The problem is verification: the Reddit body is blocked by 403, and batch size, context length, generation length, and draft-model setup are not visible. llama.cpp-style speedups often look great on fixed prompts, then shrink inside long-context agent loops. I would put this in the “rerun locally” bucket, not the “production conclusion” bucket.

Bordair is useful because it frames jailbreaks as interaction dynamics, not magic strings: multi-turn setup, forward momentum, and role redefinition. The summary gives six months of API traffic and about 6,700 attacks from the public game last month. The Reddit body is blocked by 403, so sample mix, hit rate, and model distribution are not verifiable. That gap matters; security vendors often confuse adversarial-game behavior with enterprise traffic. I buy the pattern list anyway. Plenty of 2025 guardrail evals still tested single-turn refusals, while real agent deployments run long context, tool calls, and slowly shifting task boundaries. If Bordair can interrupt “forward momentum” before the final malicious ask, it is closer to a usable defense than another keyword layer or policy classifier.

AgentScope Java 2.0 matters because Alibaba Cloud is packaging agent runtime work in a shape Java enterprises can deploy. The concrete hooks are not flashy: K8s elastic scaling, session recovery, Workspace-based tenant isolation, HarnessAgent for context and fault handling, and Human-in-the-Loop permission gates. That is the checklist that keeps SRE and security teams from killing an agent rollout. I’m less sold on the capability claim. The snippet gives no latency numbers, recovery test conditions, isolation boundary tests, or integration detail against LangGraph, AutoGen, or Spring AI. The strategy is clear: capture JVM and K8s production estates before agent infrastructure hardens elsewhere. Without reproducible load and failure data, AgentScope Java 2.0 reads more like an enterprise delivery vocabulary than a proven runtime.

WeChat’s sharp move is not the agent UI; it is collapsing Mini Programs, phone assistants, and payment paths into one entry point. The summary gives three hard hooks: a right-swipe chat window, natural-language calls into millions of Mini Programs, and A2A links with Huawei, Honor, Xiaomi, OPPO, and vivo. The article body is only a CAPTCHA page, so pricing, rollout size, and developer requirements are not disclosed. This looks like Tencent finally refusing to fight OpenAI, Doubao, or Kimi on chat quality. It is using WeChat’s transaction graph to own task execution. Ordering coffee sounds boring, but that is the point: agents win when they cross merchant accounts, identity, payment, and fulfillment. Baidu and Alibaba have pieces of that loop. WeChat already has the daily door.

2x3090 running Qwen3.6-27B int4 near linearly is useful, but I would not treat it as proven law. The reported setup has teeth: no NVLink, PCIe 8x/8x, TP=2, narrative decode from 53 TPS to 94 TPS, and code decode from 62 TPS to 120 TPS. For a 27B int4 model on one RTX 3090, weight bandwidth and memory pressure are already tight, so splitting the model can expose a lot of hidden headroom. The catch is that the Reddit body is blocked by 403, so batch size, prompt length, KV-cache settings, backend, and exact flags are not verifiable here. vLLM, llama.cpp, and exllamav2 behave very differently under tensor parallelism. P2P being enabled also does not make PCIe free. I’d use this as a strong homelab configuration hint, not as a general multi-GPU inference rule.

WeChat AI is taking the most Tencent-native route: turn mini-program pages into callable actions. Automatic mode lets the platform read mini-program source code during submission and analyze pages. Developer mode lets teams submit custom skills, then pass evaluation and review. Both modes can run together, and Tencent says existing mini-program services are unaffected. The risky part is the automatic mode. WeChat owns identity, payments, social graph, and mini-program distribution, so an agent that can “access, call, and operate” pages has a cleaner path than a standalone assistant. The article does not give rollout scale, permission prompts, rollback behavior, or skill-review criteria. OpenAI and Apple have already shown how brittle app actions get; WeChat’s version touches commerce and local services, so the blast radius is larger.

Two sources on this one: NVIDIA's own blog and a Chinese outlet that translated it. No UK government release, no third-party analysis — so everything we're seeing is through NVIDIA's lens. The blog drops a few concrete numbers: UK-based cloud providers doubled in a year, all running on NVIDIA GPUs and software, covering healthcare, education, and public services. The figures are probably real, but which customers get highlighted and how the growth story is framed is NVIDIA's call. The Chinese piece adds nothing new. I'd treat this as NVIDIA marketing the "sovereign AI" concept with a UK case study. What I actually want to see — UK government procurement data, compute allocation plans, pricing — isn't in either article.

Amap’s sharp move is not the “world first” label; it is pushing 3D city generation to one satellite image, 10 minutes, and a consumer GPU. ABot-Earth0.5 covers 190+ countries and regions, outputs editable 3DGS assets, and can feed Unity or Unreal Engine. That is closer to a production pipeline than another NeRF or Gaussian Splatting demo. I don’t fully buy the “1% of traditional cost” and “1000x efficiency” claims yet. The article gives no baseline for traditional mapping, city density, texture fidelity, or human cleanup rate. Google Earth, Cesium, and Niantic all ran into update cadence and geometric trust, not raw generation speed alone. Amap has the base-map and road semantics advantage; the stress point is verifiable accuracy.

The sharp part is Russia pausing a surveillance system after Iran’s Supreme Leader was killed. That pause says more than the “AI spying breakthrough” label: Moscow treated CCTV analytics as part of a targeting chain, not just policing infrastructure. The snippet gives only three hooks: CCTV data, AI, and targeting enemies. It gives no system name, vendor, model mechanism, or timeline. I don’t buy the “breakthrough” framing yet. Face recognition, gait cues, and cross-camera tracking have lived inside city security stacks for years. The escalation is connecting identity, live movement, and strike decisions. The Lavender and Where’s Daddy reporting around Gaza already showed the pattern: the model does not need to pull the trigger. It only needs to compress the path from detection to location.

PE software acquisitions fell to $50B in the first five months, and that is a pricing reset, not a generic deal slump. The snippet gives value only. It does not give deal count, sector mix, or the definition of the “AI rout,” so the headline is doing a lot of work. The buyer question has changed. In 2021, a software take-private deal could lean on ARR, retention, and gross margin. In 2026, every workflow vendor gets tested against Copilot, Cursor-style coding agents, and ServiceNow’s AI layer. I don’t read this as PE abandoning software. I read it as PE refusing to pay old SaaS multiples for products whose moat now depends on whether AI sits inside the workflow or eats it from above.

This is NVIDIA's own blog post announcing an AI factory partnership with LG Group, and aihot-selected republished it in full — so both sources trace back to the same official material. LG will use NVIDIA's GPUs and software stack to build an AI factory focused on physical AI and autonomous driving. LG's businesses span electronics, displays, auto parts, and batteries, so the factory is meant to serve both internal needs and external customers. I'd take this with a grain of salt for now. Official blogs are PR vehicles, not technical disclosures — there's no compute scale, no investment figure, no timeline. What's confirmed is that LG joins the list of large Korean enterprises signing on with NVIDIA, and the "AI factory" branding keeps spreading across industries. The thing to watch for is whether concrete order sizes or deployment dates follow. Right now it's a framework announcement.

This is all from Mark Gurman's Power On newsletter — the Japanese Bloomberg piece and the Chinese reprint are the same source, not independent reporting. Gurman has a solid track record on Apple's supply chain and personnel moves, but this story is about internal debates, not product specs or launch dates, so there's less to verify against. The core tension he describes: one camp wants to fix the existing Siri first, the other wants to skip straight to a new LLM-powered version. That split isn't surprising — Apple demoed new Siri features at WWDC last year and they've been delayed repeatedly, so people have been guessing about internal disagreements for a while. Gurman's piece adds names and specifics to those guesses. I'd take this with a grain of salt. Internal arguments framed as a 'crisis' and a 'battle' is a narrative choice, not a confirmed fact. No second outlet has independently corroborated the same inside details, and Apple hasn't commented. If you're tracking Apple's AI timeline, this helps explain why Siri is moving slower than expected, but don't read it as a settled direction yet.

Moonshot’s $30B ask feels rushed; that price buys a scarce Chinese closed-model seat, not proven Kimi economics. Bloomberg’s hard facts are thin: up to $2B sought, a $30B target valuation, and a third financing effort in six months. Revenue, gross margin, enterprise retention, and cloud-credit terms are not given. Kimi did earn real long-context mindshare, but DeepSeek’s low-cost inference and open distribution changed the valuation anchor. Closed labs now need application revenue, not just model demos. Three funding pushes in six months smells like ammunition before the window gets tighter.

RTPurboV2 looks like a cheap life-extension path for vanilla Transformers, not another bet on Mamba or SSMs. The hard hook is specific: 85% of attention heads become SWA, while the remaining 15% retrieval heads get low-rank projection, clustering, and dynamic top-p compression. The adaptation reportedly needs about 600 steps and 1M label tokens, with up to 9.36x Prefill speedup. I discount the 9.36x until the setup is visible. The WeChat body is blocked by verification, so model size, context length, batch size, hardware, precision, and quality regression are not disclosed here. Unlike vLLM or FlashAttention-style runtime work, this changes the attention pattern. If the gain only appears on selected long-sequence cases, it is a narrow serving trick, not a broad inference-cost reset.

MANGO looks like better routing over GPT-4o-mini, not proof that agent swarms suddenly reason well. The hard numbers in the summary are a 12.8% accuracy gain over MaAS on MATH500 and a 5.1% F1 gain over AFlow on DROP; the knobs are reinforcement learning, textual gradients, and Skip-k scheduling. I buy half of it. Multi-agent work has had one boring failure mode all year: more nodes raise cost, latency, and error propagation. The article body is CAPTCHA-gated, so token cost, number of calls, failure cases, and significance tests are missing. Without those, the 12.8% says the flow search found a nicer path, not that the swarm story is solved.