Skip to content

docs(spec): Transporter — Chrome Web Store launch design#12

Merged
github-actions[bot] merged 1 commit into
mainfrom
spec/transporter-cws-launch
May 22, 2026
Merged

docs(spec): Transporter — Chrome Web Store launch design#12
github-actions[bot] merged 1 commit into
mainfrom
spec/transporter-cws-launch

Conversation

@chrischall
Copy link
Copy Markdown
Owner

Approved design for shipping the Chrome extension to the Chrome Web Store as Transporter — single-word, store-only rebrand. See the doc for full details.

Locks in:

  • Store-facing name + brand-scope (store only, npm/repo stay fetchproxy)
  • Permission strategy (<all_urls> justified)
  • Branding assets layout in docs/store-assets/ (reusable for AMO + App Store later)
  • Privacy policy hosting via GitHub Pages
  • Manual first upload; CWS API automation deferred
  • Transition for existing sideload users (re-pair each MCP once)

This spec → writing-plans → plan execution. Firefox and Safari are explicitly out of scope for this submission.

🤖 Generated with Claude Code

Approved through the brainstorming skill end-to-end. Locks in:

- Store-facing name: Transporter (single word, transit metaphor)
- Store-only rebrand — npm/repo stay fetchproxy; only manifest +
  popup wordmark switch
- Permission set unchanged from current; <all_urls> kept with
  justification (per-MCP domains[] is the runtime enforcement gate)
- Branding assets live in docs/store-assets/ (real icons, promo
  tile, 3 screenshots) — reusable for AMO + Mac App Store later
- Privacy policy at docs/PRIVACY.md served via GitHub Pages
- First CWS upload is manual; Publisher API automation is a
  follow-up after first review passes
- Existing sideload users re-pair each MCP once (no data loss)

Sequential scope: Chrome first; Firefox + Safari each get their own
spec + plan. Future-proofs structure for the cohort by keeping all
branding assets browser-neutral.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@chrischall chrischall added the documentation Improvements or additions to documentation label May 22, 2026
@github-actions github-actions Bot enabled auto-merge May 22, 2026 01:52
@github-actions github-actions Bot merged commit 8393bef into main May 22, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant