Decouple runner onboarding

.github/workflows/generate_leaderboard.yml

@@ -1,15 +1,22 @@
 name: Generate Leaderboard
 
-# Triggers only when results/ changes land on main.
-# This covers both direct merges and squash merges.
+# Triggers when anything that can change the rendered leaderboard lands on
+# main: new community/verified results, generator code, the static site, or
+# the auto-generated README platforms matrix (so a runner/platform metadata
+# change also redeploys). This covers both direct merges and squash merges.
 on:
   push:
     branches:
       - main
     paths:
       - 'results/**'
+      - 'leaderboard/**'
+      - 'tools/generate_platforms_matrix.py'
+      - 'schema/platforms.json'
+      - 'runners/*/meta.json'
 
-  # Allow manual trigger from Actions tab (useful for first deploy)
+  # Allow manual trigger from Actions tab (useful for first deploy or to
+  # force a redeploy when nothing in the watched paths changed).
   workflow_dispatch:
 
 jobs:

.github/workflows/validate_pr.yml

@@ -1,12 +1,16 @@
 name: Validate Submission
 
-# Triggers only when results/ directory is touched in a PR.
-# Schema changes, script changes, and doc changes do not trigger this.
+# Triggers when results/, runner metadata, the platforms catalogue, the
+# README (which contains the auto-generated matrix), or the matrix
+# generator itself are touched in a PR.
 on:
   pull_request:
     paths:
       - 'results/**'
       - 'runners/**'
+      - 'schema/platforms.json'
+      - 'tools/generate_platforms_matrix.py'
+      - 'README.md'
 
 jobs:
   validate-runners:
@@ -66,6 +70,24 @@ jobs:
         if: steps.changed.outputs.folders == ''
         run: echo "No runner folders changed in this PR — skipping."
 
+      # Always validate every runner folder (not just the ones touched in
+      # this PR). This catches drift introduced by shared changes — e.g.
+      # a meta.schema.json edit that breaks an unrelated existing runner.
+      - name: Validate all runner folders (drift check)
+        run: |
+          echo "::group::Validating every runner folder in the repo"
+          python runners/validate_runners.py
+          echo "::endgroup::"
+
+      # README "Supported platforms" matrix is generated from each runner's
+      # meta.json. If a PR changes a runner's suite_support / hardware_label
+      # or adds a new runner without regenerating the table, fail.
+      - name: README platforms matrix is in sync
+        run: |
+          echo "::group::tools/generate_platforms_matrix.py --check"
+          python tools/generate_platforms_matrix.py --check
+          echo "::endgroup::"
+
   validate:
     name: Validate result submissions
     runs-on: ubuntu-latest

.gitignore

@@ -1,27 +1,50 @@
+# ── Python ──────────────────────────────────────────────────────────────────
 __pycache__/
 *.py[cod]
+*.egg
 *.egg-info/
 dist/
 build/
 .venv/
 venv/
 env/
-*.egg
+
+# ── Editor / IDE ────────────────────────────────────────────────────────────
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+*.tmp
 .DS_Store
-*.log
-my_submission/
-mini_result/
-/tmp/
-leaderboard/site/leaderboard.js
-leaderboard/site/api/
+
+# ── Test / lint caches ──────────────────────────────────────────────────────
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+htmlcov/
+.tox/
+
+# ── Jupyter ─────────────────────────────────────────────────────────────────
+.ipynb_checkpoints/
+
+# ── AccelMark local-only files ──────────────────────────────────────────────
 configs/models_local.yaml
 configs/submitter.yaml
 configs/runner_configs/*.yaml
+leaderboard/site/leaderboard.js
+leaderboard/site/api/
 
-# Local-only benchmark artifacts (not needed for submission)
+# ── Benchmark artifacts (local-only — not part of submissions) ──────────────
+samples.jsonl
+samples.jsonl.ipynb_checkpoints/
 accuracy_outputs.jsonl
 run.log
-samples.jsonl.ipynb_checkpoints/
+*.log
+my_submission/
+mini_result/
 *_backup/
 backup/
-.ipynb_checkpoints/
+/tmp/

CODE_OF_CONDUCT.md

@@ -0,0 +1,144 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and maintainers pledge to make participation in
+AccelMark a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic
+status, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances
+  of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Benchmark-specific expectations
+
+AccelMark is a results-driven leaderboard. The following are specifically
+out of scope:
+
+* **Cherry-picked, doctored, or fabricated results.** Submitting a result
+  knowing it does not reflect the listed hardware / software is misconduct,
+  not a mistake. Mistakes are expected and welcome; fabrication is not.
+* **Misrepresentation of affiliation.** Vendor employees may submit results
+  for their own hardware (it is encouraged) — but the `[vendor]` tag in the
+  submitter name must be present, per `CONTRIBUTING.md`.
+* **Disparaging another vendor or contributor's hardware in PR/issue
+  comments.** Numbers speak; commentary should focus on methodology and
+  reproducibility, not on the entity behind a competing result.
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior that they deem inappropriate,
+threatening, offensive, or harmful.
+
+Maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that
+are not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies
+when an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainers by opening a confidential security
+advisory at <https://github.com/JuhaoLiang1997/AccelMark/security/advisories/new>
+or, when GitHub access is not available, by emailing the maintainer listed
+in the repository profile. All complaints will be reviewed and investigated
+promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of
+the reporter of any incident.
+
+## Enforcement Guidelines
+
+Project maintainers will follow these Community Impact Guidelines in
+determining the consequences for any action they deem in violation of this
+Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from a maintainer, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, for a specified period of time.
+Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public
+or private interaction with the people involved, including unsolicited
+interaction with those enforcing the Code of Conduct, is allowed during
+this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.
+
+[homepage]: https://www.contributor-covenant.org