Platform adoption triage, 2026-08-01 to 2026-08-27

Closes the three platform-watch issues open since 08-21: #3641, #3714, #3762 · 27 capabilities, 11 snapshots

The backlog in one strip: 27 capabilities, 21 already decided, 6 decided here

21 green   triaged in #3641's first comment (ADOPT-NOW 3, ADOPT-LATER 4, DECLINE 14).
           Both ADOPT-NOW items landed in #3647. Not re-derived here.
 6 amber   never triaged. Decided in this PR, each with the measurement that decided it.

The six, and what was measured

datecapabilityverdictevidence
08-20Python SDK v1.0 (httpx2, py3.10 floor, removes Text Completions and compaction_control, drops sampling params from Messages methods)DECLINE, one pin changeFloor already clear: pyproject.toml:5 is requires-python = ">=3.11". Zero hits for every removed symbol. The four temperature/top_p/top_k sites are torch model.generate, ChatOllama x2 and a retrieval top_k, not Messages calls
08-26Compliance API session endpoints out of betaDECLINEEnterprise admin surface; no ork code reads it
08-26Claude Science and M365 office_agents transcriptsDECLINEzero hits for claude_science, office_agents, product_surface
08-26Admin API in the ant CLI and 7 SDKsDECLINEevery Admin API string in the repo is MongoDB Atlas
08-27beta-header removal, BetaSkill to BetaContainerSkillDECLINEzero hits for either symbol; publish-skills.mjs uses neither beta namespace
08-27personal and service-account keys, workspace keys legacyDOC NOTEcc-bare-auth-gotcha.md distinguishes no key kind (0 hits for workspace / service account / personal). One paragraph when that file is next edited

Decline-and-document is the point. Four of the six are structurally out of scope for a Claude Code plugin. Saying so in a dated file means the next watcher run does not re-open the question, and a reader who wonders why ork ignores the Compliance API has an answer with a date on it.

The one action

pyproject.toml:24   anthropic>=0.40.0        no upper bound, while the SDK shipped a breaking major
              now   anthropic>=0.40.0,<2

NOT a fix for the removals: the measurement above says ork's call sites survive 1.x untouched.
It is a guard against the NEXT major arriving unannounced in a fresh install.

Standing shape of the lane, so the next reader does not re-derive it

no extraction lane     platform-release-watch.mjs has no LLM step (claude-release-watch.yml:150-153).
                       Snapshot presence on disk is the only state. features[] is never populated.
                       Triage is human BY CONSTRUCTION.
closing is safe        the filer keys off snapshot ABSENCE, not open issues (yml:161-165),
                       and all 11 snapshots are on main. Closing cannot cause a re-file.
convention unused      the experimental: + exit-criteria frontmatter #3627 nominated is documented
                       in doctor/references/version-compatibility.md:10-24 and has 0 uses across 106 skills.
no board               docs/site renders no platform adoption board; the only artefact under it is the
                       static public/lab/platform-watcher-3627.html.