Add a verified ShakaCode stewardship and ShakaStack lineage timeline

[justin808]

Parent: #45

Why

ShakaStack is more compelling as the culmination of sustained Rails + React work than as a newly assembled brand. The site should show that lineage without turning the homepage into a company biography.

Proposed change

Add a short visual or editorial timeline covering verified milestones such as:

• ShakaCode consulting since 2011;
• creation and production adoption of React on Rails;
• adoption of the Rails community's Webpacker path and its transition into Shakapacker;
• the naming connection: DHH suggested “Shakapacker,” which later inspired “ShakaStack”;
• Shakapacker's evolution to first-class Rspack support;
• development of E2E on Rails, ShakaPerf, and Control Plane Flow from recurring delivery needs;
• consolidation of the projects under ShakaStack.

Dates and wording above are candidates, not automatically publishable facts.

Acceptance criteria

• Verify every date, naming claim, and causal relationship with primary sources or maintainer confirmation.
• Explain Shakapacker as stewardship and a maintained community transition path, not merely a rename.
• Include the DHH naming detail only after confirming the exact wording/context and that it is appropriate to publish.
• Connect Rspack to modern bundling speed without unsupported “fastest” claims.
• Keep the homepage version concise; link to a fuller About/history destination if needed.
• Avoid implying that all five projects began at the same time or through the same extraction process.
• Add tests for links and critical factual copy and complete required validation.