docs: align the README with the current product - #85
Merged
Conversation
Derssa
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Rewrites the README so it describes what Torollo actually ships today. The hook now leads with the product's core loop — guided roadmaps auto-graded against the real state of your local containers — instead of a generic sandbox pitch.
npx torollo start.Types of Changes
Verification & Testing
Automated Checks
npm run lintsuccessfully with no errorsnpm run buildsuccessfully with no compilation errorsnpm testsuccessfully (all tests pass)Manual Verification
Docs-only change; backend (lint, build, jest) and frontend (lint, build, vitest — 231 tests) all pass. Every factual claim was cross-checked against the repo: roadmap titles, difficulties, durations and step counts against the JSON files in
roadmaps/; the "what validators check" list against the step validators; the RabbitMQ management-console claim against the image tag (rabbitmq:3-management-alpine) and its published port; the anchor link intodocs/adding-a-node.mdand all relative links resolved. Grepped the final README to confirm zero mentions of retired promises or pricing.Checklist