chore: update urls after transfer to FreedomIntelligence org

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
   - name: Live leaderboard
-    url: https://juhaoliang1997.github.io/AccelMark
+    url: https://freedomintelligence.github.io/AccelMark
     about: View all submitted benchmark results
   - name: Contributing guide
-    url: https://github.com/JuhaoLiang1997/AccelMark/blob/main/CONTRIBUTING.md
+    url: https://github.com/FreedomIntelligence/AccelMark/blob/main/CONTRIBUTING.md
     about: How to run and submit a benchmark

.github/ISSUE_TEMPLATE/new_suite.md

@@ -14,7 +14,7 @@ assignees: ''
   merging.
 
   Full walk-through: DEVELOPMENT.md "Adding a new suite"
-                     https://github.com/JuhaoLiang1997/AccelMark/blob/main/DEVELOPMENT.md
+                     https://github.com/FreedomIntelligence/AccelMark/blob/main/DEVELOPMENT.md
 -->
 
 ## Why this suite?

.github/workflows/validate_pr.yml

@@ -14,6 +14,12 @@ on:
       - 'README.md'
       - 'leaderboard/site/**'
 
+# Lock the default GITHUB_TOKEN down to read-only on repo contents for every
+# job (GitHub's hardening recommendation for OSS repos). Jobs that need more
+# (e.g. posting a PR comment) opt in explicitly via their own `permissions:`.
+permissions:
+  contents: read
+
 jobs:
   validate-runners:
     name: Validate runner folders
@@ -116,6 +122,13 @@ jobs:
   validate:
     name: Validate result submissions
     runs-on: ubuntu-latest
+    # Needs pull-requests:write to post the validation summary comment
+    # via actions/github-script. After the FreedomIntelligence transfer
+    # the default GITHUB_TOKEN is read-only on issues/pull-requests, so
+    # this must be granted explicitly.
+    permissions:
+      contents: read
+      pull-requests: write
 
     steps:
       - name: Checkout PR

CODE_OF_CONDUCT.md

@@ -75,7 +75,7 @@ appointed representative at an online or offline event.
 
 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>
+advisory at <https://github.com/FreedomIntelligence/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.

CONTRIBUTING.md

@@ -36,8 +36,6 @@ gh pr create   # or open the PR via the GitHub web UI
 
 That's it. CI validates the result automatically; merging the PR publishes it to the leaderboard.
 
-> _Prefer not to use git?_ Open a [Community Submission issue](https://github.com/JuhaoLiang1997/AccelMark/issues/new?template=community_submission.md), paste your `result.json`, and the CI bot will draft the PR on your behalf.
-
 ---
 
 ## One-time setup
@@ -335,23 +333,13 @@ python -m http.server -d leaderboard/site 8000       # serve the static site
 Both `leaderboard.js` and `leaderboard/site/api/` are gitignored — the GitHub
 Actions workflow regenerates them on every merge to `main`.
 
-### Alternative: open a submission issue (no git required)
-
-If you'd rather not use git, paste your `result.json` into a
-[Community Submission issue](https://github.com/JuhaoLiang1997/AccelMark/issues/new?template=community_submission.md).
-A bot will validate the JSON, draft a PR with the files in the right place,
-and link it back to your issue. You don't need to touch git or fork the repo.
-
-> **Why paste instead of attach?** The bot reads `result.json` directly from
-> the issue body. File attachments are not accessible to GitHub Actions.
-
 ---
 
 ## Leaderboard tiers
 
 | Tier | How to get it | Leaderboard placement |
 |------|--------------|----------------------|
-| **community** | Submit a PR (or issue → bot-drafted PR) and pass CI validation | Community tab |
+| **community** | Submit a PR and pass CI validation | Community tab |
 | **verified** | Independently reproduced on the same hardware/runner within 5% | Main leaderboard |
 
 To promote a community result to **verified**, anyone with the same hardware

DEVELOPMENT.md

@@ -1134,6 +1134,6 @@ python runners/validate_submission.py --dir /tmp/accelmark_test/
 ## Questions and Support
 
 - **Bug in LoadGen or schema:** Open a GitHub Issue
-- **New suite proposal:** Open a GitHub Issue with the [**Propose a new suite**](https://github.com/JuhaoLiang1997/AccelMark/issues/new?template=new_suite.md) template
+- **New suite proposal:** Open a GitHub Issue with the [**Propose a new suite**](https://github.com/FreedomIntelligence/AccelMark/issues/new?template=new_suite.md) template
 - **New platform support:** Open a PR with a working platform script and at least one verified result
 - **Leaderboard question:** Check `leaderboard/generate.py` — it's well-commented

NOTICE

@@ -2,7 +2,7 @@ AccelMark
 Copyright 2024-2026 Juhao Liang and The AccelMark Contributors
 
 This product includes software developed as part of the AccelMark project
-(https://github.com/JuhaoLiang1997/AccelMark).
+(https://github.com/FreedomIntelligence/AccelMark).
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.