chore: update repo-platform template to staging@70c478026855

[Vivswan]

Automated template update from Vivswan/repo-platform (staging channel).

• Previous: facc3d6
• New: staging@70c478026855

Review any merge conflicts and confirm repository-local sections were preserved before merging.

Note

This branch is regenerated on every sync run; manual commits
pushed to it are overwritten. Make fixes in a separate branch or
after merging.

Warning

copier hit merge conflicts, resolved below in favor of the
template where possible. Restore any dropped local lines that
should stay, and hand-edit anything marked unresolved, before
merging.

CONTRIBUTING.md

Conflict 1: dropped local lines (template version kept):

# Contributing

Thanks for helping improve Cloud Speech!

## Setup

```bash
git clone https://github.com/vivswan/cloud-speech
cd cloud-speech
bun install
bun run dev        # extension dev (browser opens) + website on localhost:5173
```

`bun run dev:extension` runs the extension alone with interactive WXT keys;
`bun run dev:web` runs only the website.

## Before you open a PR

All of these must pass; CI gates on them via the single `all-green` check:

```bash
bun run typecheck      # strict TypeScript, both apps
bun run check          # biome lint + format, YAML style (check:fix auto-fixes)
bun run test:coverage  # vitest unit tests with coverage thresholds
bun run build:chrome && bun run build:firefox  # both browser builds must succeed
```

CI runs these via the repo-owned `.github/workflows/checks.yml`, inside the
managed `ci.yml` gate from [repo-platform](https://github.com/vivswan/repo-platform),
which also checks typography (plain ASCII punctuation only), YAML style,
workflow lint, and CodeQL.

PR titles AND commit subjects must follow
[Conventional Commits](https://www.conventionalcommits.org/)
(`feat:`, `fix:`, `docs:`, `chore:`, and so on). PRs are squash-merged, and the
title becomes the commit that drives release-please versioning. `feat!:` and
`fix!:` denote breaking changes.

## Project layout

- `apps/extension`: the WXT extension (see `AGENTS.md` for architecture)
- `apps/web`: the website with setup guides, pricing, troubleshooting, and the
  privacy policy (Astro, GitHub Pages)
- `sources/`: the original single-provider forks, kept as read-only reference

## Adding a TTS provider

The whole point of the architecture: a provider is one file.

1. Create `apps/extension/src/providers/<id>.ts` implementing `TtsProvider`
   (see `types.ts`; `google.ts` is a good REST example, `polly.ts` an SDK one).
2. Register it with one line in `apps/extension/src/providers/index.ts`.
3. Add its strings to all four locales in `apps/extension/src/locales/`.
4. Add a setup guide page at `apps/web/src/pages/setup/<id>.astro` (copy an
   existing one; Astro routes pages by file path, so there is nothing to
   register).
5. Add `buildSsml`/normalization tests under `apps/extension/tests/providers/`.

No provider-specific code goes anywhere else; the UI, storage, and playback
are registry-driven.

## Localization

Every user-facing string needs a key in `en.yml`, `hi.yml`, `zh_CN.yml`, and
`zh_TW.yml`. The build fails on missing keys in the default locale; please keep
the other three in sync rather than leaving English fallbacks.

## Releases (maintainers)

Merging the rolling release-please PR tags a version, builds the chrome and
firefox zips (plus the AMO-required sources zip) from the tag and attaches them
to the GitHub release, and publishes the single chrome zip to every Chrome Web
Store listing ID and the firefox zip to addons.mozilla.org (each skipped until
its secrets are configured); see `.github/workflows/release.yml`. The website
redeploys on the release via the managed `pages.yml` (production root from the
release tag; every push to main also publishes a preview under `/staging/`).

[Copilot]

Pull request overview

Template-sync PR updating this repository to Vivswan/repo-platform staging 70c478026855, refreshing managed community/CI/security automation files.

Changes:

• Replaces CONTRIBUTING.md with the managed template header + preserves a local-content marker (but local contributing guidance is currently missing below it).
• Updates the managed CI gate workflow (gitleaks action bump, adds dependency review, adds a release-please freshness check).
• Adds/refreshes baseline community & security configuration (Contributor Covenant CoC, repo settings flags, copier template pin).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
CONTRIBUTING.md	Swaps to managed contributing template and adds local-section marker (currently missing the repo-specific content below it).
CODE_OF_CONDUCT.md	Adds Contributor Covenant Code of Conduct file.
.github/workflows/dependabot-bun-lockfile.yml	Comment reflow (no functional change expected).
.github/workflows/ci.yml	Updates gate jobs (gitleaks action, dependency review, release freshness check).
.github/settings.yml	Enables secret scanning + push protection in managed settings.
.copier-answers.yml	Updates tracked template commit reference to the new staging revision.