docs: restructure README around the user journey

[omaiesh]

Closes #216.

Two files: README.md (the restructure) and CONFIGURATION.md (cleanup, because the README now sends readers there).

README

It opened with positioning material — hero video, "What is Rosetta", a layering diagram, comparison tables, a 12-point collapsible — before a reader reached anything they could act on. This reorders it around what a reader actually does: decide whether they need it, install it, run something.

Intro — what Rosetta changes about the agent's behaviour, then a Do you need it? block with five concrete symptoms, so the stop-or-continue decision happens before install rather than after scrolling. The intro video is collapsed, inline.

Quick start — four numbered steps: install, initialize, review and commit the generated context, run your first workflow. Per-IDE install is one table. Committing the generated files is now its own step; previously it was one clause inside a paragraph, and it is the step people skip.

The recommended path — new section covering the five steps of a real task: get context → pin down what to build → implement → test → check before it ships. Each lists the workflows that fit, with example prompts, and the section ends with two recordings of the path on real projects. All 14 active workflows are represented; the old Top Workflows list had 7 and omitted modernization-flow, research-flow, adhoc-flow, external-lib-flow, and coding-agents-prompting-flow.

What's inside: the skill library — the R3 core skills grouped by purpose, including an Always active group that names the skill behind each guardrail. The old Top Guardrails list described behaviours without saying where they came from.

Go deeper — one collapsed table of every document and what it is for. Adds FAQ.md, ELEVATOR_PITCH.md, REVIEW.md, docs/CONTEXT.md, docs/MCP-ARCHITECTURE.md, and llms-full.txt, none of which were linked from the README before.

Removed — the comparison tables, the layering diagram, "Why not just use IDE rules?", "Who benefits", the 12-point collapsible, and the Contributing section. That ground is covered by OVERVIEW.md and docs/CONTEXT.md, both linked from Go deeper.

CONFIGURATION.md

The README now points here as the thing to do before real work, so the page had to stop repeating what precedes it.

• The Install and Onboard section is removed, along with all five Quick Start references. Installing and initializing happen before a reader gets here; carrying a second copy of those steps is how the two documents drifted apart in the first place.
• Sections renumbered accordingly (Set Up the Repository → 1, Choose a Workspace Layout → 2, Modernization Additional Setup → 3), and the internal link to the modernization section updated.
• Added a short overview list of the five setup steps at the top, so the page opens with what it actually asks of you. The page already claimed to be "the checklist" without showing one.

No existing wording was rewritten — only removed, renumbered, or linked.

Known overlap, deliberately not addressed here

The issue offered two options for QUICKSTART. This PR takes neither — QUICKSTART.md is untouched. The README now carries the same happy path inline, so both documents describe install and first-run.

docs/reviews/DOC-STRUCTURE-PLAN.md is also untouched, so its README contract (which lists "full install steps" and "workflow how-tos" under Excludes) and its open items §5.1 and §5.4 still read as they did before this PR. Both were flagged in the triage comment on #216.

Reconciling the plan and deciding QUICKSTART's fate is follow-up work.

Review notes

• No claim in the new text is invented. The privacy sentence in step 2 is the wording from SECURITY.md; workflow descriptions come from instructions/r3/core/workflows/; the skill list matches instructions/r3/core/skills/.
• The git add line in step 3 uses a <placeholder> rather than an enumerated file list, since the canonical committed-vs-excluded list lives in INSTALLATION.md and would drift if copied.
• The approval notice was dropped from the README only. It still appears in PLUGINS.md, MCPs.md, INSTALLATION.md, QUICKSTART.md, and the docs/web/ mirrors.
• docs/web/ mirrors of these pages are not updated here.

🤖 Generated with Claude Code

[github-actions]

Rosetta Triage Review

Summary: Reorders the README around what a reader does (decide → install → initialize → run a workflow) instead of leading with positioning content, folds QUICKSTART.md into it as a redirect, and updates docs/reviews/DOC-STRUCTURE-PLAN.md to mark the resulting doc-ownership overlap (§5.1, §5.4) resolved. Closes #216.

Findings:

• Workflow index now covers all 14 active workflows (old Top Workflows had 7, missing modernization-flow, research-flow, adhoc-flow, external-lib-flow, coding-agents-prompting-flow).
• The "prior approval from your manager and company" notice is dropped from README but confirmed still present in PLUGINS.md, MCPs.md, and INSTALLATION.md — consistent with the PR description.
• QUICKSTART.md is reduced to an anchor-redirect table into README, matching Option A from docs: restructure README around user journey and merge QuickStart into it #216.

Caveats:

• Doc-only PR (no code/tests affected); scope is focused and matches the linked issue.
• The dropped approval notice is now one hop farther from a first-time reader who starts at README — worth confirming this is the intended tradeoff.

Automated triage by Rosetta agent

[YevheniiaLementova]

I've left several suggestions, otherwise LGTM!

[isolomatov-gd]

This is definitely a step in the right direction, but it is just rephrasing what we had. We need genuinely new good README.md as we talked with important notes on what/why rosetta does something really better.
Example: Discovery phase in coding-flow finds genuine issues and artifacts, design phases allows to select one of three best designs, makes AI follow your intent, etc.