[purpshell]

Summary

Adds native Number catalog list/get/products/sync and Marketing Messages status, Official multipart and Linked Devices group picture commands, and Platform webhook batching flags/details. Existing Graph invocations and native contact block/unblock remain available. Help and docs describe betas, feature errors and Hybrid linked-only routing.

Draft, waiting for the accepted SDK prerelease containing SDK #360. Local checks use the exact packed SDK candidate f9937116b17f9962de8a3eb632c44d0399b05002; the committed registry dependency remains 0.1.0-dev.20261004024706. No Git/file dependency or unpublished version is committed.

Impact

Area	Status	Evidence
CLI commands, output, help and docs	Updated	src/commands/cloud, src/commands/group/picture.ts, src/developer/batching.ts, docs/official-api-round2.md
TypeScript SDK dependency	Blocked on registry publication	SDK #360; exact candidate and backend merge/spec/release pins in contracts/official-api-round2.json
Go, Python, PHP, Rust, C#	Coordinated with native owner	SDK #348 retains all native branch ownership and its existing Official subset; no native code here
Release evidence	Held	published:false supplement is enforced by scripts/prepare-release.mjs
Production dependency audit	Blocked on existing dependency	Unchanged @modelcontextprotocol/server@2.0.0 has high advisories GHSA-jm63-cq47-j5jp and GHSA-46jr-4wx8-v453, plus moderate GHSA-rvq5-wwqv-78pq; audit reports 2.3.1 as an available fix
Session checkpoint publication	Blocked	Coordinator's monorepo push hold and delegated T3 V2 recorder gap

No impact table

Area	Reason and evidence
API, backend libraries, runners/Bartender, Temporal, Admin API/MCP, producer logs/audits	Consumes the six merged backend contracts; no backend state or authority changes
Inspector, Console, Admin UI, Help Center, marketing	No graphical UI change; private Console routes are excluded
Authentication, enrollment/flags, billing/PAYG/Usage, analytics, tracking, experiments, onboarding authority	Reuses existing SDK/client and server checks; no credentials, enrollment, financial or measurement mutation
Shared CI and dependency lock inputs	All selectors are GitHub-hosted ubuntu-latest; workflow, package.json and lockfile remain unchanged

Verification

Node 24.15.0 with the exact local SDK package candidate: 111 test files / 1,066 tests passed. Typecheck, lint, build, formatting, release-evidence checks and package dry-run passed. New fixture tests exercise native routes, preserved error codes/exit 3, multipart bytes, JSON/help output, invalid flags and Linked Devices picture routing. Existing Graph command tests pass.

Exact-head CI 39565704066 fails at npm ci's prepare/build step with the old registry SDK, which lacks catalogs, getStatus, Official setPicture and WebhookBatchingInput. The independent clean registry-pin typecheck reproduces those seven errors. CI remains blocked until the exact SDK prerelease pin moves. The production audit also fails on the unchanged MCP dependency. No checks/assertions were weakened and no manual CI run was dispatched.

Session provenance and UI evidence

Agent registration #511, Codex / gpt-6.1-sol, delegated task oa-p-sdk-cli-20261021. Selected visible excerpts remain local inside the dedicated monorepo worktree. Full delegated transcript capture and a published checkpoint are unavailable; the current recorder uses older T3 projections and monorepo pushes are held. CLI text/HTTP fixtures only; no graphical UI or real credentials/customer content.

Rollout and rollback

Targets CLI main 301bd6afd019aa8422cc91912424981387effb25. SDK first, then accepted registry publication, exact CLI package/lock pin refresh, full clean verification and exact-head CI. Nightlies require matching staging acceptance; stable publication requires production acceptance. Keep the draft and explicit release hold until those dependencies and the audit blocker are resolved.

All source workflow selectors are GitHub-hosted only, so the conditional ci-1 push hold does not apply to this CLI push. No monorepo push, provider action, flag/enrollment change, deployment, hosted receiver test or package publication occurred.

Revert the commands/settings support to roll back the CLI. A client revert does not reverse applied blocks, catalog refreshes or group pictures. Hybrid group operations never retry through Official.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}