Rebuild Explorer Quick Start with prereqs and 5 canonical steps#308
Open
PunchTheDev wants to merge 1 commit into
Open
Rebuild Explorer Quick Start with prereqs and 5 canonical steps#308PunchTheDev wants to merge 1 commit into
PunchTheDev wants to merge 1 commit into
Conversation
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
Explorer's Quick Start was a 4-step recipe in the wrong order (install → scaffold → eval → then explore) with no prereqs row and no PR-submission step. Rebuilt as 5 steps in onboarding-arc order (install → explore → scaffold → eval → PR), with prereqs surfaced explicitly and every step header routed to the canonical Guide section.
Changes
Playground.tsxL83–203 —QuickStartBlockrewritten:Docker Desktop+Python 3.11+) added above the code block as cursor-help tooltips. First-timers without these fail Step 1 silently.gh pr createcommand and a tooltip explaining thepassed/optimizationCI labels.# Nheader gets aStep N ↗link to/guide#setup#explore#write#eval#submit. Explorer's Quick Start now treats itself as the entry point to the canonical explainer, not a duplicate.--dockerflag tooltip — explains it's theforge-eval:latestimage CI uses, so a local PASS won't surprise you with a CI FAIL (matches step 372 framing)..forge/results/{selectedSpec}.jsonparameterized with current spec, mentions thestagefield, links to4-stage pipeline ↗explainer.BACKLOG.md— ExplorerQuick Startflipped○ ○ ○→● ● ●.Verification
Puppeteer 1440×900 on
/explorer?spec=r01_001_easy:# 1.…# 5.)/guide#setup, Step 1–5 → matching anchors, 4-stage pipeline →/guide#eval, Full Guide →/guide/explorer?spec=…→/guide#eval