Show latest bounty in activity contributor summaries

[g8rr5dg2p7-svg]

Bounty #298

Summary

• Add source bounty metadata to contributor summaries returned by /api/v1/activity.
• Render a Latest bounty link in each contributor card on /activity, so readers can jump from a contributor summary to the source GitHub bounty issue behind that contributor's latest accepted work.
• Keep the existing latest work and latest proof links intact.

Contributor Discovery Impact

The activity page already groups accepted work by contributor, but the contributor cards only exposed the latest accepted work and proof. This adds the missing source-bounty context to the grouped view, so contributors and maintainers can understand which bounty the contributor most recently completed without scanning the full recent-work list.

Validation

• PYTHONPATH=. .venv/bin/pytest tests/test_activity.py -q -> 3 passed
• PYTHONPATH=. .venv/bin/pytest -q -> 243 passed, 2 existing warnings
• .venv/bin/ruff check app/main.py tests/test_activity.py -> passed
• .venv/bin/ruff format --check app/main.py tests/test_activity.py -> passed
• PYTHONPATH=. .venv/bin/mypy app -> success
• PYTHONPATH=. .venv/bin/python scripts/docs_smoke.py -> docs smoke ok
• PYTHONPATH=. .venv/bin/python scripts/check_agents.py -> AGENTS.md ok
• git diff --check -> clean

No secrets, wallet material, deployment credentials, private vulnerability details, payout details, or MRWK price claims are included.

Summary by CodeRabbit

• New Features
  • The contributor activity view now displays a "Latest bounty" field for each contributor, showing their most recent bounty information with a link to the related repository and issue.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 08fb927e-0993-42b7-b5ad-63896fabbeb0

📥 Commits

Reviewing files that changed from the base of the PR and between 29a4dc5 and ee87ea3.

📒 Files selected for processing (3)

• app/main.py
• app/templates/activity.html
• tests/test_activity.py

---

📝 Walkthrough

Walkthrough

The PR extends the activity feature to surface latest bounty information for contributors. The API response now includes the bounty repository, issue number, and issue URL alongside existing contributor metadata. The activity template displays this information as a "Latest bounty" field in the contributor ledger card, with test assertions validating both the API shape and rendered output.

Changes

Latest Bounty Contributor Metadata

Layer / File(s)	Summary
API response with bounty fields app/main.py, tests/test_activity.py	activity_to_dict gains three new "latest" fields for bounty repo, issue number, and issue URL. Test assertions validate the new fields are present in the contributor payload.
Template display of bounty information app/templates/activity.html, tests/test_activity.py	Contributor card adds a "Latest bounty" reference field that renders a link via safe_public_url when latest_bounty_issue_url is available, otherwise shows a - placeholder. Test assertion confirms "Latest bounty" text appears in rendered HTML.

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly summarizes the main change: adding latest bounty information to activity contributor summaries.
Description check	✅ Passed	The description is comprehensive and well-structured, covering summary, impact, and extensive validation results across all required checks.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[weilixiong]

✅ Reviewed with evidence:

Files inspected:

• app/main.py: Added latest_bounty_repo, latest_bounty_issue_number, latest_bounty_issue_url to contributor summaries
• app/templates/activity.html: Rendered "Latest bounty" link in contributor card
• tests/test_activity.py: Updated existing test assertions + template check

Changes: +12/-0 across 3 files

Verification:

pytest tests/test_activity.py -q
3 passed in 1.59s

Assessment: Clean, focused PR matching #298 bounty spec (contributor activity + bounty discovery). No scope drift. Test coverage validates both API shape and HTML template.

Risk: LOW — read-only UI enhancement, no write paths.

[weilixiong]

Review — PR #303: Show latest bounty in activity contributor summaries

Files inspected: app/main.py, app/templates/activity.html, tests/test_activity.py

What changed: Adds latest_bounty_repo, latest_bounty_issue_number, latest_bounty_issue_url to the paid-activity contributor summary, and renders a "Latest bounty" link in the activity template.

Verification:

• py_compile: all clean
• ruff check: all passed
• pytest tests/test_activity.py -x: 3/3 passed (1.05s)
• 3 files, 12 insertions, 0 deletions — focused scope
• Tests cover new field in API response and template rendering
• Activity template correctly links latest bounty issue URL

Findings: No issues. Small, well-tested feature addition. Template uses safe_public_url() consistently with existing patterns. Tests verify both empty-state and populated-state rendering.

Rating: Recommended for accept.

Claim: MRWK bounty #293 (review open MergeWork PRs, round 8, 40 MRWK).