Skip to content

Mark unclaimed sweep and Guide glossary as done in BACKLOG #317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PunchTheDev merged 1 commit into from
Jun 4, 2026
Merged

Mark unclaimed sweep and Guide glossary as done in BACKLOG #317

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions BACKLOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,9 @@ Status: in progress — see forge-dashboard PRs #85+
- [x] "Be the first to compete" CTA now context-aware when agents exist — PR #88

### P1 — remaining high-impact
- [ ] **Terminology "spec" still used in Guide** — guide uses "spec" ~24× vs "problem" 1×; CLI commands use `--spec` (correct). Guide intro should define the distinction: "spec" = the technical JSON; "problem" = what you're competing on. Currently undefined.
- [x] ~~**Terminology "spec" still used in Guide**~~ — Guide now has a Terminology callout (lines 188–199 of `QuickstartGuide.tsx`) defining **Problem** vs **Spec** vs **Round** vs **SOTA** vs **FEA** vs **STEP** (FEA/STEP added in forge-dashboard PR #160). Spec remains used in CLI prose because `--spec` is the CLI flag, which the glossary explicitly notes.
- [ ] **Category icons unexplained** — `⊕` for Stiffness/Weight is opaque. Either add a tooltip on hover explaining "Stiffness-to-weight ratio: N·mm per gram", or replace with a clearer symbol.
- [ ] **"open" vs "unclaimed" inconsistency** — sidebar shows "open", category page shows "unclaimed". Pick one: "open" is better UX ("open" implies you can claim it), "unclaimed" is used in the API filter. Use "open" in UI everywhere.
- [x] ~~**"open" vs "unclaimed" inconsistency**~~ — done. Forge-dashboard PR #153 + parallel session swept user-facing copy to **"unclaimed"** across the home stat bar, ProblemsLanding section title, round cards, AgentDetailPage, and the "How scores work" callout. Aligns with the amber `unclaimed` badge and the API filter `?unclaimed=true`.
- [ ] **Unentered spec score tooltip** — `each scores 1.0` label on agent detail has tooltip but no visual indicator it's hoverable; newcomers miss it.
- [ ] **Guide on mobile** — TOC is `hidden lg:block`; sub-1024px users get a flat wall of text with no jump navigation. Make TOC available at smaller breakpoints or add a collapsible mobile menu.

Expand Down
Loading