docs: move docs site to github.github.com/squad and update repo links (#2411)

* docs: move docs site to github.github.com/squad and update repo links

GitHub Pages doesn't redirect after a repository transfer, so links to
bradygaster.github.io/squad now return 404.

- Astro site, RSS fallback, robots sitemap, header, footer and edit links
- Docs-site and repository links in READMEs, contributor docs, package
  READMEs, current docs pages, a sample and the pr-lifecycle skill
- test/docs-site-location.test.ts guards the site location in CI

Blog narrative, changelogs and bradygaster/squad#NNN references are
unchanged.

Closes #2405

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* test(docs): share one docs-site guard and scan every migrated link

Review fixes for #2411.

The node --test copy of the retired-site guard in
docs/tests/astro-features.test.mjs had drifted from
test/docs-site-location.test.ts. It flagged unrelated sites such as
bradygaster.github.io/squadcaster/, exempted every path under
/schemas/implementation-provenance/, and missed protocol-relative and
upper-case links. Both guards now import one contract,
scripts/docs-site-location.mjs: the site settings, the link patterns,
the scanned files and the historical allowlist. The retired-site pattern
ends /squad at a path boundary and exempts only the exact versioned
schema ID (.../implementation-provenance/v1), not the paths below it.

The old-repository check covered only the five site-chrome files, so a
regression in any other migrated link passed. It now scans every
tracked file under the migrated paths (docs, samples, READMEs,
contributor guides and the pr-lifecycle skill). It also catches the
raw.githubusercontent.com, SSH remote, REST and gh --repo forms that the
migration rewrote. HISTORICAL_REPO_LINKS lists what stays as written:
blog posts, release notes for v1.1.0 and earlier, contributor-credit
and spec-provenance permalinks, the generated upgrade-matrix section of
upgrading.md, and three internal launch and design records. Each entry
needs a reason and must still keep a link, and none may cover a current
entry point.

test/docs-site-location.test.ts pins the settings, the pattern examples
and the allowlist behavior. Every failure names the file and line, or
the input.

Refs #2405

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* test(docs): tighten the schema-ID exemption and guard docs-only PRs

Review follow-up for #2411.

The retired-site exemption for the implementation-provenance schema ID
also accepted dotted suffixes, so links such as
.../implementation-provenance/v1.json or v1.html passed both guards.
The exemption now applies only where the version ends the URL: it must
be followed by the end of the line, whitespace, one of ) " ' ` < > ],
or a # fragment, which points into the same schema. A "." counts only
as a sentence end, before whitespace or the end of the line, and a
query (v1?...) is a link. Every tracked occurrence of the ID still
passes, and new pattern cases cover the .json, .html, query and
fragment forms.

Pull requests that change only docs paths skip the squad-ci test job,
which is where test/docs-site-location.test.ts runs. docs-quality now
also runs node --test docs/tests/astro-features.test.mjs. The suite
needs only Node built-ins, so the step runs before any npm install.
test/ci/docs-quality.test.ts pins that step, the suite's import of the
shared guard, and docs-quality running for docs-only pull requests.

Refs #2405

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: tamirdresher

.copilot/skills/pr-lifecycle/SKILL.md

@@ -138,7 +138,7 @@ For advanced scenarios (worktrees, multi-repo coordination), see `.copilot/skill
 
 2. **Create PR targeting dev:**
    ```bash
-   gh pr create --repo bradygaster/squad --base dev \
+   gh pr create --repo github/squad --base dev \
      --title "fix: brief description (#issue-number)" \
      --body "Closes #{issue-number}
 
@@ -351,7 +351,7 @@ Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>"
 
 # Push and PR
 git push -u origin squad/610-fix-broken-link
-gh pr create --repo bradygaster/squad --base dev \
+gh pr create --repo github/squad --base dev \
   --title "docs: fix broken link (#610)" \
   --body "Closes #610"
 ```
@@ -386,7 +386,7 @@ Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>"
 
 # Push and PR
 git push -u origin squad/42-add-profile-api
-gh pr create --repo bradygaster/squad --base dev \
+gh pr create --repo github/squad --base dev \
   --title "feat: add profile API (#42)" \
   --body "Closes #42
 

.github/workflows/squad-ci.yml

@@ -68,6 +68,10 @@ jobs:
         with:
           node-version: '22.23.4'
           cache: 'npm'
+      # Docs-only pull requests skip the `test` job, so the docs site location guard runs here
+      # as well. The suite uses Node built-ins only, so it needs no npm install.
+      - name: Docs feature and site location tests
+        run: node --test docs/tests/astro-features.test.mjs
       - name: Install docs tools
         run: |
           success=false

CONTRIBUTING.md

@@ -62,7 +62,7 @@ Each package has independent versioning via changesets. A change to squad-sdk ma
 
 **Step 1: Fork the repo on GitHub**
 
-Go to https://github.com/bradygaster/squad and click "Fork" to create your own copy.
+Go to https://github.com/github/squad and click "Fork" to create your own copy.
 
 **Step 2: Clone your fork**
 
@@ -74,7 +74,7 @@ cd squad
 **Step 3: Add upstream remote**
 
 ```bash
-git remote add upstream git@github.com:bradygaster/squad.git
+git remote add upstream git@github.com:github/squad.git
 ```
 
 **Step 4: Fetch the dev branch**
@@ -187,7 +187,7 @@ The Co-authored-by trailer is **required** for all commits (added by Copilot CLI
 
 1. Add a changeset: `npx changeset add` (required before PR — see Changesets section)
 2. Push your branch: `git push origin {yourusername}/217-readme-help-update`
-3. Create a PR **as a draft**: `gh pr create --draft --base dev --repo bradygaster/squad --head {yourusername}:your-branch`
+3. Create a PR **as a draft**: `gh pr create --draft --base dev --repo github/squad --head {yourusername}:your-branch`
 4. Link the issue: Add `Closes #217` to PR description
 5. Work on your changes until CI passes and you're satisfied
 6. **Mark as "Ready for review"** — this is the handoff signal to the core team (see below)
@@ -390,7 +390,7 @@ CI watches for drift: `scripts/check-changeset-drift.mjs` warns on PRs and fails
 
 - **main** — Stable, published releases. All merges include changesets.
 - **preview** — Staging branch for release candidates (promote: dev → preview → main).
-- **bradygaster/dev** — Integration branch. **All PRs from forks must target this branch**, not `main`.
+- **dev** — Integration branch on `github/squad`. **All PRs from forks must target this branch**, not `main`.
 - **user/issue-slug** — Feature branches from users or agents.
 
 > **Note:** The `insider` npm tag (`@bradygaster/squad-cli@insider`) publishes from `dev` via manual workflow dispatch. There is no separate insider branch.

CONTRIBUTORS.md

@@ -19,13 +19,13 @@ The Insider Program gives you access to cutting-edge features before they ship.
 
 ### How to Join
 
-Install from the insider branch using the honor system:
+Install the insider build from npm using the honor system:
 
 ```bash
-npx github:bradygaster/squad#insider
+npm install -g @bradygaster/squad-cli@insider
 ```
 
-That's it. You're now on insider builds.
+That's it. You're now on insider builds. For Homebrew and WinGet, see the [Insider Program guide](https://github.github.com/squad/docs/insider-program/).
 
 ### What to Expect
 
@@ -36,7 +36,7 @@ That's it. You're now on insider builds.
 
 ### Report Issues
 
-Found a bug in an insider build? Please [open a GitHub issue](https://github.com/bradygaster/squad/issues) with:
+Found a bug in an insider build? Please [open a GitHub issue](https://github.com/github/squad/issues) with:
 
 - **Version** — The full version string from your `squad.agent.md`
 - **What happened** — Clear description of the bug or unexpected behavior
@@ -130,4 +130,4 @@ These community members shaped Squad through issues, discussions, and feedback.
 
 Contributing code? See [CONTRIBUTING.md](CONTRIBUTING.md) for the full guide.
 
-Questions? [GitHub Discussions](https://github.com/bradygaster/squad/discussions).
+Questions? [GitHub Discussions](https://github.com/github/squad/discussions).

README.md

@@ -42,22 +42,22 @@ Choose the install method for your platform:
 | npm (all platforms, Node.js 22.5+) | `npm install -g @bradygaster/squad-cli` |
 | Homebrew (macOS) | `brew install --cask bradygaster/squad/squad` |
 | WinGet (Windows) | `winget install --id bradygaster.Squad --exact` |
-| Install script (macOS/Linux, no npm) | See [Standalone Install](https://bradygaster.github.io/squad/docs/features/standalone-install/) |
+| Install script (macOS/Linux, no npm) | See [Standalone Install](https://github.github.com/squad/docs/features/standalone-install/) |
 
 Preview and insider builds are available as `squad-preview` and
 `squad-insider` Homebrew casks, or as `bradygaster.Squad.Preview` and
 `bradygaster.Squad.Insider` WinGet packages.
 
 Direct archives for macOS, Linux, and Windows are also available from
-[GitHub Releases](https://github.com/bradygaster/squad/releases/latest).
+[GitHub Releases](https://github.com/github/squad/releases/latest).
 
 ```bash
 squad init
 ```
 
 All methods install the same CLI. Standalone installs vendor Node.js, so they do
 not require Node.js or access to the npm registry. See the
-[complete installation guide](https://bradygaster.github.io/squad/docs/get-started/installation/)
+[complete installation guide](https://github.github.com/squad/docs/get-started/installation/)
 for prerequisites and platform details.
 
 > **⚡ Want to be up and running in under a second?** Use `squad init --preset default` to start with a fully-configured squad — complete with members, charters, and routing rules — ready to go immediately. The default `squad init` (without the flag) walks you through setup step by step, ideal if you prefer to build and customize your squad deliberately.
@@ -112,8 +112,8 @@ Use the same channel you installed from:
 | npm | `npm install -g @bradygaster/squad-cli@latest` |
 | Homebrew | `brew upgrade --cask squad` |
 | WinGet | `winget upgrade --id bradygaster.Squad --exact` |
-| Install script | Re-run the [install script](https://bradygaster.github.io/squad/docs/features/standalone-install/#macos-and-linux) |
-| Direct archive | Download the newer archive from [GitHub Releases](https://github.com/bradygaster/squad/releases/latest) |
+| Install script | Re-run the [install script](https://github.github.com/squad/docs/features/standalone-install/#macos-and-linux) |
+| Direct archive | Download the newer archive from [GitHub Releases](https://github.com/github/squad/releases/latest) |
 
 **Step 2: Update Squad-owned files in your project**
 
@@ -144,7 +144,7 @@ To install and run Squad from source for development:
 
 ```bash
 # Clone the repository
-git clone https://github.com/bradygaster/squad.git
+git clone https://github.com/github/squad.git
 cd squad
 
 # Install dependencies (npm workspaces)
@@ -442,7 +442,7 @@ When agents finish, the coordinator records follow-up work and leaves a breadcru
 
 **And it's all in git.** Anyone who clones your repo gets the team — with all their accumulated knowledge.
 
-**Each agent gets the right model.** Squad picks models quality-first by default: premium for architecture, research and review, standard for code and docs, fast for mechanical work. Opt in to the `balanced` or `economy` profile, or to the `hydrafusion` research preview with `"modelProfile": "hydrafusion"` in `.squad/config.json`. Per-agent selection works in the Copilot CLI and app; VS Code runs every agent on the one session model. See [Model Selection](https://bradygaster.github.io/squad/docs/features/model-selection/).
+**Each agent gets the right model.** Squad picks models quality-first by default: premium for architecture, research and review, standard for code and docs, fast for mechanical work. Opt in to the `balanced` or `economy` profile, or to the `hydrafusion` research preview with `"modelProfile": "hydrafusion"` in `.squad/config.json`. Per-agent selection works in the Copilot CLI and app; VS Code runs every agent on the one session model. See [Model Selection](https://github.github.com/squad/docs/features/model-selection/).
 
 ---
 
@@ -654,7 +654,7 @@ durable human handoff after exhaustion. Both workers produce drafts only;
 open, merged and closed-unmerged linked PRs suppress automatic duplicates.
 Human review and merge are always required.
 
-See [the gh-aw guide](https://bradygaster.github.io/squad/docs/guide/gh-aw/#retrospective-auto-implementation-opt-in) for the full authority model.
+See [the gh-aw guide](https://github.github.com/squad/docs/guide/gh-aw/#retrospective-auto-implementation-opt-in) for the full authority model.
 
 ### Slash commands
 
@@ -675,7 +675,7 @@ See [the gh-aw guide](https://bradygaster.github.io/squad/docs/guide/gh-aw/#retr
 
 Write a detailed team description in the issue body, then comment `/squad cast` — the issue becomes your casting brief. The more context you give, the better Squad tailors your team.
 
-📖 See [GitHub Agentic Workflows guide](https://bradygaster.github.io/squad/docs/guide/gh-aw/) for the complete setup, configuration, and usage reference.
+📖 See [GitHub Agentic Workflows guide](https://github.github.com/squad/docs/guide/gh-aw/) for the complete setup, configuration, and usage reference.
 
 ---
 

README.zh.md

@@ -40,13 +40,13 @@ git init
 | npm（所有平台，需要 Node.js 22.5+） | `npm install -g @bradygaster/squad-cli` |
 | Homebrew（macOS） | `brew install --cask bradygaster/squad/squad` |
 | WinGet（Windows） | `winget install --id bradygaster.Squad --exact` |
-| 安装脚本（macOS/Linux，无需 npm） | 查看[独立安装指南](https://bradygaster.github.io/squad/docs/features/standalone-install/) |
+| 安装脚本（macOS/Linux，无需 npm） | 查看[独立安装指南](https://github.github.com/squad/docs/features/standalone-install/) |
 
 预览版和 Insider 版也可通过 Homebrew 的 `squad-preview`、
 `squad-insider` cask，或 WinGet 的 `bradygaster.Squad.Preview`、
 `bradygaster.Squad.Insider` 软件包安装。
 
-你也可以从 [GitHub Releases](https://github.com/bradygaster/squad/releases/latest)
+你也可以从 [GitHub Releases](https://github.com/github/squad/releases/latest)
 直接下载 macOS、Linux 或 Windows 压缩包。
 
 ```bash
@@ -55,7 +55,7 @@ squad init
 
 所有方式安装的都是同一个 CLI。独立安装包自带 Node.js，无需安装
 Node.js，也无需访问 npm registry。完整要求和平台说明请参阅
-[安装指南](https://bradygaster.github.io/squad/docs/get-started/installation/)。
+[安装指南](https://github.github.com/squad/docs/get-started/installation/)。
 
 **✓ 验证：** 检查项目中是否创建了 `.squad/team.md`。
 
@@ -103,8 +103,8 @@ Squad 会提议一个团队 — 每个成员的名字都来自一个持久化的
 | npm | `npm install -g @bradygaster/squad-cli@latest` |
 | Homebrew | `brew upgrade --cask squad` |
 | WinGet | `winget upgrade --id bradygaster.Squad --exact` |
-| 安装脚本 | 重新运行[安装脚本](https://bradygaster.github.io/squad/docs/features/standalone-install/#macos-and-linux) |
-| 直接下载 | 从 [GitHub Releases](https://github.com/bradygaster/squad/releases/latest) 下载新版本 |
+| 安装脚本 | 重新运行[安装脚本](https://github.github.com/squad/docs/features/standalone-install/#macos-and-linux) |
+| 直接下载 | 从 [GitHub Releases](https://github.com/github/squad/releases/latest) 下载新版本 |
 
 **第二步：更新项目中 Squad 管理的文件**
 

SUPPORT.md

@@ -4,7 +4,7 @@
 
 This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
 
-For help or questions about using Squad, please use [GitHub Discussions](https://github.com/bradygaster/squad/discussions) on this repository.
+For help or questions about using Squad, please use [GitHub Discussions](https://github.com/github/squad/discussions) on this repository.
 
 **Squad** is under active development and maintained by GitHub staff and the community. We will do our best to respond to support, feature requests, and community questions in a timely manner.
 

docs/astro.config.mjs

@@ -8,7 +8,7 @@ import { createRequire } from 'module';
 const require = createRequire(import.meta.url);
 
 export default defineConfig({
-  site: 'https://bradygaster.github.io',
+  site: 'https://github.github.com',
   base: '/squad/',
   integrations: [sitemap()],
   vite: {

docs/demo-agentic-sdlc-walkthrough.md

@@ -519,4 +519,4 @@ Accept:   "Reply /squad plan activate..."
 
 ---
 
-*Demo created for the Squad project — [github.com/bradygaster/squad](https://github.com/bradygaster/squad)*
+*Demo created for the Squad project — [github.com/github/squad](https://github.com/github/squad)*

docs/public/robots.txt

@@ -1,4 +1,4 @@
 User-agent: *
 Allow: /
-Sitemap: https://squad.dev/sitemap-index.xml
+Sitemap: https://github.github.com/squad/sitemap-index.xml