Complete v0.3.2 Chrome Web Store dashboard listing closeout

[lamemustafa]

Pack v0.3.2 has been submitted to Chrome Web Store, but dashboard-side listing evidence is still incomplete.

Evidence already recorded:

• Chrome Web Store Submit run 28704776806 completed successfully for v0.3.2.
• docs/PUBLICATION_READINESS.md records upload state SUCCEEDED, publish state PENDING_REVIEW, and no warnings.
• docs/chrome-web-store/assets/exports/asset-hashes.json records the seven synthetic/redacted listing PNG exports.
• pack.complyeaze.com/source now exposes the reviewed Pack commit ed6d209225c4... and the Chrome Web Store asset hashes after ComplyEaze PR #142.

Remaining dashboard work:

• Upload/review the v0.3.2 GSTR-1 listing copy in Chrome Web Store dashboard.
• Upload/review the generated screenshot and promotional PNG assets from docs/chrome-web-store/assets/exports/.
• Confirm privacy-practices declarations and reviewer instructions match the exact v0.3.2 build.
• Record dashboard image/listing review state and final publication evidence.
• Keep store-facing claims source-first alpha until publication is proven.

Acceptance criteria:

• Dashboard contains the v0.3.2 title/short description/full description from docs/chrome-web-store/listing.md.
• Dashboard asset inventory matches docs/chrome-web-store/assets/exports/asset-hashes.json or any intentional difference is recorded with reason.
• Chrome Web Store dashboard shows v0.3.2 as published/live, or the pending/rejected state is recorded with exact date and next action.
• docs/PUBLICATION_READINESS.md is updated with the dashboard/publication evidence.
• pack.complyeaze.com/status remains accurate after any publication-state update.

Related:

• Configure read-only Chrome Web Store status credentials #59 tracks read-only Chrome Web Store status-monitor credentials. That monitor should be used to verify submitted/pending or published state once its read-only credential is configured.

[lamemustafa]

Repo-side runbook follow-up is merged in PR #63 as commit 412515f6bcce.

New operator checklist: docs/chrome-web-store/dashboard-closeout.md.

Remaining external closeout is still dashboard-held: upload/review the v0.3.2 listing copy and PNG assets, complete privacy-practices declarations and reviewer instructions in the Chrome Web Store Developer Dashboard, configure the read-only status workflow credentials tracked in #59, then record review/publication evidence in docs/PUBLICATION_READINESS.md.

[lamemustafa]

Fresh closeout check after Pack PR #63 and ComplyEaze PR #143:

• pack.complyeaze.com/source and /status are now live on Pack source 412515f6bcce and still correctly show CWS v0.3.2 as PENDING_REVIEW.
• The public Chrome Web Store listing still shows the old published Store item: title ComplyEaze Pack: GST GSTR-3B Downloader, visible version 0.2.1, and GSTR-3B-only copy. I did not find public GSTR-1 listing text on the Store page.
• Recent Chrome Web Store Status workflow runs are still failing; latest observed run was 28736100206 (schedule, master, ef8d2c09..., completed/failure, created 2026-07-05T09:22:11Z).

So this issue remains open for dashboard-held closeout: upload/review the v0.3.2 GSTR-1 listing copy/assets/privacy/reviewer fields and then record the final Store review/publication evidence.