PR reciprocal link into react-on-rails-demo-hacker-news-rsc back to the starter

[justin808]

Context

The demo-portfolio strategy depends on traffic flowing in both directions. Today the HN demo doesn't link back to this starter. PR a small README change with a "See also: react-on-rails-starter-tanstack" callout.

Acceptance criteria

• PR opened against shakacode/react-on-rails-demo-hacker-news-rsc
• README of that repo includes a "See also" or "Related" section linking back to shakacode/react-on-rails-starter-tanstack with a one-line description ("The 2026 TanStack-first starter that this demo's patterns derive from" or similar — match the actual relationship)
• Aim for merge before launch (Wed 2026-06-03); if blocked on review, accept one-way link for launch and freshen post-launch
• Tag Justin for review in the PR

Files likely touched

• README.md in the HN RSC demo repo (small edit)

Notes / gotchas

• Lead time is the risk here — reviews may sit. Open the PR by end of Day 2 (Wed 2026-05-27) to leave 5+ days for review.
• Keep the PR small and tight; reviewers approve quickly when there's no ambiguity
• If you don't have write access to open a PR, coordinate with Justin to get added or have him merge

Wave + dependencies

• Wave: 3
• Owner mode: parallel-safe
• Blocked by: nothing
• Blocks: nothing structural (launch tolerates one-way link if review stalls)

---

Part of the 2026-06-03 HN launch — see internal/planning/3357-react-on-rails-starter-launch.md.

[justin808]

External reciprocal-link PR is open: shakacode/react-on-rails-demo-hacker-news-rsc#30. Keeping this issue open until that PR is merged.

[justin808]

Completed by the reciprocal-link PR merged in shakacode/react-on-rails-demo-hacker-news-rsc#30. Closing this starter tracking issue now that the external PR is merged.