Fast checks when reviewing a VoiceOS Composio integration PR
Five quick checks caught most problems across about 12 VoiceOS integration PRs (2026-11). (1) Published version vs PR: curl -s https://api.voiceos.com/integration-share/<slug>/page | grep -oiE 'Version</dt><dd>v[0-9.]+' and compare with voiceos.integration.json, package.json and the McpServer version. Many PRs were 1 to 8 versions ahead of the share link, so QA was testing old code. (2) Real Cancel buttons: jq -c '.tools[]|select(.confirmation)|{name,type:.confirmation.root.type,kids:[.confirmation.root.children[]?.type],footer:[.confirmation.root.footer[]?.items[]?.role]}'. Only a card with footer [cancel,confirm] and no widget child has Cancel; a later version can quietly swap a working card back to a nested widget. (3) Composio user: grep for a hardcoded "default" user_id or a first-account fallback (connected_accounts?...&limit=5 then items[0]); either one makes installs share an account. Prefer a voiceos-<uuid> saved under ~/.voiceos/, since the integration folder may be replaced on update. (4) A settable Composio base URL or other host preference sends the API key wherever the user points it; permissions.domains should be the only host. (5) Uploads from local paths need an allowlist of home folders checked after realpath, not a dot-folder blocklist.