Normalize examples catalog repo slugs

Author: justin808

docs/README.md

@@ -22,7 +22,7 @@ React on Rails is one product with two tiers: open source for Rails + React inte
 
 ### Evaluating Rails + React options
 
-- [Examples and migration references](./oss/getting-started/examples-and-references.md)
+- [Examples and migration references](./oss/getting-started/examples-and-references.md) — maintained starters, migration repos, and Pro + RSC demos
 - [Example migrations](./oss/migrating/example-migrations.md) — curated migration references and proof criteria
 - [Examples gallery](https://reactonrails.com/examples) — reactonrails.com showcase apps
 - [Compare with alternatives](./oss/getting-started/comparing-react-on-rails-to-alternatives.md) — decision guide covering Hotwire, Inertia, Next.js, and more

docs/oss/building-features/rails-webpacker-react-integration-options.md

@@ -114,7 +114,7 @@ Webpack's HMR allows the replacement of modules for React in-place without reloa
 [github.com/pmmmwh/react-refresh-webpack-plugin](https://github.com/pmmmwh/react-refresh-webpack-plugin)
 
 You can see an example commit in the maintained SSR + HMR tutorial repo that
-[adds React Refresh](https://github.com/shakacode/react_on_rails_demo_ssr_hmr/commit/7e53803fce7034f5ecff335db1f400a5743a87e7).
+[adds React Refresh](https://github.com/shakacode/react-on-rails-demo-ssr-hmr/commit/7e53803fce7034f5ecff335db1f400a5743a87e7).
 
 1. Add react refresh packages:
    ```bash

docs/oss/getting-started/examples-and-references.md

@@ -12,7 +12,7 @@ starting from.
 
 ### SSR + HMR Tutorial Demo
 
-- Repo: [shakacode/react_on_rails_demo_ssr_hmr](https://github.com/shakacode/react_on_rails_demo_ssr_hmr)
+- Repo: [shakacode/react-on-rails-demo-ssr-hmr](https://github.com/shakacode/react-on-rails-demo-ssr-hmr)
 - Use it when you want the maintained Rails + React + SSR + HMR walkthrough repo
   that backs the tutorial and Webpack configuration guidance.
 
@@ -36,15 +36,18 @@ starting from.
 
 ## Migration References
 
+For detailed proof criteria and migration contribution guidance, see
+[Example Migrations](../migrating/example-migrations.md).
+
 ### Migrate from `react-rails`
 
-- Repo: [shakacode/react-on-rails-migration-example](https://github.com/shakacode/react-on-rails-migration-example)
+- Repo: [shakacode/react-on-rails-example-migration](https://github.com/shakacode/react-on-rails-example-migration)
 - Use it when you want a focused before/after migration reference instead of
   reconstructing the upgrade from older blog posts.
 
 ### Open Flights Migration Example
 
-- Repo: [shakacode/react-on-rails-open-flights-example](https://github.com/shakacode/react-on-rails-open-flights-example)
+- Repo: [shakacode/react-on-rails-example-open-flights](https://github.com/shakacode/react-on-rails-example-open-flights)
 - Use it when you want a larger example app that shows React on Rails replacing
   `react-rails` in a more realistic codebase.
 
@@ -55,16 +58,24 @@ starting from.
 
 ### Hacker News RSC Demo
 
-- Repo: [shakacode/react-on-rails-hn-rsc-demo](https://github.com/shakacode/react-on-rails-hn-rsc-demo)
+- Repo: [shakacode/react-on-rails-demo-hacker-news-rsc](https://github.com/shakacode/react-on-rails-demo-hacker-news-rsc)
 - Use it when you want a compact public demo of React on Rails Pro with React
   Server Components on a familiar read-heavy UI.
 
 ### Marketplace RSC Performance Demo
 
-- Repo: [shakacode/react-server-components-marketplace-demo](https://github.com/shakacode/react-server-components-marketplace-demo)
+- Repo: [shakacode/react-on-rails-demo-marketplace-rsc](https://github.com/shakacode/react-on-rails-demo-marketplace-rsc)
 - Use it when you want a public performance-oriented RSC demo showing the shape
   of the user-visible win on a marketplace-style surface.
 
+### Gumroad-Style RSC Benchmark Demo
+
+- Repo: [shakacode/react-on-rails-demo-gumroad-rsc](https://github.com/shakacode/react-on-rails-demo-gumroad-rsc)
+- Use it when you want a benchmark-oriented comparison between an Inertia-style
+  surface and a React on Rails Pro + RSC surface on the same product domain.
+- Note: this is a ShakaCode-built demo modeled on a Gumroad-style UI, not an
+  official Gumroad product or integration.
+
 ## Legacy Repos
 
 Version-specific demos, `test-*` repos, generator snapshots, and older tutorial

internal/planning/examples-catalog-and-repo-naming-plan.md

@@ -33,16 +33,16 @@ Those names are package identities, not marketing slugs.
 These are the repos we should feature on `reactonrails.com/examples` and point
 to from the docs:
 
-| Current repo                               | Recommended action | Proposed canonical name               | Notes                                     |
-| ------------------------------------------ | ------------------ | ------------------------------------- | ----------------------------------------- |
-| `react_on_rails_demo_ssr_hmr`              | Rename             | `react-on-rails-demo-ssr-hmr`         | Maintained SSR + HMR tutorial repo        |
-| `react-on-rails-rsc-demo`                  | Rename             | `react-on-rails-demo-rsc-starter`     | Minimal public RSC starter                |
-| `react-on-rails-hn-rsc-demo`               | Rename             | `react-on-rails-demo-hacker-news-rsc` | Compact Pro + RSC showcase                |
-| `react-server-components-marketplace-demo` | Rename             | `react-on-rails-demo-marketplace-rsc` | Performance-focused RSC demo              |
-| `gumroad-rsc`                              | Rename             | `react-on-rails-demo-gumroad-rsc`     | Inertia vs React on Rails Pro benchmark   |
-| `react-on-rails-migration-example`         | Rename             | `react-on-rails-example-migration`    | Focused `react-rails` migration reference |
-| `react-on-rails-open-flights-example`      | Rename             | `react-on-rails-example-open-flights` | Larger migration reference                |
-| `react_on_rails-demos`                     | Rename             | `react-on-rails-demos`                | Shared infrastructure repo for demo apps  |
+| Public repo                           | Recommended action | Canonical status          | Notes                                     |
+| ------------------------------------- | ------------------ | ------------------------- | ----------------------------------------- |
+| `react-on-rails-demo-ssr-hmr`         | Feature            | Rename completed          | Maintained SSR + HMR tutorial repo        |
+| `react-on-rails-rsc-demo`             | Feature            | Keep current slug for now | Minimal public RSC starter                |
+| `react-on-rails-demo-hacker-news-rsc` | Feature            | Rename completed          | Compact Pro + RSC showcase                |
+| `react-on-rails-demo-marketplace-rsc` | Feature            | Rename completed          | Performance-focused RSC demo              |
+| `react-on-rails-demo-gumroad-rsc`     | Feature            | Rename completed          | Inertia vs React on Rails Pro benchmark   |
+| `react-on-rails-example-migration`    | Feature            | Rename completed          | Focused `react-rails` migration reference |
+| `react-on-rails-example-open-flights` | Feature            | Rename completed          | Larger migration reference                |
+| `react-on-rails-demos`                | Feature            | Rename completed          | Shared infrastructure repo for demo apps  |
 
 ## Repos to De-emphasize or Archive
 
@@ -99,8 +99,7 @@ private planning material only.
 ## Execution Order
 
 1. Update docs and `reactonrails.com/examples` first.
-2. After the docs PRs land and demo links are verified, open a tracking issue
-   for the rename/archive rollout.
-3. Rename active featured repos.
-4. Update repo descriptions/topics.
-5. Archive or de-emphasize legacy repos after the new catalog is live.
+2. Verify GitHub redirects for completed renames before removing any legacy
+   slugs from docs or issue references.
+3. Update repo descriptions and topics.
+4. Archive or de-emphasize legacy repos after the new catalog is live.