docs(research): archive planning-phase design notes under research/#3
Conversation
Five point-in-time docs from the design sprint that preceded the engine extraction. Adding them to the repo (under research/, not at the root) so the context is browsable, with a README that: - frames them as not-maintained historical snapshots - notes which recommendations shipped vs which evolved - calls out the briefly-considered "TanStack Run" naming so readers don't get confused Contents: - RESEARCH.md — competitive landscape + positioning - API_CANDIDATES.md — three designs evaluated, Candidate 2 won - PRIOR_ART_AI_ORCHESTRATION.md — inventory of Alem's PR #542 - SRC_SKEW_AND_RESUMPTION.md — fingerprint-mode analysis - EXPLICIT_VERSIONING.md — the model that shipped
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis PR introduces six research documents to ChangesWorkflow Design & Research Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
Comment |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
More templates
@tanstack/react-template
@tanstack/react-template-devtools
@tanstack/solid-template
@tanstack/solid-template-devtools
@tanstack/template
@tanstack/template-devtools
@tanstack/workflow-core
commit: |
Moves the five planning markdown files out of the repo root into a new `research/` directory, with a `README.md` framing them as historical context (not maintained docs).
Why
The five files were sitting untracked at the root from the design sprint. The user wants them in the repo for browsable context but not at the root — `research/` is the chosen home.
The README explains:
Test plan
Summary by CodeRabbit