Repository navigation
Calls: document WhatsApp number restrictions in the calls commands - #27
Conversation
|
Warning Review limit reached
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 51 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 73 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 (6)
Comment |
|
@coderabbitai review |
|
|
@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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed5130ea45
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
| `code: "number_restricted"` for anyone else; calls to existing contacts still | ||
| work. A call WhatsApp refuses for that reason ends with | ||
| `reason: "call_restricted"` in `calls watch`. `polymorfa listen | ||
| --events session.restriction_updated` reports the restriction starting and |
There was a problem hiding this comment.
Use the singular listen event flag
The documented monitoring command cannot run because src/commands/listen.ts defines only the singular, repeatable --event flag; oclif will reject --events as an unknown option. Anyone following this instruction therefore cannot subscribe to restriction updates without consulting the separate command help. Change this to polymorfa listen --event session.restriction_updated.
Useful? React with 👍 / 👎.
|
Codex follow-up: the README now uses the singular, repeatable |
|
@codex review |
|
Codex Review: Didn't find any major issues. Delightful! 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 Current head 5880cd3 merges CLI dev c78687d and pins the exact published BanSafe SDK @polymorfa/sdk@0.1.0-dev.20260923101121. Restricted place/invite human and JSON error paths, exit status and request ID have regressions. Full npm verify passed locally (637 tests, build, package check, production audit). Please review this head. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5880cd3fa3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
| `code: "number_restricted"` for anyone else; calls to existing contacts still | ||
| work. A call WhatsApp refuses for that reason ends with |
There was a problem hiding this comment.
Describe the allowlist as prior chats, not contacts
For a saved or otherwise known contact that has never had a direct chat with the Number, this sentence promises that the call will work even though the preceding restriction says only people previously chatted with are allowed. Replace “existing contacts” with “people it has already chatted with” (or equivalent) so operators do not treat address-book/contact membership as sufficient.
Useful? React with 👍 / 👎.
|
Current-head local |
|
@codex review |
|
Codex Review: Didn't find any major issues. You're on a roll. 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". |
|
Merge gate for |
Explains and verifies the Calls behavior when WhatsApp restricts a Number to people it has already chatted with.
calls placeandcalls invitepreserve the API'snumber_restrictedcode, request ID and exit status 3 in human and JSON output. Call watch output preservescall_restricted; the README and help explain the restriction andsession.restriction_updatedevent.The CLI now pins the exact published
@polymorfa/sdk@0.1.0-dev.20260923101121produced by merged SDK #282. Existing Calls and BanSafe services use typed SDK APIs; no raw adapter remains in this change. CLIdevis merged normally.Verification
Full
npm run verifypasses: format, lint, typecheck, 637 tests across 73 files, build, package check and production audit with zero vulnerabilities. Restricted place/invite behavior, human/JSON classification, request ID, exit status and watch output have focused regressions. A live call against a deployed API was not exercised.Contract and release assessment
Current-head CI and automated reviews remain merge gates.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.