Refs #406: Accept backticked refs in submission gate

[er1c-cartman]

Summary

• allow scripts/submission_quality_gate.py to recognize Markdown inline-code bounty references such as Refs `#406`
• cover both prose references and /claim command bodies with a focused regression test

Refs #406.

Evidence

The submission quality gate currently recognizes Refs #406 and /claim #406, but common Markdown inline-code variants such as Refs `#406` or /claim `#406` are reported as missing bounty references. This can make a valid submission draft look invalid before a contributor opens the PR. This patch mirrors the queue-health parser behavior for the submission preflight path.

Validation

• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 ~/.local/bin/uv run --extra dev python -m pytest tests/test_submission_quality_gate.py -q -> 24 passed
• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 ~/.local/bin/uv run --extra dev python -m pytest -q -> 415 passed
• ~/.local/bin/uv run --extra dev ruff check scripts/submission_quality_gate.py tests/test_submission_quality_gate.py -> passed
• ~/.local/bin/uv run --extra dev ruff format --check scripts/submission_quality_gate.py tests/test_submission_quality_gate.py -> 2 files already formatted
• ~/.local/bin/uv run --extra dev mypy app scripts/submission_quality_gate.py -> success
• git diff --check -> clean
• changed-file secret scan -> no matches

Note: pytest plugin autoload is disabled because this workstation has an unrelated ROS Humble pytest plugin on the global path.

Summary by CodeRabbit

• New Features

  • Bounty reference recognition now accepts backticked format (e.g., \Normalize GitHub account lookup inputs #123`) in addition to plain Normalize GitHub account lookup inputs #123` format.

• Tests

  • Added validation test for backticked bounty reference handling.

[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: fc786a37-9400-4bb7-808d-4caafe817a66

📥 Commits

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

📒 Files selected for processing (2)

• scripts/submission_quality_gate.py
• tests/test_submission_quality_gate.py

---

📝 Walkthrough

Walkthrough

The PR extends bounty reference parsing to recognize backticked issue numbers (`#123`) alongside plain #123 format. The regex pattern is updated in the quality gate script, and a new test validates that submission evaluation correctly extracts bounty IDs from both formats.

Changes

Backticked Bounty Reference Support

Layer / File(s)	Summary
Backticked bounty reference parsing scripts/submission_quality_gate.py, tests/test_submission_quality_gate.py	BOUNTY_REF_RE regex now optionally matches backtick-wrapped #<number> in addition to plain format. New test validates that evaluate_submission accepts backticked bounty references in both Refs and /claim contexts, extracts the ID, and reports the expected passing check.

Possibly related PRs

• ramimbo/mergework#325: Updates to scripts/submission_quality_gate.py and tests/test_submission_quality_gate.py for bounty reference parsing logic.
• ramimbo/mergework#342: Both PRs modify bounty-reference parsing and extraction in the quality gate and corresponding test coverage.
• ramimbo/mergework#438: Both PRs update the bounty-reference parsing regex to accept specific /claim/Refs reference formats.

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Bounty Pr Focus	⚠️ Warning	PR references Bounty #406 but commits 131 files: 129 unrelated scaffold files plus 2 target files. Diff includes entire repository structure instead of focused changes.	Create clean PR with only scripts/submission_quality_gate.py and tests/test_submission_quality_gate.py to match stated scope.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concretely names the changed surface by referencing the specific issue (#406) and describing the functional change (accepting backticked refs in submission gate).
Description check	✅ Passed	The description includes all required sections: Summary, Evidence, and validation test evidence showing all checks passed. Related bounty reference is present.
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	README and docs contain no investment, price, or cash-out claims; MRWK properly described as native project coin with future features clearly conditional.

_{✏️ 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.}

[carpedkm]

Reviewed PR #479 at current head e416a9499450e0d31f9c189acfc6b556d0a89871. No blocker found.

Evidence checked:

• The diff is scoped to scripts/submission_quality_gate.py and tests/test_submission_quality_gate.py.
• The regex change mirrors the already-reviewed queue-health behavior for optional inline-code backticks around #<issue> after existing bounty/ref/fix/close/claim prefixes.
• Existing plain forms still parse (Refs #319), while the new common Markdown forms parse as intended (Refs #319 and `/claim `#319).
• A mixed reference body with Bounty #319`` and Refs #406 returns both refs, so the change preserves multi-reference behavior.
• The added regression covers both prose and /claim command bodies.
• GitHub Quality, readiness, docs, and image checks is passing.

Validation run locally on this head:

• ./.venv/bin/python -m pytest tests/test_submission_quality_gate.py -q -> 24 passed
• ./.venv/bin/python -m pytest -q -> 415 passed
• ./.venv/bin/python -m ruff check scripts/submission_quality_gate.py tests/test_submission_quality_gate.py -> passed
• ./.venv/bin/python -m ruff format --check scripts/submission_quality_gate.py tests/test_submission_quality_gate.py -> 2 files already formatted
• ./.venv/bin/python -m mypy scripts/submission_quality_gate.py -> success
• ./.venv/bin/python scripts/docs_smoke.py -> docs smoke ok
• git diff --check origin/main...HEAD -> clean

This is a narrow parser usability fix and looks ready to merge from my review.

[GHX5T-SOL]

Reviewed PR #479 at current head e416a9499450e0d31f9c189acfc6b556d0a89871 for Bounty #447.

I checked scripts/submission_quality_gate.py and tests/test_submission_quality_gate.py. The change is scoped to accepting inline-code bounty references such as Refs #319 and `/claim `#319 through the existing reference prefixes, while preserving plain Refs #319 behavior. I also spot-checked that mixed references still de-duplicate/sort correctly and that a backticked ref line is skipped when deriving the submission title.

Validation:

• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python -m pytest tests/test_submission_quality_gate.py -q -> 24 passed
• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 uv run --extra dev python -m pytest -q -> 415 passed
• uv run --extra dev ruff check scripts/submission_quality_gate.py tests/test_submission_quality_gate.py -> passed
• uv run --extra dev ruff format --check scripts/submission_quality_gate.py tests/test_submission_quality_gate.py -> 2 files already formatted
• uv run --extra dev python -m mypy scripts/submission_quality_gate.py -> 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
• git diff --no-ext-diff origin/main..HEAD | gitleaks stdin --no-banner --redact --exit-code 1 -> no leaks found
• uv run --extra dev python -c 'from scripts.submission_quality_gate import _bounty_refs, _title_from_submission; print(_bounty_refs("Bounty #319\\nRefs #406\\n/claim #319")); print(_title_from_submission("Refs #319\\nFix parser title"))' -> [319, 406] and fix parser title

GitHub readback before review showed the PR open/non-draft, merge state CLEAN, and both CodeRabbit plus project CI successful. No blockers found.