Refs #406: Accept hash-prefixed activity searches

[er1c-cartman]

Summary

• Let accepted-work activity search treat #<number> as a GitHub-style issue/bounty reference.
• Preserve the displayed query text (#164) while matching the numeric bounty issue or bounty id fields.
• Add API and rendered activity-page coverage for hash-prefixed issue searches.

Validation

• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python -m pytest tests/test_activity.py -q -> 3 passed, including invalid hash queries #, #abc, and #123abc
• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev ruff check tests/test_activity.py -> passed
• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev ruff format --check tests/test_activity.py -> 1 file already formatted
• git diff --check -> passed

Summary by CodeRabbit

• New Features

  • Activity search now supports filtering by GitHub issue number with a # prefix (e.g., #164) to find work tied to a specific issue.

• Tests

  • Added test coverage for filtering by issue reference and for invalid # queries returning no results.

• Bug Fixes / UI

  • Activity page correctly shows the # query in the search input, a “Showing accepted work matching” message, and a “Clear” link when filtered.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 065e6d29-9609-40cc-a7d2-27639d5ba739

📥 Commits

Reviewing files that changed from the base of the PR and between a2743e3 and 720f1f1.

📒 Files selected for processing (1)

• tests/test_activity.py

---

📝 Walkthrough

Walkthrough

This PR adds issue-reference search to activity filtering. A new helper function parses #<number> queries and extracts digit-only issue numbers. The activity row matching logic retains substring search and adds special-case matching against bounty_id and bounty_issue_number. Test coverage validates both API and UI filtering paths.

Changes

GitHub issue reference search in activity

Layer / File(s)	Summary
Issue number query parsing and matching app/serializers.py	New helper function extracts digit-only issue numbers from #... queries. Activity row matching adds special-case handling to check extracted numbers against bounty_id and bounty_issue_number string values while retaining existing substring search.
Activity filter test coverage tests/test_activity.py	API test validates issue-reference search response including normalized query, totals, and matching items; tests iterate invalid # inputs to assert empty results. UI test verifies /activity page filtering displays search input, confirmation message, filtered results, and clear link.

Possibly related PRs

• ramimbo/mergework#299: Both PRs modify the /api/v1/activity query-matching logic in _activity_row_matches (this PR adds q=#<issue> parsing/matching against bounty_issue_number, while the other PR expands searchable bounty-related fields like bounty_issue_url), so they share the same code path.

🚥 Pre-merge checks | ✅ 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Refs #406: Accept hash-prefixed activity searches' is concrete and directly names the changed surface—adding hash-prefixed query support to activity search.
Description check	✅ Passed	The description includes a clear summary of the changes, validation evidence for tests and linting, and references the related issue. Required template sections are covered.
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.
Mergework Public Artifact Hygiene	✅ Passed	No investment, price, cash-out, off-ramp, fabricated payout, or security details found. MRWK properly described as native coin supporting future snapshots, bridges, and onchain claims.
Bounty Pr Focus	✅ Passed	PR #486 references Bounty #406 and changes match stated scope: hash-prefixed activity search support added with comprehensive test coverage, no unrelated changes.

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

---

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

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: fc20348f-afe7-49c0-95d3-b1bc9211e576

📥 Commits

Reviewing files that changed from the base of the PR and between d8532d4 and a2743e3.

📒 Files selected for processing (2)

• app/serializers.py
• tests/test_activity.py

[GHX5T-SOL]

Reviewed PR #486 at current head a2743e39aff7bfa0bdbb5b7c7d5c207ea379008c.

I do not see a blocker. The patch keeps the activity search display value intact (#164) while allowing a GitHub-style issue reference to match the numeric bounty issue number or internal bounty id. The fallback remains the existing broad text search first, so ordinary account/repo/proof searches continue to work before the hash-reference path is considered.

Validation I ran:

PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python -m pytest tests/test_activity.py -q -> 3 passed
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python -m pytest tests/test_activity.py tests/test_serializers.py -q -> 8 passed
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python -m pytest -q -> 414 passed
uv run --extra dev ruff check app/serializers.py tests/test_activity.py -> passed
uv run --extra dev ruff format --check app/serializers.py tests/test_activity.py -> 2 files already formatted
uv run --extra dev python -m mypy app -> success
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python scripts/docs_smoke.py -> docs smoke ok
git diff --check origin/main...HEAD -> clean
gitleaks detect --no-banner --redact --source . --log-opts origin/main..HEAD --exit-code 1 -> no leaks found

GitHub CI is successful and CodeRabbit reports no actionable comments.

[GHX5T-SOL]

Reviewed the updated head 720f1f168c1925df3f19c0c92ac0fb0e8784fd08.

I do not see a blocker. The new commit adds the negative coverage CodeRabbit asked for, so invalid hash queries such as #, #abc, and #123abc now assert the empty activity result shape while the earlier valid #<issue> behavior remains covered.

Validation on this head:

PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /home/kali/money/mergework/.venv/bin/python -m pytest tests/test_activity.py -q -> 3 passed
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /home/kali/money/mergework/.venv/bin/python -m pytest tests/test_activity.py tests/test_serializers.py -q -> 8 passed
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /home/kali/money/mergework/.venv/bin/python -m pytest -q -> 414 passed
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /home/kali/money/mergework/.venv/bin/python scripts/docs_smoke.py -> docs smoke ok
/home/kali/money/mergework/.venv/bin/python -m ruff check app/serializers.py tests/test_activity.py -> passed
/home/kali/money/mergework/.venv/bin/python -m ruff format --check app/serializers.py tests/test_activity.py -> 2 files already formatted
/home/kali/money/mergework/.venv/bin/python -m mypy app -> success
git diff --check upstream/main...HEAD -> clean
gitleaks detect --no-banner --redact --source . --log-opts upstream/main..HEAD --exit-code 1 -> no leaks found

GitHub CI is successful and CodeRabbit is successful/skipped on the current head.