Update to Adzviser

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.app.json →

.codex-plugin/plugin.json →

.mcp.json →

assets/adzviser-directory-light.png →

docs/review-notes.md →

skills/adzviser-data-mode/SKILL.md →

skills/adzviser-data-mode/agents/openai.yaml →

skills/adzviser-preview-ui-mode/SKILL.md →

skills/adzviser-preview-ui-mode/agents/openai.yaml →

docs/review-notes.md

− removed · + added

--- before
+++ after
@@ -0,0 +1,141 @@
+# Adzviser review preparation
+
+The five positive and three negative cases, demo URL, countries, commerce
+information and release notes are included in `.codex-plugin/plugin.json`.
+This package uses the original Codex layout, with a single authoritative
+manifest and `.mcp.json`. These notes record verification evidence and are
+not imported as review form fields.
+
+## Simple review prompts
+
+1. How much did we spend on Google Ads last month in the Demo workspace?
+2. How many active users did we have last week in GA4 in Demo?
+3. How many purchase conversions did we have per campaign in Meta Ads last month in Demo?
+4. How many Google Search Console clicks did we get last month in Demo?
+5. How many Shopify orders did we have last month in Demo?
+
+All five use Data Mode, with no widget interaction. The Meta case explicitly
+uses Total Purchases so the meaning of conversion is unambiguous. The three
+negative cases request budget changes, GA4 deletion and Shopify refunds;
+the plugin should explain its limits without invoking its tools.
+
+## Workspace, dates and evidence
+
+The consolidated Adzviser connection exposed to this session listed Demo with
+Google Ads, Google Analytics, Facebook Ads, Search Console and Shopify connected.
+The reviewer account must have access to that same workspace and those sources.
+No dedicated reviewer login was exercised during this preparation.
+
+Verification used the reference date 2026-10-01 in America/Los_Angeles. Last
+month was September 1-30, 2026. Last week was the previous complete Monday-Sunday
+week, September 21-27, 2026. Reviewers should resolve these relative dates at
+execution time; the values below are evidence, not hardcoded expected results.
+
+| Check | Status | Evidence and limits |
+| --- | --- | --- |
+| Google Ads report request | Passed | September Cost returned 12,069.96 with Account Currency Code USD and an account name. Returned spend is already normalized. |
+| GA4 report request | Passed | September 21-27 returned 90 Active users in a single period-wide row, with no daily summation. |
+| Meta Ads report request | Passed | September returned seven distinct campaign IDs and their Total Purchases counts. The request did not substitute another conversion metric. |
+| Search Console report request | Passed | September returned 1,411 Clicks without query/page breakdowns. |
+| Shopify report request | Passed | September returned 170 Orders without customer or order-level personal data. |
+| Consolidated HTTP regression checks | Passed | All 11 existing checks passed with external authentication/data mocked, covering the full catalog, multi-source requests, errors, discovery and coexistence with source-specific connectors. |
+| Local tool annotation presence | Passed | All 65 tool descriptors contain explicit boolean readOnlyHint, destructiveHint, openWorldHint and idempotentHint values. This is not a live portal scan or an approval result. |
+| Full conversational cases | Not run | Direct report calls do not prove fresh-chat date resolution, tool selection, user-visible answers, or handling of the three negative prompts. |
+| Saved portal draft and reviewer sign-in | Not run | No upload, dedicated reviewer sign-in or portal scan was performed here. |
+
+Runtime connection labels do not establish a particular saved portal draft.
+The checks above used the existing consolidated Adzviser connection. No backend
+changes or deployments were needed for this package.
+
+## Demo and listing
+
+Demo: https://youtu.be/U9YHJKabsF8
+
+Anonymous YouTube checks returned ChatGPT App Store Demo by Adzviser, playback
+status OK, a non-private flag and a 385-second duration. The video's visual
+quality and coverage were not independently watched.
+
+The registered MCP URL, confirmed by the published 4.0.0 portal screenshot,
+is https://mcp-chatgpt.adzviser.com/widgets/http. Root status and endpoint-specific
+OAuth protected-resource discovery were reachable at this exact host. This
+single MCP server provides the consolidated catalog, including Data Mode and
+Preview UI; review cases use Data Mode only.
+
+The supplied Adzviser icon is a 256 x 256 PNG. The original display name and default prompts are preserved. The listing now
+uses Data & Analytics and explicitly describes marketing and sales analytics.
+This update is version 5.0.0; version 4.0.0 is already published. The subtitle
+is Google Ads, Meta Ads, Shopify. Existing
+website, support, privacy and terms links are included and reachable. The
+publisher's choices of all supported countries and website-only subscriptions
+carry forward. Reviewer credentials and account email addresses are excluded.
+
+## Supported-source inventory
+
+The listing enumerates all 59 distinct sources in the consolidated server's
+current catalog, grouped by use. Coverage was checked against all 61 live
+source-discovery tools and their local resource mappings on 2026-10-01.
+Facebook page/post and Instagram profile/post tools are each grouped under
+one product. Public ad libraries and PageSpeed Insights are included as data
+sources without implying that users must connect private accounts to them.
+This catalog check does not claim a live report was run against every source;
+the five actual reporting checks are documented above.
+
+## Upload this update
+
+This ZIP updates the existing published Adzviser plugin. Its immutable package
+name is `app-6949dd4e2608819189e651a8086079cb`. Version 5.0.0 follows the
+published 4.0.0 release. The ZIP's single top-level folder matches that package
+name; the local working folder and ZIP filename remain readable. The public
+display name remains Adzviser.
+
+Reupload this corrected 5.0.0 ZIP to the existing 5.0.0 draft. The package uses
+the supported Codex layout: `.codex-plugin/plugin.json` references `.mcp.json`.
+The MCP declaration and both skills' dependency URLs now use the exact URL
+shown on the published 4.0.0 page:
+
+https://mcp-chatgpt.adzviser.com/widgets/http
+
+The draft's MCP key remains `adzviser`. No server alias or app binding was
+invented from the published page's Not specified MCP key. The endpoint was
+corrected to match the existing registration rather than requesting a change
+to the published server.
+
+The category is Data & Analytics. The full supported-source list, subtitle,
+icons, demo URL, five positive and three negative cases, countries and commerce
+information are retained. Credentials are supplied only through secure portal
+fields. Package validation is not a portal upload or approval result.
+
+## Connection investigation, 2026-10-01
+
+The user supplied the published 4.0.0 MCP page. It shows the registered URL
+https://mcp-chatgpt.adzviser.com/widgets/http, Authentication Authorized, Domain
+verified, Configuration Configured, MCP key Not specified, and live tools.
+The earlier prepared drafts declared a different hostname copied from the
+original skill dependency hints. That was a confirmed packaging error.
+
+Changing versions and switching package formats did not correct this URL
+mismatch. A fresh portal export of the preceding 5.0.0 draft was byte-identical
+to all eight uploaded files after removing the ZIP's wrapper directory; the
+portal had received and retained the incorrect declaration.
+
+The installed 4.0.0 package also has a Portal-generated app binding to
+`asdk_app_6949dd4e2608819189e651a8086079cb`. The original 4.0.0 download omits
+that binding, so absence of `.app.json` in an export did not prove a broken
+connection. No app binding was copied into this public author-upload ZIP.
+
+The corrected host's root endpoint returned 200 and status running. Its
+endpoint-specific OAuth metadata returned 200 with resource exactly equal to
+https://mcp-chatgpt.adzviser.com/widgets/http and authorization server
+https://mcp-chatgpt.adzviser.com. Anonymous initialization returned the expected
+401 challenge pointing to that host's OAuth resource metadata. An authenticated
+metric-discovery call through the published Adzviser connection previously
+returned 119 Google Ads metrics and 433 breakdowns.
+
+The corrected archive fixes the verified URL mismatch. The saved 5.0.0 draft's
+association, OAuth state and ability to scan remain unverified until reupload.
+Inspect that draft's MCP card and discovered tools after upload. Run the five
+simple prompts and three negative prompts against the saved version before
+completing review attestations.
+
+Published-plugin update reference:
+https://developers.openai.com/plugins/deploy/submission#update-your-published-plugin