[NREM][Space] Document deployment process for Chrome Web Store releases

[numbers-official]

Problem

In the PR #9 review conversation, a team member (wcchung) asked whether merging to main auto-deploys to Chrome Web Store, indicating the deployment process is not well understood across the team. Another member (olgahaha) clarified that GitHub Actions must be manually triggered and that she had shared the steps before.

Evidence (from PR #9 conversation, bf08ad18)

@wcchung: "After I merge the pull request, will it automatically submit to Chrome extension store. Or I'll need further process?"
@olgahaha: "you can use GitHub Actions to deploy. Merging to the main branch won't trigger the deployment. I've shared the steps with you before."

The release workflow (.github/workflows/release.yml) uses workflow_dispatch with a version_type input (patch/minor/major). It bumps version, builds, creates a GitHub release, and uploads to Chrome Web Store as a draft. This is not documented in the repository README or any contributor guide.

Proposed Approach

Add a RELEASING.md or a "Releasing" section in README.md documenting:

1. The release workflow is manual (workflow_dispatch), not triggered by merge.
2. How to trigger it (GitHub Actions tab → "Release to Chrome Web Store" → select version type).
3. The release uploads as a draft to CWS — a manual publish step is still needed in the CWS developer dashboard.
4. Required secrets/vars: CHROME_EXTENSION_ID, CHROME_CLIENT_ID, CHROME_CLIENT_SECRET, CHROME_REFRESH_TOKEN, OAUTH_CLIENT_ID, EXTENSION_KEY.

Generated by NREM Mode with Omni