Complete v0.4.0 Chrome Web Store dashboard listing closeout

[lamemustafa]

Pack v0.4.0 has been uploaded to Chrome Web Store, but dashboard-held listing/privacy requirements still block publication.

Current evidence

• GitHub release v0.4.0 points to source commit eb21404d274917876fcba20abce09216ce6348f4.
• Release workflow 29507382500 built and verified the exact ZIP, published the prerelease assets, and uploaded version 0.4.0 to Chrome Web Store.
• Upload state was SUCCEEDED; publish returned HTTP 400 directing the maintainer to complete Developer Dashboard requirements.
• PR docs(store): refresh v0.4.0 listing assets #83 merged as c7d306ed1acb0920a1d00c785755238c8b78a668, providing reviewed v0.4.0 listing copy, privacy/permission declarations, synthetic RGB assets, and hash evidence.
• The public Store listing remains on the previously published package until dashboard work and review complete.

Remaining dashboard work

• Save the v0.4.0 title, summary, full description, single-purpose statement, permission justifications, and data-use selections from docs/chrome-web-store/listing.md.
• Upload the seven committed, hash-matched PNGs from docs/chrome-web-store/assets/exports/.
• Confirm the dashboard uses the exact Store-supported GSTR-1/GSTR-3B single-period scope and excludes private GSTR-2B/full-year claims.
• Save draft, resolve any dashboard validation messages, submit for review, and record the resulting state/date.
• Update docs/PUBLICATION_READINESS.md and pack.complyeaze.com/status only from recorded dashboard/publication evidence.

Acceptance criteria

• Dashboard listing and privacy fields match the reviewed v0.4.0 brief from PR docs(store): refresh v0.4.0 listing assets #83.
• Dashboard asset inventory matches docs/chrome-web-store/assets/exports/asset-hashes.json, or an intentional difference is recorded with reason.
• Chrome Web Store shows v0.4.0 as submitted/pending, rejected with an exact next action, or published/live, with dated evidence.
• Publication-readiness and public status surfaces remain accurate after the dashboard state changes.
• Before any later release PR is merged, README.md and docs/PUBLICATION_READINESS.md source-version claims are aligned with that release version; autogenerated PR chore(master): release 0.4.1 #84 was closed rather than cutting an unauthorized v0.4.1 release.

Related

• Configure read-only Chrome Web Store status credentials #59 separately tracks the read-only Chrome Web Store status-monitor credential. Do not copy write-capable publishing OAuth credentials into that environment.

[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.

[lamemustafa]

Current closeout update (2026-07-16): the stale Store-approval workflow blocker was cancelled, Release Please successfully created v0.4.0 PR #81, and the seven synthetic Store PNGs were regenerated and visually reviewed. Their hashes exactly match the committed asset manifest, so no asset source change is needed. Package/listing closeout remains pending until #81 is review-clean and merged, its protected Store job completes, and the dashboard-held listing/images are saved. The public listing copy must continue to exclude private source-build GSTR-2B and full-year claims.

[lamemustafa]

v0.4.0 submission evidence (2026-07-16): release workflow run 29507382500 successfully built and verified the exact ZIP, created the prerelease assets, uploaded version 0.4.0 to Chrome Web Store, and received upload state SUCCEEDED. The subsequent publish call failed with HTTP 400 and the Store-directed message to resolve requirements in Developer Dashboard. Authentication, release provenance, ZIP integrity, and upload are therefore validated; dashboard-held listing/privacy/permission declarations remain the blocker. Do not blindly rerun until the dashboard shows and resolves the exact validation items.