Repository navigation
feat: Official API and Flow lifecycle commands - #41
Conversation
|
Warning Review limit reachedThe included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 4 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Your 60 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (34)
Comment |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review |
|
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Pin the SDK prerelease published from SDK dev a46d2f2, which contains the Official API consumers. Add --idempotency-key to cloud template create and delete (sent once, never retried). Drop the call-detail runtime guard now that the pinned SDK exposes Client.calls.retrieve.
|
Local review (head |
|
Local review (head |
|
Correction to the review note above: the third lockfile bump is js-yaml 4.3.1 → 4.3.2, not picomatch. |
Add commands for Official API templates, catalog discovery, credential health and reauthorization, service-window and pricing observations, project Flow operations, and phone-scoped Flow encryption keys. Typing accepts an inbound Official message ID, while QuickLink status distinguishes request receipts from history delivery. Provider writes are not automatically repeated, destructive Flow and key-replacement actions require
--yes, and unknown receipts remain visible.SDK pin
@polymorfa/sdkis pinned to0.1.0-dev.20261001124422(exact, with lockfile), published by the SDKpublish-devworkflow from SDKdeva46d2f2after polymorfa/sdks #308, #313, #314, #315 and #316 merged. Its contracts are pinned to APIdev29abb7b66a8e225af4df5cf354e9836ccb2ce04c, which contains every Official API PR these commands use.Also in this update:
cloud template createandcloud template deleteaccept--idempotency-key(API #360). The SDK still sends exactly once; reusing the key after an unknown outcome getsidempotency_completedinstead of a second write.calls getno longer needs a runtime guard forClient.calls.retrieve; the pinned SDK exposes it (removes a now-failing lint assertion).Verification (head ce58584)
Node 24: typecheck, lint, prettier, build pass. Full vitest: 100 files, 946 passed / 2 skipped (with
--maxWorkers=4; default parallelism hit 5 s timeouts in unrelated spawn-heavy tests on this machine). Cloud and Flow command tests (25) pass against the published SDK, including the new idempotency header assertions. No live Meta call.Five-part impact
dev.