Repo Check page shows contradictory info when CONTRIBUTING.md is missing

[sunlight7777777]

On the Repo Check page, the Activity & Feasibility panel always tells users to "check the CONTRIBUTING.md file for setup instructions" — even when the Community Standards panel on the same page flags that the repo has no CONTRIBUTING.md. The two panels contradict each other within the same view.

This appears to be a hardcoded template string rather than content rendered from the per-repo community-standards check.

Steps to reproduce

1. Open the Repo Check page for any repo that does not have a CONTRIBUTING.md file (example: infiniflow/ragflow).

2. Observe the Community Standards panel → Contributing Guidelines is marked with a red ❌ (correct — the file does not exist).

3. Observe the Activity & Feasibility panel on the same page → it still reads:

   "To start contributing, fork the repository, clone it locally, and check the CONTRIBUTING.md file for setup instructions."

Expected behavior

The instructions text should be conditional on the result of the CONTRIBUTING.md check (and ideally on other community-standards signals), not a static template applied to every repo.

Actual behavior

The same sentence is rendered for every repo regardless of whether CONTRIBUTING.md exists, directing users to a file that may not be present.

Why this matters for Gittensor specifically

The README states that a repo is more likely to be whitelisted if it provides contributing guidelines. The Repo Check page is therefore a meaningful signal for prospective miners deciding where to contribute. Pointing miners at a non-existent CONTRIBUTING.md undermines that signal and wastes contributor time on repos that don't actually have onboarding docs.

Suggested fix

Replace the static string with a conditional based on the same check that drives the Community Standards card. Rough pseudocode:

if (communityStandards.contributingMd.present) {
  return `To start contributing, fork the repository, clone it locally, and check the ` +
         `[CONTRIBUTING.md](${contributingMdUrl}) file for setup instructions.`;
} else {
  return `To start contributing, fork the repository and clone it locally. ` +
         `This repository does not yet have a CONTRIBUTING.md — refer to the README ` +
         `for setup instructions, or consider opening a PR to add contributing guidelines.`;
}

Additional polish (optional):

• When CONTRIBUTING.md exists, render it as a real link to the file on the default branch instead of plain text.
• Compose the guidance from whatever community-health files do exist (README, PR template, issue templates) rather than naming files that may be absent.

Screenshot