Add page-level Fork CTA to agent profile header#286
Open
PunchTheDev wants to merge 1 commit into
Open
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
Adds a context-aware Fork CTA row to the bottom of the agent-profile header card on
/rankings/:agentId. A would-be competitor landing on the page now sees a clear, page-level action ("challenge this agent's setup") and an accent-styledFork repo →button — separate from (and complementing) the per-problem↗ codechips already in the table below.Motivation
BACKLOG row
Fork CTAs — ○ ○ ○. Before this PR the only fork affordances on the agent profile lived inside the per-row table chips. A would-be miner scanning the page chrome got no obvious "what do I do next" handle — failed the "would-be miner" seat.Changes
src/App.tsxL2185–2204 (AgentDetailPage): new bordered-top row inside the header card with two parts:entry.total_wins:total_wins > 0:Challenge {contributor}'s setup — fork the repo, open any of their N #1 problems below, and beat the score to take the top spot.total_wins === 0:Race {contributor} for the top spot — fork the repo, pick any of their M entered problems below, and submit a passing agent with a better score.Fork repo →linking to${FORGE_REPO}/fork, target=_blank, with a 155-char tooltip explaining what fork actually does ("Opens the GitHub fork dialog for PunchTheDev/forge — your fork is where you edit an agent.py, run forge eval locally, and open a PR back to this benchmark.")BACKLOG.md:Fork CTAsrow flips○ ○ ○→● ● ●with full notes on the implementation.Verification
Puppeteer at 1440×900 on
/rankings/PunchTheDev:ctaPresent=truectaHref="https://github.com/PunchTheDev/forge/fork"target="_blank"ctaTooltipLen=155sentenceText="Challenge PunchTheDev's setup — fork the repo, open any of their 3 #1 problems below, and beat the score to take the top spot."(total_wins=3 path)rgba(99, 102, 241, 0.1)(forge-accent/10)borderTop=1pxdivider present