docs: the ObjectUI protocol pages claim native mobile rendering and offline-first mobile apps that the platform does not deliver #29315

Blocked-by: objectstack-ai/mobile#150

The maintainer asked for this design's cards to be filed but not dispatched yet (verbatim: 「开卡，不要派发」). objectstack-ai/mobile#150 is the release gate.

Defect

Customer-facing docs advertise capabilities the runtime does not deliver, which AGENTS.md Prime Directive 10 forbids (declared ≠ delivered):

• content/docs/protocol/objectui/index.mdx ~line 183: "Mobile app? Same YAML file renders natively (zero code)".
• content/docs/protocol/objectui/index.mdx ~lines 495–515, "Offline-First Mobile Apps":
  • it shows a mobile_renderer: { offline_cache, sync_strategy } block, which is no metadata key the spec declares;
  • it attaches dollar savings figures to it.
• content/docs/protocol/objectui/concept.mdx ~lines 245–285: the server-driven-UI diagram describes a mobile app with a generic native renderer.

Re-check: grep -n "renders natively\|Offline-First Mobile\|mobile_renderer\|Mobile App Bundle" content/docs/protocol/objectui/*.mdx

Reality

The ObjectOS mobile app (objectstack-ai/mobile 2.0) is a native shell that hosts the web Console. Phones get the same Console renderer as browsers, so "one definition, every screen" is still true, but through the Console, not a native renderer. There is no offline mobile renderer.

Ask

• Rewrite those passages to state what is delivered: one definition rendered by the Console on desktop and phone, and the mobile app hosting the Console.
• Delete the mobile_renderer example and the unmeasured savings figures.
• Keep the server-driven-UI argument, which still holds for the Console.

Acceptance

The re-check grep returns nothing that promises native rendering or offline mobile.