diff --git a/.github/agents/agentic-campaign-designer.agent.md b/.github/agents/agentic-campaign-designer.agent.md
index ddcd9215b6..ecd6472fd4 100644
--- a/.github/agents/agentic-campaign-designer.agent.md
+++ b/.github/agents/agentic-campaign-designer.agent.md
@@ -260,9 +260,9 @@ gh aw campaign validate <campaign-id>
 ## Documentation Links
 
 Point users to these resources:
-- **Getting started**: https://githubnext.github.io/gh-aw/guides/campaigns/getting-started/
-- **Campaign flow**: https://githubnext.github.io/gh-aw/guides/campaigns/flow/
-- **Spec format**: https://githubnext.github.io/gh-aw/guides/campaigns/scratchpad/
+- **Getting started**: https://github.github.io/gh-aw/guides/campaigns/getting-started/
+- **Campaign flow**: https://github.github.io/gh-aw/guides/campaigns/flow/
+- **Spec format**: https://github.github.io/gh-aw/guides/campaigns/scratchpad/
 - **Workflow catalog**: https://github.com/githubnext/agentics
 
 ## Success Criteria
@@ -357,7 +357,7 @@ Agent: 🎉 Your agentic campaign spec is ready!
    gh aw campaign new security-2025 --project --owner mycompany
    ```
 
-📚 **Learn more**: https://githubnext.github.io/gh-aw/guides/campaigns/getting-started/
+📚 **Learn more**: https://github.github.io/gh-aw/guides/campaigns/getting-started/
 ```
 
 ## Remember
diff --git a/.github/aw/create-agentic-workflow.md b/.github/aw/create-agentic-workflow.md
index 762451dc80..95d2812f13 100644
--- a/.github/aw/create-agentic-workflow.md
+++ b/.github/aw/create-agentic-workflow.md
@@ -170,7 +170,7 @@ When a user requests capabilities beyond agentic workflows:
 
 Before creating workflows, read the Peli's Agent Factory documentation:
 
-- Fetch: https://githubnext.github.io/gh-aw/_llms-txt/agentic-workflows.txt
+- Fetch: https://github.github.io/gh-aw/_llms-txt/agentic-workflows.txt
 
 This llms.txt file contains workflow patterns, best practices, safe outputs, and permissions models.
 
diff --git a/.github/aw/github-agentic-workflows.md b/.github/aw/github-agentic-workflows.md
index c859c87750..50538454fc 100644
--- a/.github/aw/github-agentic-workflows.md
+++ b/.github/aw/github-agentic-workflows.md
@@ -1792,4 +1792,4 @@ gh aw logs <workflow-id>
 
 ### Documentation
 
-For complete CLI documentation, see: https://githubnext.github.io/gh-aw/setup/cli/
\ No newline at end of file
+For complete CLI documentation, see: https://github.github.io/gh-aw/setup/cli/
\ No newline at end of file
diff --git a/.github/aw/main_workflow_schema.json b/.github/aw/main_workflow_schema.json
index e7adc37d31..4a01ae4907 100644
--- a/.github/aw/main_workflow_schema.json
+++ b/.github/aw/main_workflow_schema.json
@@ -1533,7 +1533,7 @@
       ]
     },
     "env": {
-      "$comment": "See environment variable precedence documentation: https://githubnext.github.io/gh-aw/reference/environment-variables/",
+      "$comment": "See environment variable precedence documentation: https://github.github.io/gh-aw/reference/environment-variables/",
       "description": "Environment variables for the workflow",
       "oneOf": [
         {
@@ -4675,7 +4675,7 @@
     "strict": {
       "type": "boolean",
       "default": true,
-      "description": "Enable strict mode validation for enhanced security and compliance. Strict mode enforces: (1) Write Permissions - refuses contents:write, issues:write, pull-requests:write; requires safe-outputs instead, (2) Network Configuration - requires explicit network configuration with no wildcard '*' in allowed domains, (3) Action Pinning - enforces actions pinned to commit SHAs instead of tags/branches, (4) MCP Network - requires network configuration for custom MCP servers with containers, (5) Deprecated Fields - refuses deprecated frontmatter fields. Can be enabled per-workflow via 'strict: true' in frontmatter, or disabled via 'strict: false'. CLI flag takes precedence over frontmatter (gh aw compile --strict enforces strict mode). Defaults to true. See: https://githubnext.github.io/gh-aw/reference/frontmatter/#strict-mode-strict",
+      "description": "Enable strict mode validation for enhanced security and compliance. Strict mode enforces: (1) Write Permissions - refuses contents:write, issues:write, pull-requests:write; requires safe-outputs instead, (2) Network Configuration - requires explicit network configuration with no wildcard '*' in allowed domains, (3) Action Pinning - enforces actions pinned to commit SHAs instead of tags/branches, (4) MCP Network - requires network configuration for custom MCP servers with containers, (5) Deprecated Fields - refuses deprecated frontmatter fields. Can be enabled per-workflow via 'strict: true' in frontmatter, or disabled via 'strict: false'. CLI flag takes precedence over frontmatter (gh aw compile --strict enforces strict mode). Defaults to true. See: https://github.github.io/gh-aw/reference/frontmatter/#strict-mode-strict",
       "examples": [true, false]
     },
     "safe-inputs": {
diff --git a/.github/workflows/release.md b/.github/workflows/release.md
index 6a4b3b2a13..65a6395b16 100644
--- a/.github/workflows/release.md
+++ b/.github/workflows/release.md
@@ -446,7 +446,7 @@ For complete details, see [CHANGELOG](https://github.com/github/gh-aw/blob/main/
 - Lead with benefits: "GitHub MCP now supports remote mode" not "Added remote mode"
 - Be specific: "Reduced compilation time by 40%" not "Faster compilation"
 - Skip internal changes unless they have user impact
-- Use docs links: `[Learn more](https://githubnext.github.io/gh-aw/path/)`
+- Use docs links: `[Learn more](https://github.github.io/gh-aw/path/)`
 - Keep breaking changes prominent with action items
 
 ### 4. Handle Special Cases
@@ -502,8 +502,8 @@ safeoutputs/update_release(
 **WARNING**: If you don't call the MCP tool properly, the release notes will NOT be updated!
 
 **Documentation Base URLs:**
-- User docs: `https://githubnext.github.io/gh-aw/`
-- Reference: `https://githubnext.github.io/gh-aw/reference/`
-- Setup: `https://githubnext.github.io/gh-aw/setup/`
+- User docs: `https://github.github.io/gh-aw/`
+- Reference: `https://github.github.io/gh-aw/reference/`
+- Setup: `https://github.github.io/gh-aw/setup/`
 
 Verify paths exist in `docs_files.txt` before linking.
\ No newline at end of file
diff --git a/.github/workflows/shared/genaiscript.md b/.github/workflows/shared/genaiscript.md
index 756c8302f9..d55ed32a30 100644
--- a/.github/workflows/shared/genaiscript.md
+++ b/.github/workflows/shared/genaiscript.md
@@ -11,7 +11,7 @@ engine:
           echo "Error: OPENAI_API_KEY secret is not set"
           echo "The GenAIScript engine with openai:gpt-4o model requires OPENAI_API_KEY secret to be configured."
           echo "Please configure this secret in your repository settings."
-          echo "Documentation: https://githubnext.github.io/gh-aw/reference/engines/"
+          echo "Documentation: https://github.github.io/gh-aw/reference/engines/"
           exit 1
         fi
         echo "OPENAI_API_KEY secret is configured"
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 246cc88d9f..acbd5fab68 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1453,7 +1453,7 @@ strict: false      # Opt out
 - `gh aw compile --strict` still overrides frontmatter settings to force strict mode on all workflows
 - To opt out of strict mode, add `strict: false` to your workflow frontmatter
 
-See [Strict Mode Documentation](https://githubnext.github.io/gh-aw/reference/frontmatter/#strict-mode-strict) for details.
+See [Strict Mode Documentation](https://github.github.io/gh-aw/reference/frontmatter/#strict-mode-strict) for details.
 
 
 ## v0.30.5 - 2025-11-24
diff --git a/actions/setup/js/assign_issue.cjs b/actions/setup/js/assign_issue.cjs
index dcfdc87228..367584a8ad 100644
--- a/actions/setup/js/assign_issue.cjs
+++ b/actions/setup/js/assign_issue.cjs
@@ -17,7 +17,7 @@ async function main() {
 
   // Check if GH_TOKEN is present
   if (!ghToken?.trim()) {
-    const docsUrl = "https://githubnext.github.io/gh-aw/reference/safe-outputs/#assigning-issues-to-copilot";
+    const docsUrl = "https://github.github.io/gh-aw/reference/safe-outputs/#assigning-issues-to-copilot";
     core.setFailed(`GH_TOKEN environment variable is required but not set. This token is needed to assign issues. For more information on configuring Copilot tokens, see: ${docsUrl}`);
     return;
   }
diff --git a/actions/setup/js/assign_issue.test.cjs b/actions/setup/js/assign_issue.test.cjs
index a3aa656443..d77507bab7 100644
--- a/actions/setup/js/assign_issue.test.cjs
+++ b/actions/setup/js/assign_issue.test.cjs
@@ -49,7 +49,7 @@ const mockCore = {
             delete process.env.GH_TOKEN,
             await eval(`(async () => { ${assignIssueScript}; await main(); })()`),
             expect(mockCore.setFailed).toHaveBeenCalledWith(expect.stringContaining("GH_TOKEN environment variable is required but not set")),
-            expect(mockCore.setFailed).toHaveBeenCalledWith(expect.stringContaining("https://githubnext.github.io/gh-aw/reference/safe-outputs/#assigning-issues-to-copilot")),
+            expect(mockCore.setFailed).toHaveBeenCalledWith(expect.stringContaining("https://github.github.io/gh-aw/reference/safe-outputs/#assigning-issues-to-copilot")),
             expect(mockExec.exec).not.toHaveBeenCalled());
         }),
           it("should fail when GH_TOKEN is empty string", async () => {
@@ -181,7 +181,7 @@ const mockCore = {
           it("should include documentation link in error message", async () => {
             (delete process.env.GH_TOKEN, (process.env.ASSIGNEE = "test-user"), (process.env.ISSUE_NUMBER = "123"), await eval(`(async () => { ${assignIssueScript}; await main(); })()`));
             const failedCall = mockCore.setFailed.mock.calls[0][0];
-            expect(failedCall).toContain("https://githubnext.github.io/gh-aw/reference/safe-outputs/#assigning-issues-to-copilot");
+            expect(failedCall).toContain("https://github.github.io/gh-aw/reference/safe-outputs/#assigning-issues-to-copilot");
           }));
       }));
   }));
diff --git a/actions/setup/js/create_agent_session.cjs b/actions/setup/js/create_agent_session.cjs
index a224916ee6..a50d89b12c 100644
--- a/actions/setup/js/create_agent_session.cjs
+++ b/actions/setup/js/create_agent_session.cjs
@@ -132,7 +132,7 @@ async function main() {
           core.error(`Task ${index + 1}: Failed to create agent session due to authentication/permission error.`);
           core.error(`The default GITHUB_TOKEN does not have permission to create agent sessions.`);
           core.error(`You must configure a Personal Access Token (PAT) as COPILOT_GITHUB_TOKEN or GH_AW_GITHUB_TOKEN.`);
-          core.error(`See documentation: https://githubnext.github.io/gh-aw/reference/safe-outputs/#agent-task-creation-create-agent-session`);
+          core.error(`See documentation: https://github.github.io/gh-aw/reference/safe-outputs/#agent-task-creation-create-agent-session`);
         } else {
           core.error(`Task ${index + 1}: Failed to create agent session: ${errorMessage}`);
         }
diff --git a/actions/setup/js/generate_footer.test.cjs b/actions/setup/js/generate_footer.test.cjs
index 57f4522394..dee25308bc 100644
--- a/actions/setup/js/generate_footer.test.cjs
+++ b/actions/setup/js/generate_footer.test.cjs
@@ -54,7 +54,7 @@ describe("generate_footer.cjs", () => {
 
     // Create the workflow install note template
     const templatePath = path.join(testPromptsDir, "workflow_install_note.md");
-    const templateContent = "To add this workflow in your repository, run `gh aw add {workflow_source}`. See [usage guide](https://githubnext.github.io/gh-aw/guides/packaging-imports/).";
+    const templateContent = "To add this workflow in your repository, run `gh aw add {workflow_source}`. See [usage guide](https://github.github.io/gh-aw/guides/packaging-imports/).";
     fs.writeFileSync(templatePath, templateContent, "utf8");
 
     // Set environment to use test directory
@@ -136,7 +136,7 @@ describe("generate_footer.cjs", () => {
       const result = generateFooter("Test Workflow", "https://github.com/test/repo/actions/runs/123", "owner/repo/workflow.md@main", "https://github.com/owner/repo/blob/main/workflow.md", undefined, undefined, undefined);
 
       expect(result).toContain("gh aw add owner/repo/workflow.md@main");
-      expect(result).toContain("See [usage guide](https://githubnext.github.io/gh-aw/guides/packaging-imports/)");
+      expect(result).toContain("See [usage guide](https://github.github.io/gh-aw/guides/packaging-imports/)");
     });
 
     it("should not include installation instructions when source is empty", () => {
diff --git a/actions/setup/js/update_issue_campaign_generator.test.cjs b/actions/setup/js/update_issue_campaign_generator.test.cjs
index c774906a0e..2a859080ce 100644
--- a/actions/setup/js/update_issue_campaign_generator.test.cjs
+++ b/actions/setup/js/update_issue_campaign_generator.test.cjs
@@ -30,7 +30,7 @@ describe("update_issue.cjs - campaign generator payload", () => {
     const { success, data } = updateIssueModule.buildIssueUpdateData(
       {
         // This is representative of how the campaign generator should update the triggering issue.
-        body: "## Campaign setup status\n\n**Status:** Ready for PR review\n\nDocs: https://githubnext.github.io/gh-aw/guides/campaigns/getting-started/\n",
+        body: "## Campaign setup status\n\n**Status:** Ready for PR review\n\nDocs: https://github.github.io/gh-aw/guides/campaigns/getting-started/\n",
       },
       {}
     );
diff --git a/actions/setup/md/workflow_install_note.md b/actions/setup/md/workflow_install_note.md
index 297e0126fa..2061e3e2fb 100644
--- a/actions/setup/md/workflow_install_note.md
+++ b/actions/setup/md/workflow_install_note.md
@@ -1 +1 @@
-To add this workflow in your repository, run `gh aw add {workflow_source}`. See [usage guide](https://githubnext.github.io/gh-aw/guides/packaging-imports/).
\ No newline at end of file
+To add this workflow in your repository, run `gh aw add {workflow_source}`. See [usage guide](https://github.github.io/gh-aw/guides/packaging-imports/).
\ No newline at end of file
diff --git a/cmd/gh-aw/main.go b/cmd/gh-aw/main.go
index 29f701be3e..47f2882462 100644
--- a/cmd/gh-aw/main.go
+++ b/cmd/gh-aw/main.go
@@ -448,7 +448,7 @@ Use "` + string(constants.CLIExtensionPrefix) + ` help all" to show help for all
 				// Print footer
 				fmt.Fprintln(os.Stderr, console.FormatInfoMessage("═══════════════════════════════════════════════════════════════"))
 				fmt.Fprintln(os.Stderr, "")
-				fmt.Fprintln(os.Stderr, console.FormatInfoMessage("For more information, visit: https://githubnext.github.io/gh-aw/"))
+				fmt.Fprintln(os.Stderr, console.FormatInfoMessage("For more information, visit: https://github.github.io/gh-aw/"))
 				return nil
 			}
 
diff --git a/docs/slides/index.md b/docs/slides/index.md
index 78c97e845a..22715055a8 100644
--- a/docs/slides/index.md
+++ b/docs/slides/index.md
@@ -200,7 +200,7 @@ npx --yes @github/copilot -i "activate https://raw.githubusercontent.com/github/
 
 > Built with AI agents in mind from day 0
 
-> Quick Start: https://githubnext.github.io/gh-aw/setup/quick-start/
+> Quick Start: https://github.github.io/gh-aw/setup/quick-start/
 
 ---
 
@@ -563,6 +563,6 @@ Analyze issue and create implementation PR
 - Network Configuration Reference
 - Safe Outputs Reference
 
-**Visit:** https://githubnext.github.io/gh-aw/guides/security/
+**Visit:** https://github.github.io/gh-aw/guides/security/
 
 Security is foundational to GitHub Agentic Workflows. We continuously evolve our security controls and welcome community feedback.
diff --git a/docs/src/content/docs/blog/2026-01-12-welcome-to-pelis-agent-factory.md b/docs/src/content/docs/blog/2026-01-12-welcome-to-pelis-agent-factory.md
index a7aef1e874..bc88d2713f 100644
--- a/docs/src/content/docs/blog/2026-01-12-welcome-to-pelis-agent-factory.md
+++ b/docs/src/content/docs/blog/2026-01-12-welcome-to-pelis-agent-factory.md
@@ -28,7 +28,7 @@ Let's explore together!
 
 ## What Is Peli's Agent Factory?
 
-Peli's factory is a collection of [**automated agentic workflows**](https://githubnext.github.io/gh-aw) we use in practice. We have built and operated **over 100 automated agentic workflows** within the [`github/gh-aw`](https://github.com/github/gh-aw) repository and its companion [`githubnext/agentics`](https://github.com/githubnext/agentics) collection. These were used mostly in the context of the [`github/gh-aw`](https://github.com/github/gh-aw) project itself, but some have also been applied at scale in GitHub internal repositories. These weren't hypothetical demos - they were working agents that:
+Peli's factory is a collection of [**automated agentic workflows**](https://github.github.io/gh-aw) we use in practice. We have built and operated **over 100 automated agentic workflows** within the [`github/gh-aw`](https://github.com/github/gh-aw) repository and its companion [`githubnext/agentics`](https://github.com/githubnext/agentics) collection. These were used mostly in the context of the [`github/gh-aw`](https://github.com/github/gh-aw) project itself, but some have also been applied at scale in GitHub internal repositories. These weren't hypothetical demos - they were working agents that:
 
 - [Triage incoming issues](/gh-aw/blog/2026-01-13-meet-the-workflows/)
 - [Diagnose CI failures](/gh-aw/blog/2026-01-13-meet-the-workflows-quality-hygiene/)
@@ -101,13 +101,13 @@ We'll dive deeper into these lessons in upcoming articles.
 
 ## Try It Yourself
 
-Want to start with automated agentic workflows on GitHub? See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/).
+Want to start with automated agentic workflows on GitHub? See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/).
 
 ## Learn More
 
 - **[Meet the Workflows](/gh-aw/blog/2026-01-13-meet-the-workflows/)** - The 19-part tour of the workflows
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Credits
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-advanced-analytics.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-advanced-analytics.md
index 3a3df0f53e..42b7d49b17 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-advanced-analytics.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-advanced-analytics.md
@@ -69,12 +69,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/prompt-
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/copilot-agent-analysis.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs,recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs,recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Project Coordination Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md
index 0067fda641..d265882d14 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md
@@ -41,7 +41,7 @@ These workflows implement patterns like epic issues, progress tracking, and dead
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Plan Command:**
 
@@ -55,12 +55,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/plan.md
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/discussion-task-miner.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-improvement.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-improvement.md
index 34356233f7..ddfad9238d 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-improvement.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-improvement.md
@@ -105,7 +105,7 @@ This is the future of code quality: not periodic cleanup sprints, but continuous
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Go Fan:**
 
@@ -131,7 +131,7 @@ gh aw add https://github.com/github/gh-aw/blob/main/.github/workflows/functional
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/repository-quality-improver.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Next Up: Continuous Documentation
 
@@ -141,8 +141,8 @@ Continue reading: [Continuous Documentation Workflows →](/gh-aw/blog/2026-01-1
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-refactoring.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-refactoring.md
index 5f7dfd9913..1c578bca8d 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-refactoring.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-refactoring.md
@@ -68,7 +68,7 @@ These workflows demonstrate how AI agents can continuously maintain institutiona
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Semantic Function Refactor:**
 
@@ -82,7 +82,7 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/semanti
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/go-pattern-detector.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Next Up: Continuous Style
 
@@ -92,8 +92,8 @@ Continue reading: [Meet the Workflows: Continuous Style →](/gh-aw/blog/2026-01
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-simplicity.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-simplicity.md
index cc4aca96a5..873f01e880 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-simplicity.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-simplicity.md
@@ -56,7 +56,7 @@ The workflows never take a day off, never get tired, and never let technical deb
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Automatic Code Simplifier:**
 
@@ -70,7 +70,7 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/code-si
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/duplicate-code-detector.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Next Up: Continuous Refactoring
 
@@ -80,8 +80,8 @@ Continue reading: [Continuous Refactoring →](/gh-aw/blog/2026-01-13-meet-the-w
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-style.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-style.md
index c2056f3548..66aa95f0ac 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-style.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-style.md
@@ -52,7 +52,7 @@ You can add this workflow to your own repository and remix it as follows:
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/terminal-stylist.md
 ```
 
-Then edit and remix the workflow specification to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specification to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Next Up: Continuous Improvement
 
@@ -62,7 +62,7 @@ Continue reading: [Continuous Improvement Workflows →](/gh-aw/blog/2026-01-13-
 
 ## Learn More
 
-Learn more about **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)**, try the **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** guide, and explore **[Charmbracelet](https://charm.sh/)**, the terminal UI ecosystem referenced by the Terminal Stylist.
+Learn more about **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)**, try the **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** guide, and explore **[Charmbracelet](https://charm.sh/)**, the terminal UI ecosystem referenced by the Terminal Stylist.
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-creative-culture.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-creative-culture.md
index 1638ee50d8..5b3bd23360 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-creative-culture.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-creative-culture.md
@@ -48,7 +48,7 @@ These communication workflows help build team cohesion and remind us that work c
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Daily Team Status:**
 
@@ -80,12 +80,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/weekly-
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-repo-chronicle.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Summon an Agent on Demand
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-documentation.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-documentation.md
index 2bb0cb5641..3feea6151a 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-documentation.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-documentation.md
@@ -52,7 +52,7 @@ In this collection of agents, we took a heterogeneous approach - some workflows
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Daily Documentation Updater:**
 
@@ -96,12 +96,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-m
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/blog-auditor.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Issue & PR Management Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-interactive-chatops.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-interactive-chatops.md
index 3b40ece17a..5fc2ec6b02 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-interactive-chatops.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-interactive-chatops.md
@@ -40,7 +40,7 @@ The Grumpy Reviewer gave us surprisingly valuable feedback with a side of sass (
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Q:**
 
@@ -60,12 +60,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/grumpy-
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/workflow-generator.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Testing & Validation Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-issue-management.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-issue-management.md
index ca99367a43..9a263f339f 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-issue-management.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-issue-management.md
@@ -46,7 +46,7 @@ Issue and PR management workflows don't replace GitHub's features; they enhance
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Issue Arborist:**
 
@@ -78,12 +78,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/sub-iss
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/issue-template-optimizer.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Fault Investigation Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-metrics-analytics.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-metrics-analytics.md
index 5d80d43b16..ac0fb83ddd 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-metrics-analytics.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-metrics-analytics.md
@@ -38,7 +38,7 @@ These workflows taught us that observability isn't optional when you're running
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Metrics Collector:**
 
@@ -58,12 +58,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/portfol
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/audit-workflows.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Operations & Release Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-multi-phase.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-multi-phase.md
index 8c377c2650..5871179370 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-multi-phase.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-multi-phase.md
@@ -40,7 +40,7 @@ These workflows prove that AI agents can handle complex, long-running projects w
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Daily Backlog Burner:**
 
@@ -72,12 +72,12 @@ gh aw add githubnext/agentics/workflows/daily-accessibility-review.md
 gh aw add githubnext/agentics/workflows/pr-fix.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Organization & Cross-Repo Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-operations-release.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-operations-release.md
index df9031cc75..2732fdc396 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-operations-release.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-operations-release.md
@@ -40,7 +40,7 @@ The Daily Workflow Updater taught us that maintenance is a perfect use case for
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Release:**
 
@@ -60,12 +60,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/changes
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-workflow-updater.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Security-related Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-organization.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-organization.md
index 4c85b2ac13..75446424fd 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-organization.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-organization.md
@@ -36,7 +36,7 @@ Scaling agents across an entire organization changes the game. The Org Health Re
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Org Health Report:**
 
@@ -56,12 +56,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/stale-r
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/ubuntu-image-analyzer.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Advanced Analytics & ML Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-quality-hygiene.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-quality-hygiene.md
index b5743bb813..201cdb997f 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-quality-hygiene.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-quality-hygiene.md
@@ -44,7 +44,7 @@ The CI Doctor has inspired a growing range of similar workflows inside GitHub, w
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **CI Doctor:**
 
@@ -64,12 +64,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/schema-
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/breaking-change-checker.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Metrics & Analytics Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-security-compliance.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-security-compliance.md
index fa559b6e16..7475e6606e 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-security-compliance.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-security-compliance.md
@@ -46,7 +46,7 @@ The Static Analysis Report runs a comprehensive security audit daily using indus
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Security Compliance:**
 
@@ -78,12 +78,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-m
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/static-analysis-report.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Teamwork & Culture Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-testing-validation.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-testing-validation.md
index 056e58243f..670dca91f2 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-testing-validation.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-testing-validation.md
@@ -54,7 +54,7 @@ These workflows embody the principle: **trust but verify**. Just because it work
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **Daily Testify Uber Super Expert:**
 
@@ -98,12 +98,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/ci-coac
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/workflow-health-manager.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Monitoring the Monitors
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-tool-infrastructure.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-tool-infrastructure.md
index dcc04621e4..ba031614a5 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-tool-infrastructure.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows-tool-infrastructure.md
@@ -38,7 +38,7 @@ These workflows provide visibility into the invisible.
 
 ## Using These Workflows
 
-You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/), then run one of the following:
+You can add these workflows to your own repository and remix them. Get going with our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/), then run one of the following:
 
 **MCP Inspector:**
 
@@ -58,12 +58,12 @@ gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/github-
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/agent-performance-analyzer.md
 ```
 
-Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specifications to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ## Next Up: Multi-Phase Improver Workflows
 
diff --git a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows.md b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows.md
index f9cd26cb59..96922da765 100644
--- a/docs/src/content/docs/blog/2026-01-13-meet-the-workflows.md
+++ b/docs/src/content/docs/blog/2026-01-13-meet-the-workflows.md
@@ -88,7 +88,7 @@ You can add this workflow to your own repository and remix it as follows:
 gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/issue-triage-agent.md
 ```
 
-Then edit and remix the workflow specification to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
+Then edit and remix the workflow specification to meet your needs, recompile using `gh aw compile`, and push to your repository. See our [Quick Start](https://github.github.io/gh-aw/setup/quick-start/) for further installation and setup instructions.
 
 ## Next Up: Code Quality & Refactoring Workflows
 
@@ -98,8 +98,8 @@ Continue reading: [Continuous Simplicity →](/gh-aw/blog/2026-01-13-meet-the-wo
 
 ## Learn More
 
-- **[GitHub Agentic Workflows](https://githubnext.github.io/gh-aw/)** - The technology behind the workflows
-- **[Quick Start](https://githubnext.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
+- **[GitHub Agentic Workflows](https://github.github.io/gh-aw/)** - The technology behind the workflows
+- **[Quick Start](https://github.github.io/gh-aw/setup/quick-start/)** - How to write and compile workflows
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-01-21-twelve-lessons.md b/docs/src/content/docs/blog/2026-01-21-twelve-lessons.md
index 82ed71b0b9..717d1a8c16 100644
--- a/docs/src/content/docs/blog/2026-01-21-twelve-lessons.md
+++ b/docs/src/content/docs/blog/2026-01-21-twelve-lessons.md
@@ -35,7 +35,7 @@ No single agent can do everything - and that's perfectly fine. A collection of f
 
 ### Guardrails Enable Innovation
 
-Something counter-intuitive we discovered is that strict constraints make it *easier* to experiment. [Safe outputs](https://githubnext.github.io/gh-aw/reference/safe-outputs/), limited permissions, allowlisted tools - they don't slow us down. They give us the confidence to move fast because we know the blast radius of any failure.
+Something counter-intuitive we discovered is that strict constraints make it *easier* to experiment. [Safe outputs](https://github.github.io/gh-aw/reference/safe-outputs/), limited permissions, allowlisted tools - they don't slow us down. They give us the confidence to move fast because we know the blast radius of any failure.
 
 With clear boundaries in place, we can prototype new agents without worrying about breaking production. Safe outputs prevent agents from accidentally deleting code or closing critical issues. Network allowlists ensure agents can't leak data to unauthorized services. These guardrails give us permission to innovate boldly.
 
diff --git a/docs/src/content/docs/blog/2026-01-27-operational-patterns.md b/docs/src/content/docs/blog/2026-01-27-operational-patterns.md
index 55e220666c..13e8b5a7c4 100644
--- a/docs/src/content/docs/blog/2026-01-27-operational-patterns.md
+++ b/docs/src/content/docs/blog/2026-01-27-operational-patterns.md
@@ -76,7 +76,7 @@ Here are our tips!
 - Add help text for `/command help`
 - Use cache-memory to track command history
 
-**Learn more**: [ChatOps Examples](https://githubnext.github.io/gh-aw/examples/comment-triggered/chatops/)
+**Learn more**: [ChatOps Examples](https://github.github.io/gh-aw/examples/comment-triggered/chatops/)
 
 ---
 
@@ -124,7 +124,7 @@ Here are our tips!
 - Include progress reports in PR descriptions
 - Allow human intervention at any phase
 
-**Learn more**: [DailyOps Examples](https://githubnext.github.io/gh-aw/examples/scheduled/dailyops/)
+**Learn more**: [DailyOps Examples](https://github.github.io/gh-aw/examples/scheduled/dailyops/)
 
 ---
 
@@ -174,7 +174,7 @@ Here are our tips!
 - Track triage accuracy
 - Update classification rules based on feedback
 
-**Learn more**: [IssueOps Examples](https://githubnext.github.io/gh-aw/examples/issue-pr-events/issueops/)
+**Learn more**: [IssueOps Examples](https://github.github.io/gh-aw/examples/issue-pr-events/issueops/)
 
 ---
 
@@ -223,7 +223,7 @@ Here are our tips!
 - Avoid label proliferation
 - Use label descriptions
 
-**Learn more**: [LabelOps Examples](https://githubnext.github.io/gh-aw/examples/issue-pr-events/labelops/)
+**Learn more**: [LabelOps Examples](https://github.github.io/gh-aw/examples/issue-pr-events/labelops/)
 
 ---
 
@@ -273,7 +273,7 @@ Here are our tips!
 - Allow manual overrides
 - Track automation accuracy
 
-**Learn more**: [ProjectOps Examples](https://githubnext.github.io/gh-aw/examples/issue-pr-events/projectops/)
+**Learn more**: [ProjectOps Examples](https://github.github.io/gh-aw/examples/issue-pr-events/projectops/)
 
 ---
 
@@ -336,7 +336,7 @@ Here are our tips!
 - Include acceptance criteria
 - Review and iterate
 
-**Learn more**: [ResearchPlanAssign Guide](https://githubnext.github.io/gh-aw/guides/researchplanassign/)
+**Learn more**: [ResearchPlanAssign Guide](https://github.github.io/gh-aw/guides/researchplanassign/)
 
 ---
 
@@ -387,7 +387,7 @@ Here are our tips!
 - Batch operations efficiently
 - Monitor cross-repo dependencies
 
-**Learn more**: [MultiRepoOps Guide](https://githubnext.github.io/gh-aw/guides/multirepoops/)
+**Learn more**: [MultiRepoOps Guide](https://github.github.io/gh-aw/guides/multirepoops/)
 
 ---
 
@@ -426,7 +426,7 @@ Here are our tips!
 - Set up appropriate notifications
 - Plan for eventual migration if successful
 
-**Learn more**: [SideRepoOps Guide](https://githubnext.github.io/gh-aw/guides/siderepoops/)
+**Learn more**: [SideRepoOps Guide](https://github.github.io/gh-aw/guides/siderepoops/)
 
 ---
 
@@ -451,7 +451,7 @@ These workflows do the following:
 5. Capture and validate outputs
 6. Delete trial repo or keep for reference
 
-**Learn more**: [TrialOps Guide](https://githubnext.github.io/gh-aw/guides/trialops/)
+**Learn more**: [TrialOps Guide](https://github.github.io/gh-aw/guides/trialops/)
 
 ---
 
diff --git a/docs/src/content/docs/blog/2026-02-02-security-lessons.md b/docs/src/content/docs/blog/2026-02-02-security-lessons.md
index 72b9d1556f..e3c7d4b6b9 100644
--- a/docs/src/content/docs/blog/2026-02-02-security-lessons.md
+++ b/docs/src/content/docs/blog/2026-02-02-security-lessons.md
@@ -343,9 +343,9 @@ The factory experienced a few security-adjacent incidents that taught valuable l
 
 For deeper technical details, see:
 
-- [Security Architecture](https://githubnext.github.io/gh-aw/introduction/architecture/)
-- [Security Guide](https://githubnext.github.io/gh-aw/guides/security/)
-- [Safe Outputs Documentation](https://githubnext.github.io/gh-aw/reference/safe-outputs/)
+- [Security Architecture](https://github.github.io/gh-aw/introduction/architecture/)
+- [Security Guide](https://github.github.io/gh-aw/guides/security/)
+- [Safe Outputs Documentation](https://github.github.io/gh-aw/reference/safe-outputs/)
 
 ## Defense in Depth
 
diff --git a/docs/src/content/docs/blog/2026-02-08-authoring-workflows.md b/docs/src/content/docs/blog/2026-02-08-authoring-workflows.md
index 028ec7a4e8..a1e2e1d47c 100644
--- a/docs/src/content/docs/blog/2026-02-08-authoring-workflows.md
+++ b/docs/src/content/docs/blog/2026-02-08-authoring-workflows.md
@@ -555,10 +555,10 @@ Browse the factory for inspiration:
 
 ### Documentation
 
-- [Workflow Reference](https://githubnext.github.io/gh-aw/reference/workflows/)
-- [Safe Outputs Guide](https://githubnext.github.io/gh-aw/reference/safe-outputs/)
-- [Tools Reference](https://githubnext.github.io/gh-aw/reference/tools/)
-- [Examples Gallery](https://githubnext.github.io/gh-aw/examples/)
+- [Workflow Reference](https://github.github.io/gh-aw/reference/workflows/)
+- [Safe Outputs Guide](https://github.github.io/gh-aw/reference/safe-outputs/)
+- [Tools Reference](https://github.github.io/gh-aw/reference/tools/)
+- [Examples Gallery](https://github.github.io/gh-aw/examples/)
 
 ### Community
 
diff --git a/docs/src/content/docs/reference/frontmatter-full.md b/docs/src/content/docs/reference/frontmatter-full.md
index 5dbbf2bfd1..91b65fc21a 100644
--- a/docs/src/content/docs/reference/frontmatter-full.md
+++ b/docs/src/content/docs/reference/frontmatter-full.md
@@ -3466,7 +3466,7 @@ bots: []
 # per-workflow via 'strict: true' in frontmatter, or disabled via 'strict: false'.
 # CLI flag takes precedence over frontmatter (gh aw compile --strict enforces
 # strict mode). Defaults to true. See:
-# https://githubnext.github.io/gh-aw/reference/frontmatter/#strict-mode-strict
+# https://github.github.io/gh-aw/reference/frontmatter/#strict-mode-strict
 # (optional)
 strict: true
 
diff --git a/docs/src/content/docs/setup/quick-start.md b/docs/src/content/docs/setup/quick-start.md
index ddc7b31705..56d7c5398a 100644
--- a/docs/src/content/docs/setup/quick-start.md
+++ b/docs/src/content/docs/setup/quick-start.md
@@ -11,7 +11,7 @@ In this guide you will add the automated [**Daily Repo Status Report**](https://
 
 Remember the aim here is _automated AI_: to install something that will run _automatically_ every day, in the context of your repository, and create a fresh status report issue in your repository without any further manual intervention. If you're familiar with GitHub Actions, you will be aware of the power of automation.
 
-There are hundreds of other ways to use GitHub Agentic Workflows, which you can explore in [Peli's Agent Factory](https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/). This workflow is just the start of what's possible.
+There are hundreds of other ways to use GitHub Agentic Workflows, which you can explore in [Peli's Agent Factory](https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/). This workflow is just the start of what's possible.
 
 ## Prerequisites
 
@@ -90,7 +90,7 @@ Some ideas for customization:
 - Request analysis of ways the repository could be modernized or simplified
 - And much more!
 
-Alternatively, you can browse some of the sample workflows in [Peli's Agent Factory](https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/) and add them to your repository using `gh aw add <workflow-spec>`, or remix them to create your own workflows.
+Alternatively, you can browse some of the sample workflows in [Peli's Agent Factory](https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/) and add them to your repository using `gh aw add <workflow-spec>`, or remix them to create your own workflows.
 
 ## What's next?
 
diff --git a/install.md b/install.md
index ddb10862f2..cb26b1b54d 100644
--- a/install.md
+++ b/install.md
@@ -110,6 +110,6 @@ After successful initialization, the user can:
 ## Reference
 
 - **Installation script**: `https://raw.githubusercontent.com/github/gh-aw/main/install-gh-aw.sh`
-- **Documentation**: `https://githubnext.github.io/gh-aw/`
+- **Documentation**: `https://github.github.io/gh-aw/`
 - **Repository**: `https://github.com/github/gh-aw`
 - **Detailed setup guide**: See `install.md` in the gh-aw repository
diff --git a/pkg/cli/add_interactive_orchestrator.go b/pkg/cli/add_interactive_orchestrator.go
index 9179f15034..5c7fb0ccc5 100644
--- a/pkg/cli/add_interactive_orchestrator.go
+++ b/pkg/cli/add_interactive_orchestrator.go
@@ -238,6 +238,6 @@ func (c *AddInteractiveConfig) showFinalInstructions() {
 	fmt.Fprintln(os.Stderr, console.FormatCommandMessage(fmt.Sprintf("  %s run <workflow>  # Trigger a workflow", string(constants.CLIExtensionPrefix))))
 	fmt.Fprintln(os.Stderr, console.FormatCommandMessage(fmt.Sprintf("  %s logs            # View workflow logs", string(constants.CLIExtensionPrefix))))
 	fmt.Fprintln(os.Stderr, "")
-	fmt.Fprintln(os.Stderr, "Learn more at: https://githubnext.github.io/gh-aw/")
+	fmt.Fprintln(os.Stderr, "Learn more at: https://github.github.io/gh-aw/")
 	fmt.Fprintln(os.Stderr, "")
 }
diff --git a/pkg/cli/commands.go b/pkg/cli/commands.go
index a7feeee577..e4307ab402 100644
--- a/pkg/cli/commands.go
+++ b/pkg/cli/commands.go
@@ -248,6 +248,6 @@ Be clear and specific about what the AI should accomplish.
 ## Notes
 
 - Run ` + "`" + string(constants.CLIExtensionPrefix) + " compile`" + ` to generate the GitHub Actions workflow
-- See https://githubnext.github.io/gh-aw/ for complete configuration options and tools documentation
+- See https://github.github.io/gh-aw/ for complete configuration options and tools documentation
 `
 }
diff --git a/pkg/cli/templates/create-agentic-workflow.md b/pkg/cli/templates/create-agentic-workflow.md
index 762451dc80..95d2812f13 100644
--- a/pkg/cli/templates/create-agentic-workflow.md
+++ b/pkg/cli/templates/create-agentic-workflow.md
@@ -170,7 +170,7 @@ When a user requests capabilities beyond agentic workflows:
 
 Before creating workflows, read the Peli's Agent Factory documentation:
 
-- Fetch: https://githubnext.github.io/gh-aw/_llms-txt/agentic-workflows.txt
+- Fetch: https://github.github.io/gh-aw/_llms-txt/agentic-workflows.txt
 
 This llms.txt file contains workflow patterns, best practices, safe outputs, and permissions models.
 
diff --git a/pkg/cli/templates/github-agentic-workflows.md b/pkg/cli/templates/github-agentic-workflows.md
index c859c87750..50538454fc 100644
--- a/pkg/cli/templates/github-agentic-workflows.md
+++ b/pkg/cli/templates/github-agentic-workflows.md
@@ -1792,4 +1792,4 @@ gh aw logs <workflow-id>
 
 ### Documentation
 
-For complete CLI documentation, see: https://githubnext.github.io/gh-aw/setup/cli/
\ No newline at end of file
+For complete CLI documentation, see: https://github.github.io/gh-aw/setup/cli/
\ No newline at end of file
diff --git a/pkg/parser/schemas/main_workflow_schema.json b/pkg/parser/schemas/main_workflow_schema.json
index 4b91479608..9f52572b4d 100644
--- a/pkg/parser/schemas/main_workflow_schema.json
+++ b/pkg/parser/schemas/main_workflow_schema.json
@@ -1842,7 +1842,7 @@
       ]
     },
     "env": {
-      "$comment": "See environment variable precedence documentation: https://githubnext.github.io/gh-aw/reference/environment-variables/",
+      "$comment": "See environment variable precedence documentation: https://github.github.io/gh-aw/reference/environment-variables/",
       "description": "Environment variables for the workflow",
       "oneOf": [
         {
@@ -5952,7 +5952,7 @@
       "type": "boolean",
       "default": true,
       "$comment": "Strict mode enforces several security constraints that are validated in Go code (pkg/workflow/strict_mode_validation.go) rather than JSON Schema: (1) Write Permissions + Safe Outputs: When strict=true AND permissions contains write values (contents:write, issues:write, pull-requests:write), safe-outputs must be configured. This relationship is too complex for JSON Schema as it requires checking if ANY permission property has a 'write' value. (2) Network Requirements: When strict=true, the 'network' field must be present and cannot contain standalone wildcard '*' (but patterns like '*.example.com' ARE allowed). (3) MCP Container Network: Custom MCP servers with containers require explicit network configuration. (4) Action Pinning: Actions must be pinned to commit SHAs. These are enforced during compilation via validateStrictMode().",
-      "description": "Enable strict mode validation for enhanced security and compliance. Strict mode enforces: (1) Write Permissions - refuses contents:write, issues:write, pull-requests:write; requires safe-outputs instead, (2) Network Configuration - requires explicit network configuration with no standalone wildcard '*' in allowed domains (patterns like '*.example.com' are allowed), (3) Action Pinning - enforces actions pinned to commit SHAs instead of tags/branches, (4) MCP Network - requires network configuration for custom MCP servers with containers, (5) Deprecated Fields - refuses deprecated frontmatter fields. Can be enabled per-workflow via 'strict: true' in frontmatter, or disabled via 'strict: false'. CLI flag takes precedence over frontmatter (gh aw compile --strict enforces strict mode). Defaults to true. See: https://githubnext.github.io/gh-aw/reference/frontmatter/#strict-mode-strict",
+      "description": "Enable strict mode validation for enhanced security and compliance. Strict mode enforces: (1) Write Permissions - refuses contents:write, issues:write, pull-requests:write; requires safe-outputs instead, (2) Network Configuration - requires explicit network configuration with no standalone wildcard '*' in allowed domains (patterns like '*.example.com' are allowed), (3) Action Pinning - enforces actions pinned to commit SHAs instead of tags/branches, (4) MCP Network - requires network configuration for custom MCP servers with containers, (5) Deprecated Fields - refuses deprecated frontmatter fields. Can be enabled per-workflow via 'strict: true' in frontmatter, or disabled via 'strict: false'. CLI flag takes precedence over frontmatter (gh aw compile --strict enforces strict mode). Defaults to true. See: https://github.github.io/gh-aw/reference/frontmatter/#strict-mode-strict",
       "examples": [true, false]
     },
     "safe-inputs": {
diff --git a/pkg/workflow/agent_validation.go b/pkg/workflow/agent_validation.go
index c892e8ed5e..37795903eb 100644
--- a/pkg/workflow/agent_validation.go
+++ b/pkg/workflow/agent_validation.go
@@ -154,7 +154,7 @@ func (c *Compiler) validateWebSearchSupport(tools map[string]any, engine CodingA
 
 	// web-search is specified, check if the engine supports it
 	if !engine.SupportsWebSearch() {
-		fmt.Fprintln(os.Stderr, console.FormatWarningMessage(fmt.Sprintf("Engine '%s' does not support the web-search tool. See https://githubnext.github.io/gh-aw/guides/web-search/ for alternatives.", engine.GetID())))
+		fmt.Fprintln(os.Stderr, console.FormatWarningMessage(fmt.Sprintf("Engine '%s' does not support the web-search tool. See https://github.github.io/gh-aw/guides/web-search/ for alternatives.", engine.GetID())))
 		c.IncrementWarningCount()
 	}
 }
diff --git a/pkg/workflow/claude_engine.go b/pkg/workflow/claude_engine.go
index beabb6a28a..6384fad143 100644
--- a/pkg/workflow/claude_engine.go
+++ b/pkg/workflow/claude_engine.go
@@ -69,7 +69,7 @@ func (e *ClaudeEngine) GetInstallationSteps(workflowData *WorkflowData) []GitHub
 	// Define engine configuration for shared validation
 	config := EngineInstallConfig{
 		Secrets:         []string{"CLAUDE_CODE_OAUTH_TOKEN", "ANTHROPIC_API_KEY"},
-		DocsURL:         "https://githubnext.github.io/gh-aw/reference/engines/#anthropic-claude-code",
+		DocsURL:         "https://github.github.io/gh-aw/reference/engines/#anthropic-claude-code",
 		NpmPackage:      "@anthropic-ai/claude-code",
 		Version:         string(constants.DefaultClaudeCodeVersion),
 		Name:            "Claude Code",
diff --git a/pkg/workflow/codex_engine.go b/pkg/workflow/codex_engine.go
index b76557b077..2985654d38 100644
--- a/pkg/workflow/codex_engine.go
+++ b/pkg/workflow/codex_engine.go
@@ -78,7 +78,7 @@ func (e *CodexEngine) GetInstallationSteps(workflowData *WorkflowData) []GitHubA
 	// Use base installation steps (secret validation + npm install)
 	steps := GetBaseInstallationSteps(EngineInstallConfig{
 		Secrets:    []string{"CODEX_API_KEY", "OPENAI_API_KEY"},
-		DocsURL:    "https://githubnext.github.io/gh-aw/reference/engines/#openai-codex",
+		DocsURL:    "https://github.github.io/gh-aw/reference/engines/#openai-codex",
 		NpmPackage: "@openai/codex",
 		Version:    string(constants.DefaultCodexVersion),
 		Name:       "Codex",
diff --git a/pkg/workflow/compiler.go b/pkg/workflow/compiler.go
index b4d5d15cdc..5e724cb702 100644
--- a/pkg/workflow/compiler.go
+++ b/pkg/workflow/compiler.go
@@ -267,7 +267,7 @@ func (c *Compiler) CompileWorkflowData(workflowData *WorkflowData, markdownPath
 		for _, toolset := range originalToolsets {
 			if toolset == "projects" {
 				fmt.Fprintln(os.Stderr, console.FormatInfoMessage("The 'projects' toolset requires a GitHub token with organization Projects permissions."))
-				fmt.Fprintln(os.Stderr, console.FormatInfoMessage("See: https://githubnext.github.io/gh-aw/reference/tokens/#gh_aw_project_github_token-github-projects-v2"))
+				fmt.Fprintln(os.Stderr, console.FormatInfoMessage("See: https://github.github.io/gh-aw/reference/tokens/#gh_aw_project_github_token-github-projects-v2"))
 				break
 			}
 		}
diff --git a/pkg/workflow/copilot_engine_installation.go b/pkg/workflow/copilot_engine_installation.go
index a923210368..e7890630eb 100644
--- a/pkg/workflow/copilot_engine_installation.go
+++ b/pkg/workflow/copilot_engine_installation.go
@@ -49,7 +49,7 @@ func (e *CopilotEngine) GetInstallationSteps(workflowData *WorkflowData) []GitHu
 	// Define engine configuration for shared validation
 	config := EngineInstallConfig{
 		Secrets:         []string{"COPILOT_GITHUB_TOKEN"},
-		DocsURL:         "https://githubnext.github.io/gh-aw/reference/engines/#github-copilot-default",
+		DocsURL:         "https://github.github.io/gh-aw/reference/engines/#github-copilot-default",
 		NpmPackage:      "@github/copilot",
 		Version:         string(constants.DefaultCopilotVersion),
 		Name:            "GitHub Copilot CLI",
diff --git a/pkg/workflow/search_integration_test.go b/pkg/workflow/search_integration_test.go
index ca9154c73f..96b4fab9aa 100644
--- a/pkg/workflow/search_integration_test.go
+++ b/pkg/workflow/search_integration_test.go
@@ -72,7 +72,7 @@ Search the web for information.
 		t.Errorf("Expected warning about web-search not being supported, but got: %s", stderrOutput)
 	}
 
-	if !strings.Contains(stderrOutput, "https://githubnext.github.io/gh-aw/guides/web-search/") {
+	if !strings.Contains(stderrOutput, "https://github.github.io/gh-aw/guides/web-search/") {
 		t.Errorf("Expected warning to include documentation link, but got: %s", stderrOutput)
 	}
 
diff --git a/pkg/workflow/secret_validation_test.go b/pkg/workflow/secret_validation_test.go
index ae25b56570..4f0a599363 100644
--- a/pkg/workflow/secret_validation_test.go
+++ b/pkg/workflow/secret_validation_test.go
@@ -20,13 +20,13 @@ func TestGenerateSecretValidationStep(t *testing.T) {
 			name:       "ANTHROPIC_API_KEY validation",
 			secretName: "ANTHROPIC_API_KEY",
 			engineName: "Claude Code",
-			docsURL:    "https://githubnext.github.io/gh-aw/reference/engines/#anthropic-claude-code",
+			docsURL:    "https://github.github.io/gh-aw/reference/engines/#anthropic-claude-code",
 			wantStrings: []string{
 				"Validate ANTHROPIC_API_KEY secret",
 				"Error: ANTHROPIC_API_KEY secret is not set",
 				"The Claude Code engine requires the ANTHROPIC_API_KEY secret to be configured",
 				"Please configure this secret in your repository settings",
-				"Documentation: https://githubnext.github.io/gh-aw/reference/engines/#anthropic-claude-code",
+				"Documentation: https://github.github.io/gh-aw/reference/engines/#anthropic-claude-code",
 				"<details>",
 				"<summary>Agent Environment Validation</summary>",
 				"✅ ANTHROPIC_API_KEY: Configured",
@@ -77,10 +77,10 @@ func TestGenerateMultiSecretValidationStep(t *testing.T) {
 			name:        "Codex dual secret validation",
 			secretNames: []string{"CODEX_API_KEY", "OPENAI_API_KEY"},
 			engineName:  "Codex",
-			docsURL:     "https://githubnext.github.io/gh-aw/reference/engines/#openai-codex",
+			docsURL:     "https://github.github.io/gh-aw/reference/engines/#openai-codex",
 			wantStrings: []string{
 				"Validate CODEX_API_KEY or OPENAI_API_KEY secret",
-				"run: /opt/gh-aw/actions/validate_multi_secret.sh CODEX_API_KEY OPENAI_API_KEY Codex https://githubnext.github.io/gh-aw/reference/engines/#openai-codex",
+				"run: /opt/gh-aw/actions/validate_multi_secret.sh CODEX_API_KEY OPENAI_API_KEY Codex https://github.github.io/gh-aw/reference/engines/#openai-codex",
 				"CODEX_API_KEY: ${{ secrets.CODEX_API_KEY }}",
 				"OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}",
 			},
@@ -89,10 +89,10 @@ func TestGenerateMultiSecretValidationStep(t *testing.T) {
 			name:        "GitHub Copilot CLI with multi-word engine name",
 			secretNames: []string{"COPILOT_GITHUB_TOKEN"},
 			engineName:  "GitHub Copilot CLI",
-			docsURL:     "https://githubnext.github.io/gh-aw/reference/engines/#github-copilot-default",
+			docsURL:     "https://github.github.io/gh-aw/reference/engines/#github-copilot-default",
 			wantStrings: []string{
 				"Validate COPILOT_GITHUB_TOKEN secret",
-				"run: /opt/gh-aw/actions/validate_multi_secret.sh COPILOT_GITHUB_TOKEN 'GitHub Copilot CLI' https://githubnext.github.io/gh-aw/reference/engines/#github-copilot-default",
+				"run: /opt/gh-aw/actions/validate_multi_secret.sh COPILOT_GITHUB_TOKEN 'GitHub Copilot CLI' https://github.github.io/gh-aw/reference/engines/#github-copilot-default",
 				"COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}",
 			},
 		},
@@ -100,10 +100,10 @@ func TestGenerateMultiSecretValidationStep(t *testing.T) {
 			name:        "Claude Code with multi-word engine name and dual secrets",
 			secretNames: []string{"CLAUDE_CODE_OAUTH_TOKEN", "ANTHROPIC_API_KEY"},
 			engineName:  "Claude Code",
-			docsURL:     "https://githubnext.github.io/gh-aw/reference/engines/#anthropic-claude-code",
+			docsURL:     "https://github.github.io/gh-aw/reference/engines/#anthropic-claude-code",
 			wantStrings: []string{
 				"Validate CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY secret",
-				"run: /opt/gh-aw/actions/validate_multi_secret.sh CLAUDE_CODE_OAUTH_TOKEN ANTHROPIC_API_KEY 'Claude Code' https://githubnext.github.io/gh-aw/reference/engines/#anthropic-claude-code",
+				"run: /opt/gh-aw/actions/validate_multi_secret.sh CLAUDE_CODE_OAUTH_TOKEN ANTHROPIC_API_KEY 'Claude Code' https://github.github.io/gh-aw/reference/engines/#anthropic-claude-code",
 				"CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}",
 				"ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}",
 			},
diff --git a/pkg/workflow/strict_mode_validation.go b/pkg/workflow/strict_mode_validation.go
index 384f37e6d1..ff5dd47dab 100644
--- a/pkg/workflow/strict_mode_validation.go
+++ b/pkg/workflow/strict_mode_validation.go
@@ -66,7 +66,7 @@ func (c *Compiler) validateStrictPermissions(frontmatter map[string]any) error {
 	for _, scope := range writePermissions {
 		if perms.IsAllowed(scope, "write") {
 			strictModeValidationLog.Printf("Write permission validation failed: scope=%s", scope)
-			return fmt.Errorf("strict mode: write permission '%s: write' is not allowed for security reasons. Use 'safe-outputs.create-issue', 'safe-outputs.create-pull-request', 'safe-outputs.add-comment', or 'safe-outputs.update-issue' to perform write operations safely. See: https://githubnext.github.io/gh-aw/reference/safe-outputs/", scope)
+			return fmt.Errorf("strict mode: write permission '%s: write' is not allowed for security reasons. Use 'safe-outputs.create-issue', 'safe-outputs.create-pull-request', 'safe-outputs.add-comment', or 'safe-outputs.update-issue' to perform write operations safely. See: https://github.github.io/gh-aw/reference/safe-outputs/", scope)
 		}
 	}
 
@@ -99,7 +99,7 @@ func (c *Compiler) validateStrictNetwork(networkPermissions *NetworkPermissions)
 	for _, domain := range networkPermissions.Allowed {
 		if domain == "*" {
 			strictModeValidationLog.Printf("Network validation failed: wildcard detected")
-			return fmt.Errorf("strict mode: wildcard '*' is not allowed in network.allowed domains to prevent unrestricted internet access. Specify explicit domains or use ecosystem identifiers like 'python', 'node', 'containers'. See: https://githubnext.github.io/gh-aw/reference/network/#available-ecosystem-identifiers")
+			return fmt.Errorf("strict mode: wildcard '*' is not allowed in network.allowed domains to prevent unrestricted internet access. Specify explicit domains or use ecosystem identifiers like 'python', 'node', 'containers'. See: https://github.github.io/gh-aw/reference/network/#available-ecosystem-identifiers")
 		}
 	}
 
@@ -141,7 +141,7 @@ func (c *Compiler) validateStrictMCPNetwork(frontmatter map[string]any, networkP
 			if _, hasContainer := serverConfig["container"]; hasContainer {
 				// Require top-level network configuration
 				if !hasTopLevelNetwork {
-					return fmt.Errorf("strict mode: custom MCP server '%s' with container must have top-level network configuration for security. Add 'network: { allowed: [...] }' to the workflow to restrict network access. See: https://githubnext.github.io/gh-aw/reference/network/", serverName)
+					return fmt.Errorf("strict mode: custom MCP server '%s' with container must have top-level network configuration for security. Add 'network: { allowed: [...] }' to the workflow to restrict network access. See: https://github.github.io/gh-aw/reference/network/", serverName)
 				}
 			}
 		}
@@ -172,7 +172,7 @@ func (c *Compiler) validateStrictTools(frontmatter map[string]any) error {
 			if mode, hasMode := serenaConfig["mode"]; hasMode {
 				if modeStr, ok := mode.(string); ok && modeStr == "local" {
 					strictModeValidationLog.Printf("Serena local mode validation failed")
-					return fmt.Errorf("strict mode: serena tool with 'mode: local' is not allowed for security reasons. Local mode runs the MCP server directly on the host without containerization, bypassing security isolation. Use 'mode: docker' (default) instead, which runs Serena in a container. See: https://githubnext.github.io/gh-aw/reference/tools/#serena")
+					return fmt.Errorf("strict mode: serena tool with 'mode: local' is not allowed for security reasons. Local mode runs the MCP server directly on the host without containerization, bypassing security isolation. Use 'mode: docker' (default) instead, which runs Serena in a container. See: https://github.github.io/gh-aw/reference/tools/#serena")
 				}
 			}
 		}
@@ -289,7 +289,7 @@ func (c *Compiler) validateStrictFirewall(engineID string, networkPermissions *N
 	// In strict mode, this is not allowed for any engine as it disables the agent sandbox
 	if sandboxConfig != nil && sandboxConfig.Agent != nil && sandboxConfig.Agent.Disabled {
 		strictModeValidationLog.Printf("sandbox: false is set, refusing in strict mode")
-		return fmt.Errorf("strict mode: 'sandbox: false' is not allowed because it disables all sandbox features including the firewall and gateway. This removes important security protections. Remove 'sandbox: false' or set 'strict: false' to disable strict mode. See: https://githubnext.github.io/gh-aw/reference/sandbox/")
+		return fmt.Errorf("strict mode: 'sandbox: false' is not allowed because it disables all sandbox features including the firewall and gateway. This removes important security protections. Remove 'sandbox: false' or set 'strict: false' to disable strict mode. See: https://github.github.io/gh-aw/reference/sandbox/")
 	}
 
 	// Only apply to copilot and codex engines
@@ -334,7 +334,7 @@ func (c *Compiler) validateStrictFirewall(engineID string, networkPermissions *N
 	// In strict mode, firewall MUST be enabled
 	if networkPermissions.Firewall == nil || !networkPermissions.Firewall.Enabled {
 		strictModeValidationLog.Printf("Firewall validation failed: firewall not enabled in strict mode")
-		return fmt.Errorf("strict mode: firewall must be enabled for %s engine with network restrictions. The firewall should be enabled by default, but if you've explicitly disabled it with 'network.firewall: false' or 'sandbox.agent: false', this is not allowed in strict mode for security reasons. See: https://githubnext.github.io/gh-aw/reference/network/", engineID)
+		return fmt.Errorf("strict mode: firewall must be enabled for %s engine with network restrictions. The firewall should be enabled by default, but if you've explicitly disabled it with 'network.firewall: false' or 'sandbox.agent: false', this is not allowed in strict mode for security reasons. See: https://github.github.io/gh-aw/reference/network/", engineID)
 	}
 
 	strictModeValidationLog.Printf("Firewall validation passed")
diff --git a/scratchpad/error-recovery-patterns.md b/scratchpad/error-recovery-patterns.md
index d78f3c51c5..c1a8550c0c 100644
--- a/scratchpad/error-recovery-patterns.md
+++ b/scratchpad/error-recovery-patterns.md
@@ -1511,7 +1511,7 @@ return fmt.Errorf(
 **Example:**
 ```go
 return fmt.Errorf(
-    "strict mode: write permission 'contents: write' is not allowed for security reasons. Use 'safe-outputs.create-issue' or 'safe-outputs.create-pull-request' to perform write operations safely. See: https://githubnext.github.io/gh-aw/reference/safe-outputs/",
+    "strict mode: write permission 'contents: write' is not allowed for security reasons. Use 'safe-outputs.create-issue' or 'safe-outputs.create-pull-request' to perform write operations safely. See: https://github.github.io/gh-aw/reference/safe-outputs/",
 )
 ```
 
diff --git a/scratchpad/gastown.md b/scratchpad/gastown.md
index a513ba44ae..701b2bc5a3 100644
--- a/scratchpad/gastown.md
+++ b/scratchpad/gastown.md
@@ -962,6 +962,6 @@ These enhancements would position gh-aw as a full-featured agentic workflow plat
 **References**:
 - Gastown: https://github.com/steveyegge/gastown
 - Beads: https://github.com/steveyegge/beads
-- gh-aw Documentation: https://githubnext.github.io/gh-aw/
+- gh-aw Documentation: https://github.github.io/gh-aw/
 
 **Last Updated**: 2026-01-02
diff --git a/scratchpad/mdflow-comparison.md b/scratchpad/mdflow-comparison.md
index 1dcfe1a789..4939418ef3 100644
--- a/scratchpad/mdflow-comparison.md
+++ b/scratchpad/mdflow-comparison.md
@@ -818,7 +818,7 @@ Neither is "better" - they're optimized for different use cases and user needs.
 ## References
 
 - mdflow Repository: https://github.com/johnlindquist/mdflow
-- GitHub Agentic Workflows Documentation: https://githubnext.github.io/gh-aw/
+- GitHub Agentic Workflows Documentation: https://github.github.io/gh-aw/
 - mdflow README: Full documentation of syntax and features
 - gh-aw Reference: `/docs/src/content/docs/reference/`
 
diff --git a/scratchpad/oh-my-code.md b/scratchpad/oh-my-code.md
index 5f3c8825b0..422bf972ae 100644
--- a/scratchpad/oh-my-code.md
+++ b/scratchpad/oh-my-code.md
@@ -1664,8 +1664,8 @@ The future likely involves both approaches: developers using AI agents locally f
 
 ### GitHub Agentic Workflows
 - **Repository**: https://github.com/github/gh-aw
-- **Documentation**: https://githubnext.github.io/gh-aw/
-- **Security Guide**: https://githubnext.github.io/gh-aw/guides/security/
+- **Documentation**: https://github.github.io/gh-aw/
+- **Security Guide**: https://github.github.io/gh-aw/guides/security/
 - **Discord**: #continuous-ai in GitHub Next Discord
 
 ### Related Comparisons
diff --git a/scratchpad/safe-output-messages.md b/scratchpad/safe-output-messages.md
index efbe88229c..de856d825d 100644
--- a/scratchpad/safe-output-messages.md
+++ b/scratchpad/safe-output-messages.md
@@ -97,12 +97,12 @@ graph TD
 **Markdown Source:**
 ```markdown
 >
-> To add this workflow in your repository, run `gh aw add owner/repo/path@ref`. See [usage guide](https://githubnext.github.io/gh-aw/setup/cli/).
+> To add this workflow in your repository, run `gh aw add owner/repo/path@ref`. See [usage guide](https://github.github.io/gh-aw/setup/cli/).
 ```text
 
 **Rendered Output:**
 >
-> To add this workflow in your repository, run `gh aw add github/gh-aw/.github/workflows/example@main`. See [usage guide](https://githubnext.github.io/gh-aw/setup/cli/).
+> To add this workflow in your repository, run `gh aw add github/gh-aw/.github/workflows/example@main`. See [usage guide](https://github.github.io/gh-aw/setup/cli/).
 
 **When shown**: Appears when workflow has a known source location.
 
diff --git a/scratchpad/safe-outputs-specification.md b/scratchpad/safe-outputs-specification.md
index c4590c60c3..7eef7ceb5d 100644
--- a/scratchpad/safe-outputs-specification.md
+++ b/scratchpad/safe-outputs-specification.md
@@ -9,7 +9,7 @@ sidebar:
 
 **Version**: 1.0.0  
 **Status**: Recommendation  
-**Latest Version**: https://githubnext.github.io/gh-aw/scratchpad/safe-outputs-specification/  
+**Latest Version**: https://github.github.io/gh-aw/scratchpad/safe-outputs-specification/  
 **Editors**: GitHub Next Team
 
 ---
diff --git a/skills/developer/SKILL.md b/skills/developer/SKILL.md
index c364d0c8a3..b4283fda7a 100644
--- a/skills/developer/SKILL.md
+++ b/skills/developer/SKILL.md
@@ -1017,7 +1017,7 @@ With triggering context:
 
 ```markdown
 >
-> To add this workflow in your repository, run `gh aw add owner/repo/path@ref`. See [usage guide](https://githubnext.github.io/gh-aw/setup/cli/).
+> To add this workflow in your repository, run `gh aw add owner/repo/path@ref`. See [usage guide](https://github.github.io/gh-aw/setup/cli/).
 ```
 
 #### Staged Mode Preview
diff --git a/skills/gh-agent-session/SKILL.md b/skills/gh-agent-session/SKILL.md
index 776f314158..a8a9bbebc5 100644
--- a/skills/gh-agent-session/SKILL.md
+++ b/skills/gh-agent-session/SKILL.md
@@ -382,5 +382,5 @@ jobs:
 
 - [GitHub Copilot Documentation](https://docs.github.com/en/copilot)
 - [GitHub CLI Extensions](https://docs.github.com/en/github-cli/github-cli/using-github-cli-extensions)
-- [Safe Outputs Documentation](https://githubnext.github.io/gh-aw/reference/safe-outputs/)
+- [Safe Outputs Documentation](https://github.github.io/gh-aw/reference/safe-outputs/)
 - [Personal Access Tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
diff --git a/skills/gh-agent-task/SKILL.md b/skills/gh-agent-task/SKILL.md
index 4f06d7d33d..ea924ef76a 100644
--- a/skills/gh-agent-task/SKILL.md
+++ b/skills/gh-agent-task/SKILL.md
@@ -382,5 +382,5 @@ jobs:
 
 - [GitHub Copilot Documentation](https://docs.github.com/en/copilot)
 - [GitHub CLI Extensions](https://docs.github.com/en/github-cli/github-cli/using-github-cli-extensions)
-- [Safe Outputs Documentation](https://githubnext.github.io/gh-aw/reference/safe-outputs/)
+- [Safe Outputs Documentation](https://github.github.io/gh-aw/reference/safe-outputs/)
 - [Personal Access Tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
diff --git a/slides/index.md b/slides/index.md
index 60b5ccd725..c17d8c80e0 100644
--- a/slides/index.md
+++ b/slides/index.md
@@ -167,7 +167,7 @@ gh aw audit 123456
 
 Complete documentation available at:
 
-https://githubnext.github.io/gh-aw/
+https://github.github.io/gh-aw/
 
 Topics covered:
 - Setup and installation
diff --git a/socials/campaign.log b/socials/campaign.log
index 9b3d6aafe9..f29739372b 100644
--- a/socials/campaign.log
+++ b/socials/campaign.log
@@ -76,16 +76,16 @@
 [2026-01-16 21:33:02] [DRY RUN] No API calls will be made
 [2026-01-16 21:33:02] Starting campaign post for 2026-01-21
 [2026-01-16 21:33:02] Content file: /home/dsyme/gh-aw/socials/content/01-welcome.md
-[2026-01-16 21:33:02] [DRY RUN] X post: Step right up into Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the golden ticket tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #AI #DevOps
-[2026-01-16 21:33:02] [DRY RUN] Bluesky post: Welcome to Peli’s Agent Factory 🍫🤖 — a slightly magical, very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
-[2026-01-16 21:33:02] [DRY RUN] Mastodon post: Welcome to Peli’s Agent Factory 🍫🔧 — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+[2026-01-16 21:33:02] [DRY RUN] X post: Step right up into Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the golden ticket tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #AI #DevOps
+[2026-01-16 21:33:02] [DRY RUN] Bluesky post: Welcome to Peli’s Agent Factory 🍫🤖 — a slightly magical, very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+[2026-01-16 21:33:02] [DRY RUN] Mastodon post: Welcome to Peli’s Agent Factory 🍫🔧 — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:33:02] [DRY RUN] LinkedIn post: At GitHub Next, we’ve been exploring what happens when a team leans into “let’s create an agentic workflow for that” — and then actually runs 100+ of them in real repositories. 🍫✨
 [2026-01-16 21:33:02] Posted to 4/4 platforms successfully
 [2026-01-16 21:33:02] Starting campaign post for 2026-01-22
 [2026-01-16 21:33:02] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
-[2026-01-16 21:33:02] [DRY RUN] X post: Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
-[2026-01-16 21:33:02] [DRY RUN] Bluesky post: Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
-[2026-01-16 21:33:02] [DRY RUN] Mastodon post: Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+[2026-01-16 21:33:02] [DRY RUN] X post: Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+[2026-01-16 21:33:02] [DRY RUN] Bluesky post: Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+[2026-01-16 21:33:02] [DRY RUN] Mastodon post: Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:33:02] [DRY RUN] LinkedIn post: Meet the Workflows (1): Issue Triage 🍬✨
 [2026-01-16 21:33:02] Posted to 4/4 platforms successfully
 [2026-01-16 21:33:02] Tracking engagement for recent posts
@@ -93,16 +93,16 @@
 [2026-01-16 21:33:19] [DRY RUN] No API calls will be made
 [2026-01-16 21:33:19] Starting campaign post for 2026-01-21
 [2026-01-16 21:33:19] Content file: /home/dsyme/gh-aw/socials/content/01-welcome.md
-[2026-01-16 21:33:19] [DRY RUN] X post: Step right up into Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the golden ticket tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #AI #DevOps
-[2026-01-16 21:33:19] [DRY RUN] Bluesky post: Welcome to Peli’s Agent Factory 🍫🤖 — a slightly magical, very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
-[2026-01-16 21:33:19] [DRY RUN] Mastodon post: Welcome to Peli’s Agent Factory 🍫🔧 — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+[2026-01-16 21:33:19] [DRY RUN] X post: Step right up into Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the golden ticket tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #AI #DevOps
+[2026-01-16 21:33:19] [DRY RUN] Bluesky post: Welcome to Peli’s Agent Factory 🍫🤖 — a slightly magical, very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+[2026-01-16 21:33:19] [DRY RUN] Mastodon post: Welcome to Peli’s Agent Factory 🍫🔧 — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:33:19] [DRY RUN] LinkedIn post: At GitHub Next, we’ve been exploring what happens when a team leans into “let’s create an agentic workflow for that” — and then actually runs 100+ of them in real repositories. 🍫✨
 [2026-01-16 21:33:19] Posted to 4/4 platforms successfully
 [2026-01-16 21:33:19] Starting campaign post for 2026-01-22
 [2026-01-16 21:33:19] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
-[2026-01-16 21:33:19] [DRY RUN] X post: Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
-[2026-01-16 21:33:19] [DRY RUN] Bluesky post: Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
-[2026-01-16 21:33:19] [DRY RUN] Mastodon post: Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+[2026-01-16 21:33:19] [DRY RUN] X post: Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+[2026-01-16 21:33:19] [DRY RUN] Bluesky post: Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+[2026-01-16 21:33:19] [DRY RUN] Mastodon post: Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:33:19] [DRY RUN] LinkedIn post: Meet the Workflows (1): Issue Triage 🍬✨
 [2026-01-16 21:33:19] Posted to 4/4 platforms successfully
 [2026-01-16 21:33:19] Tracking engagement for recent posts
@@ -111,27 +111,27 @@
 [2026-01-16 21:33:45] Starting campaign post for 2026-01-21
 [2026-01-16 21:33:45] Content file: /home/dsyme/gh-aw/socials/content/01-welcome.md
 [2026-01-16 21:33:45] [DRY RUN] X post:
-Step right up into Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the golden ticket tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #AI #DevOps
+Step right up into Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the golden ticket tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #AI #DevOps
 [2026-01-16 21:33:45] [DRY RUN] Bluesky post:
-Welcome to Peli’s Agent Factory 🍫🤖 — a slightly magical, very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Welcome to Peli’s Agent Factory 🍫🤖 — a slightly magical, very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:33:45] [DRY RUN] Mastodon post:
-Welcome to Peli’s Agent Factory 🍫🔧 — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+Welcome to Peli’s Agent Factory 🍫🔧 — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:33:45] [DRY RUN] LinkedIn post:
 At GitHub Next, we’ve been exploring what happens when a team leans into “let’s create an agentic workflow for that” — and then actually runs 100+ of them in real repositories. 🍫✨
-If you’re curious, this is the golden ticket: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+If you’re curious, this is the golden ticket: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:33:45] Posted to 4/4 platforms successfully
 [2026-01-16 21:33:45] Starting campaign post for 2026-01-22
 [2026-01-16 21:33:45] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
 [2026-01-16 21:33:45] [DRY RUN] X post:
-Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
 [2026-01-16 21:33:45] [DRY RUN] Bluesky post:
-Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:33:45] [DRY RUN] Mastodon post:
-Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:33:45] [DRY RUN] LinkedIn post:
 Meet the Workflows (1): Issue Triage 🍬✨
 One of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes it, replies with context, and applies labels consistently.
-Tour + links to the workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Tour + links to the workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:33:45] Posted to 4/4 platforms successfully
 [2026-01-16 21:33:45] Tracking engagement for recent posts
 [2026-01-16 21:38:19] Running campaign
@@ -140,29 +140,29 @@ Tour + links to the workflow source: https://githubnext.github.io/gh-aw/blog/202
 [2026-01-16 21:38:19] Content file: /home/dsyme/gh-aw/socials/content/01-welcome.md
 [2026-01-16 21:38:19] [DRY RUN] X post:
 Welcome to our latest blog series from GitHub Agentic Workflows!
-In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
+In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
 Automation isn't just about scripts—it's about creating intelligent agents that keep our projects moving.
 #GitHubNext #AI #DevOps #ContinuousAI
 [2026-01-16 21:38:19] [DRY RUN] Bluesky post:
-Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:38:19] [DRY RUN] Mastodon post:
-Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:38:19] [DRY RUN] LinkedIn post:
 At GitHub Next, we’ve been exploring what happens when a team leans into “let’s create an agentic workflow for that” — and then actually runs 100+ of them in real repositories. 🍫✨
-If you’re curious, this is the golden ticket: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+If you’re curious, this is the golden ticket: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:38:19] Posted to 4/4 platforms successfully
 [2026-01-16 21:38:19] Starting campaign post for 2026-01-22
 [2026-01-16 21:38:19] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
 [2026-01-16 21:38:19] [DRY RUN] X post:
-Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+Meet the Workflows (1): Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
 [2026-01-16 21:38:19] [DRY RUN] Bluesky post:
-Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Meet the Workflows (1): Issue Triage 🍬🛠️ — a practical “starter spell” for handling new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:38:19] [DRY RUN] Mastodon post:
-Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+Meet the Workflows (1): Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents: triage new issues with automated analysis + consistent labeling. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:38:19] [DRY RUN] LinkedIn post:
 Meet the Workflows (1): Issue Triage 🍬✨
 One of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes it, replies with context, and applies labels consistently.
-Tour + links to the workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Tour + links to the workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:38:19] Posted to 4/4 platforms successfully
 [2026-01-16 21:38:19] Tracking engagement for recent posts
 [2026-01-16 21:41:43] Starting campaign post for 2026-01-21
@@ -170,36 +170,36 @@ Tour + links to the workflow source: https://githubnext.github.io/gh-aw/blog/202
 [2026-01-16 21:41:43] [DRY RUN] X post:
 Welcome to our blog series, about our new technology for automated agentics on GitHub - GitHub Agentic Workflows!
 Automated agentics are powerful, but what are they useful for in software repositories?
-In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
+In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
 Automation isn't just about scripts—it's about creating intelligent agents that keep projects moving and achieve continuous improvement.
 #GitHubNext #AI #devops #continuousai
 [2026-01-16 21:41:43] [DRY RUN] Bluesky post:
-Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:41:43] [DRY RUN] Mastodon post:
-Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:41:43] [DRY RUN] LinkedIn post:
 Welcome to our blog series from GitHub Next on GitHub Agentic Workflows — a practical look at “automated agentics” in software repos. 🍫✨
 Automated agentics are powerful… but what are they actually useful for day-to-day engineering?
 In this series, we’d like to take you on a tour of Peli’s Agent Factory: a slightly magical (but very real) place where 100+ agentic workflows help keep real repositories humming — from triage and maintenance to continuous improvement.
 🎟️ Take the golden ticket tour here:
-https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 #GitHubNext #AI #DevOps #ContinuousAI
 [2026-01-16 21:41:43] Posted to 4/4 platforms successfully
 [2026-01-16 21:41:43] Tracking engagement for recent posts
 [2026-01-16 21:42:59] Starting campaign post for 2026-01-22
 [2026-01-16 21:42:59] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
 [2026-01-16 21:42:59] [DRY RUN] X post:
-Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
 [2026-01-16 21:42:59] [DRY RUN] Bluesky post:
-Day 2 on the factory tour 🍫✨: Issue Triage 🍬🛠️ — a practical “starter spell” for new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Day 2 on the factory tour 🍫✨: Issue Triage 🍬🛠️ — a practical “starter spell” for new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:42:59] [DRY RUN] Mastodon post:
-Factory Floor, Station 1 🍫🔧: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+Factory Floor, Station 1 🍫🔧: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:42:59] [DRY RUN] LinkedIn post:
 Meet the Workflows (1): Issue Triage 🍬✨
 Welcome back to the tour of Peli’s Agent Factory. If day 1 was the “golden ticket” intro, day 2 is our first stop on the factory floor: Issue Triage.
 It’s one of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes the report, replies with helpful context, and applies labels consistently — so maintainers can spend more time building and less time sorting.
 Tour + links to the workflow source:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 #GitHubNext #AI #DevOps
 [2026-01-16 21:42:59] Posted to 4/4 platforms successfully
 [2026-01-16 21:42:59] Tracking engagement for recent posts
@@ -210,35 +210,35 @@ https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:46:08] [DRY RUN] X post:
 Welcome to our blog series, about our new technology for automated agentics on GitHub - GitHub Agentic Workflows!
 Automated agentics are powerful, but what are they useful for in software repositories?
-In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
+In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
 Automation isn't just about scripts—it's about creating intelligent agents that keep projects moving and achieve continuous improvement.
 #GitHubNext #AI #devops #continuousai
 [2026-01-16 21:46:08] [DRY RUN] Bluesky post:
-Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:46:08] [DRY RUN] Mastodon post:
-Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:46:08] [DRY RUN] LinkedIn post:
 Welcome to our blog series from GitHub Next on GitHub Agentic Workflows — a practical look at “automated agentics” in software repos. 🍫✨
 Automated agentics are powerful… but what are they actually useful for day-to-day engineering?
 In this series, we’d like to take you on a tour of Peli’s Agent Factory: a slightly magical (but very real) place where 100+ agentic workflows help keep real repositories humming — from triage and maintenance to continuous improvement.
 Start the tour here:
-https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 #GitHubNext #AI #DevOps #ContinuousAI
 [2026-01-16 21:46:08] Posted to 4/4 platforms successfully
 [2026-01-16 21:46:08] Starting campaign post for 2026-01-22
 [2026-01-16 21:46:08] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
 [2026-01-16 21:46:08] [DRY RUN] X post:
-Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
 [2026-01-16 21:46:08] [DRY RUN] Bluesky post:
-Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🛠️ — a practical “starter” for new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🛠️ — a practical “starter” for new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:46:08] [DRY RUN] Mastodon post:
-Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:46:08] [DRY RUN] LinkedIn post:
 Meet the Workflows (1): Issue Triage 🍬✨
 Welcome back to the tour of Peli’s Agent Factory. Day 2 is our first stop on the factory floor: Issue Triage.
 It’s one of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes the report, replies with helpful context, and applies labels consistently — so maintainers can spend more time building and less time sorting.
 Tour + links to the workflow source:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 #GitHubNext #AI #DevOps
 [2026-01-16 21:46:08] Posted to 4/4 platforms successfully
 [2026-01-16 21:46:08] Tracking engagement for recent posts
@@ -249,35 +249,35 @@ https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:51:10] [DRY RUN] X post:
 Welcome to our blog series, about our new technology for automated agentics on GitHub - GitHub Agentic Workflows!
 Automated agentics are powerful, but what are they useful for in software repositories?
-In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
+In this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ 
 Automation isn't just about scripts—it's about creating intelligent agents that keep projects moving and achieve continuous improvement.
 #GitHubNext #AI #devops #continuousai
 [2026-01-16 21:51:10] [DRY RUN] Bluesky post:
-Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 [2026-01-16 21:51:10] [DRY RUN] Mastodon post:
-Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
+Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation
 [2026-01-16 21:51:10] [DRY RUN] LinkedIn post:
 Welcome to our blog series from GitHub Next on GitHub Agentic Workflows — a practical look at “automated agentics” in software repos. 🍫✨
 Automated agentics are powerful… but what are they actually useful for day-to-day engineering?
 In this series, we’d like to take you on a tour of Peli’s Agent Factory: a slightly magical (but very real) place where 100+ agentic workflows help keep real repositories humming — from triage and maintenance to continuous improvement.
 Start the tour here:
-https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 #GitHubNext #AI #DevOps #ContinuousAI
 [2026-01-16 21:51:10] Posted to 4/4 platforms successfully
 [2026-01-16 21:51:10] Starting campaign post for 2026-01-22
 [2026-01-16 21:51:10] Content file: /home/dsyme/gh-aw/socials/content/02-meet-workflows.md
 [2026-01-16 21:51:10] [DRY RUN] X post:
-Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
+Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI
 [2026-01-16 21:51:10] [DRY RUN] Bluesky post:
-Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🛠️ — a practical “starter” for new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🛠️ — a practical “starter” for new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 [2026-01-16 21:51:10] [DRY RUN] Mastodon post:
-Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
+Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub
 [2026-01-16 21:51:10] [DRY RUN] LinkedIn post:
 Meet the Workflows (1): Issue Triage 🍬✨
 Welcome back to the tour of Peli’s Agent Factory. Day 2 is our first stop on the factory floor: Issue Triage.
 It’s one of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes the report, replies with helpful context, and applies labels consistently — so maintainers can spend more time building and less time sorting.
 Tour + links to the workflow source:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 #GitHubNext #AI #DevOps
 [2026-01-16 21:51:10] Posted to 4/4 platforms successfully
 [2026-01-16 21:51:10] Starting campaign post for 2026-01-23
@@ -287,16 +287,16 @@ Day 3 in Peli’s Agent Factory 🍫✨: Continuous Simplicity.
 Two agents that run continuously to keep code simple 🧹🤖
 - Automatic Code Simplifier
 - Duplicate Code Detector
-Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #GitHubNext #AI #DevOps
+Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #GitHubNext #AI #DevOps
 [2026-01-16 21:51:10] [DRY RUN] Bluesky post:
 Day 3 in Peli’s Agent Factory 🍫✨: Continuous Simplicity.
-While humans sprint ahead, these agents trail along simplifying recently-changed code and spotting semantic duplication (with Serena). Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
+While humans sprint ahead, these agents trail along simplifying recently-changed code and spotting semantic duplication (with Serena). Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
 [2026-01-16 21:51:10] [DRY RUN] Mastodon post:
 Day 3 in Peli’s Agent Factory 🍫🔧: Continuous Simplicity 🧹🤖
 Two quiet maintainers:
 - Automatic Code Simplifier
 - Duplicate Code Detector
-Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #Automation #GitHub
+Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #Automation #GitHub
 [2026-01-16 21:51:10] [DRY RUN] LinkedIn post:
 Day 3 in Peli’s Agent Factory: Continuous Simplicity 🍫✨
 After issue triage, the next stop on our tour are agents that continuously simplify code!
@@ -304,7 +304,7 @@ Two workflows:
 - Automatic Code Simplifier 🧹 
 - Duplicate Code Detector 🤖
 Tour + workflow source links:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
 #GitHubNext #AI #DevOps #Automation
 [2026-01-16 21:51:10] Posted to 4/4 platforms successfully
 [2026-01-16 21:51:10] Starting campaign post for 2026-01-24
@@ -314,17 +314,17 @@ Day 4 in Peli’s Agent Factory 🍫✨: Continuous Refactoring.
 Two agents that keep codebases structurally tidy 🧠🔧
 - Semantic Function Refactor (finds functions in the “wrong” file)
 - Go Pattern Detector (fast AST scan + deep agent review)
-Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #GitHubNext #AI #DevOps
+Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #GitHubNext #AI #DevOps
 [2026-01-16 21:51:10] [DRY RUN] Bluesky post:
 Day 4 in Peli’s Agent Factory 🍫✨: Continuous Refactoring.
 These agents look past “does it work?” and ask “does it live in the right place?” One does whole-repo semantic grouping (with Serena) to spot misplaced/outlier functions; the other uses ast-grep to cheaply detect patterns, then escalates to an agent only when needed.
-Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
+Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
 [2026-01-16 21:51:10] [DRY RUN] Mastodon post:
 Day 4 in Peli’s Agent Factory 🍫🔧: Continuous Refactoring 🧠🧹
 Two maintainers with a structural view:
 - Semantic Function Refactor (whole-repo organization)
 - Go Pattern Detector (AST pattern scan → agent review)
-Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #Automation #GitHub
+Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #Automation #GitHub
 [2026-01-16 21:51:10] [DRY RUN] LinkedIn post:
 Day 4 in Peli’s Agent Factory: Continuous Refactoring 🍫✨
 After continuous simplification, the next stop on our tour is structural refactoring: agents that scan the whole codebase and flag opportunities to improve organization and consistency.
@@ -332,7 +332,7 @@ Two workflows:
 - Semantic Function Refactor 🧠 — groups functions by purpose and highlights “outliers” that likely belong elsewhere
 - Go Pattern Detector 🔍 — uses fast AST pattern matching (ast-grep), and only triggers deeper agent analysis when it finds a match
 Tour + workflow source links:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
 #GitHubNext #AI #DevOps #Automation
 [2026-01-16 21:51:10] Posted to 4/4 platforms successfully
 [2026-01-16 21:51:10] Tracking engagement for recent posts
diff --git a/socials/content/01-welcome.md b/socials/content/01-welcome.md
index 1fb27cc714..fec54eef17 100644
--- a/socials/content/01-welcome.md
+++ b/socials/content/01-welcome.md
@@ -1,6 +1,6 @@
 # Welcome to Peli's Agent Factory
 
-Blog URL: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Blog URL: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 Social Publish Date: 2026-01-21
 
 ## X (Twitter)
@@ -11,7 +11,7 @@ We're launching a blog series that shows how to use GitHub Agentic Workflows to
 
 This isn't about demos or toy examples. You'll learn practical patterns you can adapt for your own repos, see the actual workflow code, and understand when agents work (and when they don't).
 
-Start your tour of Peli's Agent Factory: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+Start your tour of Peli's Agent Factory: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 
 #GitHubNext #AI #DevOps #ContinuousAI #PelisFactory
 
@@ -21,7 +21,7 @@ What if you could use automated agentic workflows to maintain and improve your r
 
 In our new blog series, we'll take you inside Peli's Agent Factory — where 50+ GitHub Agentic Workflows handle everything from issue triage to code refactoring. You'll learn practical patterns and see the source code for workflows we run every day.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 
 ## Mastodon
 
@@ -29,7 +29,7 @@ What if you could use automated agents to maintain and improve your repository?
 
 Using GitHub Agentic Workflows, we'll introduce you to 50+ agents that triage issues, simplify code, detect patterns, and keep repos healthy. You'll see real examples with source code you can learn from.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation #PelisFactory
+https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation #PelisFactory
 
 ## LinkedIn
 
@@ -46,6 +46,6 @@ This series isn't about theoretical possibilities. You'll learn:
 Whether you're exploring repository automation for the first time or looking to level up your existing practices, you'll find actionable insights you can apply immediately.
 
 Start your tour of Peli's Agent Factory:
-https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
+https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
 
 #GitHubNext #AI #DevOps #ContinuousAI #PelisFactory
diff --git a/socials/content/02-meet-workflows.md b/socials/content/02-meet-workflows.md
index 5ee7297460..0bbfac52b9 100644
--- a/socials/content/02-meet-workflows.md
+++ b/socials/content/02-meet-workflows.md
@@ -1,6 +1,6 @@
 # Meet the Workflows: Issue Triage
 
-Blog URL: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+Blog URL: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 Social Publish Date: 2026-01-22
 
 ## X (Twitter)
@@ -11,7 +11,7 @@ Using GitHub Agentic Workflows, our Issue Triage agent does the first pass for y
 
 You'll learn how this workflow saves hours of maintainer time and why it's one of the highest-leverage agents we run. We're sharing the actual workflow source so you can see exactly how it works and adapt it for your repos.
 
-See the tour + workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+See the tour + workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 
 #GitHubNext #AI #PelisFactory
 
@@ -21,7 +21,7 @@ How much time do you spend manually labeling and triaging issues? ✍️
 
 Our Issue Triage workflow (built with GitHub Agentic Workflows) handles the first pass automatically — analyzing context, replying with helpful information, and applying consistent labels. You'll see how it works and get the source code.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 
 ## Mastodon
 
@@ -29,7 +29,7 @@ Want to automate your issue triage? ✍️
 
 Using GitHub Agentic Workflows, this is one of the simplest but highest-leverage agents we run. It analyzes new issues, applies consistent labels, and replies with context — giving you back hours of maintainer time. Source code included.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub #PelisFactory
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub #PelisFactory
 
 ## LinkedIn
 
@@ -47,6 +47,6 @@ The result? Your team spends less time on repetitive triage and more time on act
 You'll see exactly how it works, learn the patterns that make it reliable, and get access to the complete workflow source code.
 
 Read the tour + get the source:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/
 
 #GitHubNext #AI #DevOps #PelisFactory
diff --git a/socials/content/03-meet-workflows-continuous-simplicity.md b/socials/content/03-meet-workflows-continuous-simplicity.md
index 4aa10a1d9f..874a7a8d77 100644
--- a/socials/content/03-meet-workflows-continuous-simplicity.md
+++ b/socials/content/03-meet-workflows-continuous-simplicity.md
@@ -1,6 +1,6 @@
 # Meet the Workflows: Continuous Simplicity
 
-Blog URL: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
+Blog URL: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
 Social Publish Date: 2026-01-23
 
 ## X (Twitter)
@@ -11,7 +11,7 @@ Learn about two agents that continuously combat code complexity. The Code Simpli
 
 You'll learn how these workflows prevent technical debt from accumulating instead of fighting it after the fact. We're sharing both workflows so you can see how continuous simplification works in practice.
 
-Tour + source code: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
+Tour + source code: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
 
 #GitHubNext #AI #DevOps #PelisFactory
 
@@ -21,7 +21,7 @@ What if your codebase could stay simple instead of gradually becoming more compl
 
 These two GitHub Agentic Workflows run continuously: one simplifies recently changed code, the other uses semantic analysis to spot hidden duplication. You'll see how they prevent technical debt before it accumulates.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
 
 ## Mastodon
 
@@ -29,7 +29,7 @@ Struggling with growing code complexity? 🧹
 
 Discover two GitHub Agentic Workflows that continuously simplify your codebase: one targets recent changes for clarity improvements, the other uses semantic analysis to detect hidden duplication. Source code included.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #Automation #GitHub #PelisFactory
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #Automation #GitHub #PelisFactory
 
 ## LinkedIn
 
@@ -46,6 +46,6 @@ Using semantic analysis (powered by Serena embeddings), this workflow spots conc
 You'll learn why continuous simplification is more effective than periodic cleanup, see the techniques that make these agents reliable, and get the complete workflow source code.
 
 Read the tour + get the workflows:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/
 
 #GitHubNext #AI #DevOps #Automation #PelisFactory
diff --git a/socials/content/04-meet-workflows-continuous-refactoring.md b/socials/content/04-meet-workflows-continuous-refactoring.md
index 7f40b98ded..29d62d6df7 100644
--- a/socials/content/04-meet-workflows-continuous-refactoring.md
+++ b/socials/content/04-meet-workflows-continuous-refactoring.md
@@ -1,6 +1,6 @@
 # Meet the Workflows: Continuous Refactoring
 
-Blog URL: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
+Blog URL: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
 Social Publish Date: 2026-01-24
 
 ## X (Twitter)
@@ -11,7 +11,7 @@ Learn about two GitHub Agentic Workflows that automate the refactoring of your c
 
 You'll learn an important pattern: use cheap tools (like ast-grep) to find candidates, then escalate only the interesting cases to AI analysis. This makes continuous refactoring affordable at scale.
 
-See how it works: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
+See how it works: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
 
 #GitHubNext #AI #DevOps #PelisFactory
 
@@ -21,7 +21,7 @@ How do you automate cleanup of AI code as your project grows? 🏗️
 
 These GitHub Agentic Workflows look beyond "does it work?" to ask "is it in the right place?" One uses semantic analysis to spot organizational issues. The other shows you how to combine cheap AST scanning with targeted agent review.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
 
 ## Mastodon
 
@@ -29,7 +29,7 @@ Wondering how to maintain good code organization at scale for AI-generated code?
 
 Discover two structural refactoring workflows built with GitHub Agentic Workflows: one uses semantic analysis to find misplaced code, the other combines AST pattern detection with agent review for cost-effective continuous improvement.
 
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #Automation #GitHub #PelisFactory
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #Automation #GitHub #PelisFactory
 
 ## LinkedIn
 
@@ -46,6 +46,6 @@ This workflow demonstrates a critical cost-optimization pattern: it uses ast-gre
 These workflows show you how to maintain good architecture continuously rather than through painful quarterly refactoring efforts.
 
 Read the tour + get the workflows:
-https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
+https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/
 
 #GitHubNext #AI #DevOps #Automation #PelisFactory
diff --git a/socials/published/2026-01-21.json b/socials/published/2026-01-21.json
index c748298f72..aa828e587f 100644
--- a/socials/published/2026-01-21.json
+++ b/socials/published/2026-01-21.json
@@ -7,20 +7,20 @@
     "x": {
       "id": "dryrun-x-2026-01-21",
       "url": "https://twitter.com/i/web/status/dryrun-x-2026-01-21",
-      "content": "Welcome to our blog series, about our new technology for automated agentics on GitHub - GitHub Agentic Workflows!\nAutomated agentics are powerful, but what are they useful for in software repositories?\nIn this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ \nAutomation isn't just about scripts—it's about creating intelligent agents that keep projects moving and achieve continuous improvement.\n#GitHubNext #AI #devops #continuousai"
+      "content": "Welcome to our blog series, about our new technology for automated agentics on GitHub - GitHub Agentic Workflows!\nAutomated agentics are powerful, but what are they useful for in software repositories?\nIn this series we'd like to take you on a tour of ✨🍫 Peli’s Agent Factory 🍫✨ — where 100+ agentic workflows keep real repos humming. Take the tour: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ \nAutomation isn't just about scripts—it's about creating intelligent agents that keep projects moving and achieve continuous improvement.\n#GitHubNext #AI #devops #continuousai"
     },
     "bluesky": {
       "uri": "at://dryrun/bluesky/2026-01-21",
-      "content": "Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/"
+      "content": "Welcome to ✨🍫 Peli’s Agent Factory 🍫✨ — a magical yet very practical tour of the agentic workflows we actually run in real repos. Start here: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/"
     },
     "mastodon": {
       "id": "dryrun-mastodon-2026-01-21",
       "url": "",
-      "content": "Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation"
+      "content": "Welcome to ✨🍫Peli’s Agent Factory 🍫✨ — not demos, but real agentic workflows doing real work to keep a repo moving. Come wander the assembly line: https://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ #GitHubNext #Automation"
     },
     "linkedin": {
       "id": "dryrun-linkedin-2026-01-21",
-      "content": "Welcome to our blog series from GitHub Next on GitHub Agentic Workflows — a practical look at “automated agentics” in software repos. 🍫✨\nAutomated agentics are powerful… but what are they actually useful for day-to-day engineering?\nIn this series, we’d like to take you on a tour of Peli’s Agent Factory: a slightly magical (but very real) place where 100+ agentic workflows help keep real repositories humming — from triage and maintenance to continuous improvement.\nStart the tour here:\nhttps://githubnext.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/\n#GitHubNext #AI #DevOps #ContinuousAI"
+      "content": "Welcome to our blog series from GitHub Next on GitHub Agentic Workflows — a practical look at “automated agentics” in software repos. 🍫✨\nAutomated agentics are powerful… but what are they actually useful for day-to-day engineering?\nIn this series, we’d like to take you on a tour of Peli’s Agent Factory: a slightly magical (but very real) place where 100+ agentic workflows help keep real repositories humming — from triage and maintenance to continuous improvement.\nStart the tour here:\nhttps://github.github.io/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/\n#GitHubNext #AI #DevOps #ContinuousAI"
     }
   }
 }
diff --git a/socials/published/2026-01-22.json b/socials/published/2026-01-22.json
index 58aae8e4fe..11db48483f 100644
--- a/socials/published/2026-01-22.json
+++ b/socials/published/2026-01-22.json
@@ -7,20 +7,20 @@
     "x": {
       "id": "dryrun-x-2026-01-22",
       "url": "https://twitter.com/i/web/status/dryrun-x-2026-01-22",
-      "content": "Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI"
+      "content": "Next stop in Peli’s Agent Factory 🍫✨: Issue Triage 🍬🧠 — an agent that reads new issues, replies with context, and applies labels automatically. Tour + workflow source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #GitHubNext #AI"
     },
     "bluesky": {
       "uri": "at://dryrun/bluesky/2026-01-22",
-      "content": "Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🛠️ — a practical “starter” for new issues: summarize, label, and suggest next steps. https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/"
+      "content": "Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🛠️ — a practical “starter” for new issues: summarize, label, and suggest next steps. https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/"
     },
     "mastodon": {
       "id": "dryrun-mastodon-2026-01-22",
       "url": "",
-      "content": "Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub"
+      "content": "Day 2 on the tour of Peli's Agent Factory! 🍫✨: Issue Triage 🍬🔍 — one of the simplest, highest-leverage agents. It analyzes new issues fast and applies consistent labels so maintainers can breathe. Tour + source: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/ #Automation #GitHub"
     },
     "linkedin": {
       "id": "dryrun-linkedin-2026-01-22",
-      "content": "Meet the Workflows (1): Issue Triage 🍬✨\nWelcome back to the tour of Peli’s Agent Factory. Day 2 is our first stop on the factory floor: Issue Triage.\nIt’s one of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes the report, replies with helpful context, and applies labels consistently — so maintainers can spend more time building and less time sorting.\nTour + links to the workflow source:\nhttps://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/\n#GitHubNext #AI #DevOps"
+      "content": "Meet the Workflows (1): Issue Triage 🍬✨\nWelcome back to the tour of Peli’s Agent Factory. Day 2 is our first stop on the factory floor: Issue Triage.\nIt’s one of the most immediately useful agentic workflows we run: when a new issue lands, the agent analyzes the report, replies with helpful context, and applies labels consistently — so maintainers can spend more time building and less time sorting.\nTour + links to the workflow source:\nhttps://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows/\n#GitHubNext #AI #DevOps"
     }
   }
 }
diff --git a/socials/published/2026-01-23.json b/socials/published/2026-01-23.json
index 37cdb43ea1..9a4afa5e0f 100644
--- a/socials/published/2026-01-23.json
+++ b/socials/published/2026-01-23.json
@@ -7,20 +7,20 @@
     "x": {
       "id": "dryrun-x-2026-01-23",
       "url": "https://twitter.com/i/web/status/dryrun-x-2026-01-23",
-      "content": "Day 3 in Peli’s Agent Factory 🍫✨: Continuous Simplicity.\nTwo agents that run continuously to keep code simple 🧹🤖\n- Automatic Code Simplifier\n- Duplicate Code Detector\nTour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #GitHubNext #AI #DevOps"
+      "content": "Day 3 in Peli’s Agent Factory 🍫✨: Continuous Simplicity.\nTwo agents that run continuously to keep code simple 🧹🤖\n- Automatic Code Simplifier\n- Duplicate Code Detector\nTour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #GitHubNext #AI #DevOps"
     },
     "bluesky": {
       "uri": "at://dryrun/bluesky/2026-01-23",
-      "content": "Day 3 in Peli’s Agent Factory 🍫✨: Continuous Simplicity.\nWhile humans sprint ahead, these agents trail along simplifying recently-changed code and spotting semantic duplication (with Serena). Tour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/"
+      "content": "Day 3 in Peli’s Agent Factory 🍫✨: Continuous Simplicity.\nWhile humans sprint ahead, these agents trail along simplifying recently-changed code and spotting semantic duplication (with Serena). Tour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/"
     },
     "mastodon": {
       "id": "dryrun-mastodon-2026-01-23",
       "url": "",
-      "content": "Day 3 in Peli’s Agent Factory 🍫🔧: Continuous Simplicity 🧹🤖\nTwo quiet maintainers:\n- Automatic Code Simplifier\n- Duplicate Code Detector\nTour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #Automation #GitHub"
+      "content": "Day 3 in Peli’s Agent Factory 🍫🔧: Continuous Simplicity 🧹🤖\nTwo quiet maintainers:\n- Automatic Code Simplifier\n- Duplicate Code Detector\nTour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/ #Automation #GitHub"
     },
     "linkedin": {
       "id": "dryrun-linkedin-2026-01-23",
-      "content": "Day 3 in Peli’s Agent Factory: Continuous Simplicity 🍫✨\nAfter issue triage, the next stop on our tour are agents that continuously simplify code!\nTwo workflows:\n- Automatic Code Simplifier 🧹 \n- Duplicate Code Detector 🤖\nTour + workflow source links:\nhttps://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/\n#GitHubNext #AI #DevOps #Automation"
+      "content": "Day 3 in Peli’s Agent Factory: Continuous Simplicity 🍫✨\nAfter issue triage, the next stop on our tour are agents that continuously simplify code!\nTwo workflows:\n- Automatic Code Simplifier 🧹 \n- Duplicate Code Detector 🤖\nTour + workflow source links:\nhttps://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity/\n#GitHubNext #AI #DevOps #Automation"
     }
   }
 }
diff --git a/socials/published/2026-01-24.json b/socials/published/2026-01-24.json
index 9bdc92d53b..b3d9e6e581 100644
--- a/socials/published/2026-01-24.json
+++ b/socials/published/2026-01-24.json
@@ -7,20 +7,20 @@
     "x": {
       "id": "dryrun-x-2026-01-24",
       "url": "https://twitter.com/i/web/status/dryrun-x-2026-01-24",
-      "content": "Day 4 in Peli’s Agent Factory 🍫✨: Continuous Refactoring.\nTwo agents that keep codebases structurally tidy 🧠🔧\n- Semantic Function Refactor (finds functions in the “wrong” file)\n- Go Pattern Detector (fast AST scan + deep agent review)\nTour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #GitHubNext #AI #DevOps"
+      "content": "Day 4 in Peli’s Agent Factory 🍫✨: Continuous Refactoring.\nTwo agents that keep codebases structurally tidy 🧠🔧\n- Semantic Function Refactor (finds functions in the “wrong” file)\n- Go Pattern Detector (fast AST scan + deep agent review)\nTour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #GitHubNext #AI #DevOps"
     },
     "bluesky": {
       "uri": "at://dryrun/bluesky/2026-01-24",
-      "content": "Day 4 in Peli’s Agent Factory 🍫✨: Continuous Refactoring.\nThese agents look past “does it work?” and ask “does it live in the right place?” One does whole-repo semantic grouping (with Serena) to spot misplaced/outlier functions; the other uses ast-grep to cheaply detect patterns, then escalates to an agent only when needed.\nTour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/"
+      "content": "Day 4 in Peli’s Agent Factory 🍫✨: Continuous Refactoring.\nThese agents look past “does it work?” and ask “does it live in the right place?” One does whole-repo semantic grouping (with Serena) to spot misplaced/outlier functions; the other uses ast-grep to cheaply detect patterns, then escalates to an agent only when needed.\nTour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/"
     },
     "mastodon": {
       "id": "dryrun-mastodon-2026-01-24",
       "url": "",
-      "content": "Day 4 in Peli’s Agent Factory 🍫🔧: Continuous Refactoring 🧠🧹\nTwo maintainers with a structural view:\n- Semantic Function Refactor (whole-repo organization)\n- Go Pattern Detector (AST pattern scan → agent review)\nTour + source links: https://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #Automation #GitHub"
+      "content": "Day 4 in Peli’s Agent Factory 🍫🔧: Continuous Refactoring 🧠🧹\nTwo maintainers with a structural view:\n- Semantic Function Refactor (whole-repo organization)\n- Go Pattern Detector (AST pattern scan → agent review)\nTour + source links: https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/ #Automation #GitHub"
     },
     "linkedin": {
       "id": "dryrun-linkedin-2026-01-24",
-      "content": "Day 4 in Peli’s Agent Factory: Continuous Refactoring 🍫✨\nAfter continuous simplification, the next stop on our tour is structural refactoring: agents that scan the whole codebase and flag opportunities to improve organization and consistency.\nTwo workflows:\n- Semantic Function Refactor 🧠 — groups functions by purpose and highlights “outliers” that likely belong elsewhere\n- Go Pattern Detector 🔍 — uses fast AST pattern matching (ast-grep), and only triggers deeper agent analysis when it finds a match\nTour + workflow source links:\nhttps://githubnext.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/\n#GitHubNext #AI #DevOps #Automation"
+      "content": "Day 4 in Peli’s Agent Factory: Continuous Refactoring 🍫✨\nAfter continuous simplification, the next stop on our tour is structural refactoring: agents that scan the whole codebase and flag opportunities to improve organization and consistency.\nTwo workflows:\n- Semantic Function Refactor 🧠 — groups functions by purpose and highlights “outliers” that likely belong elsewhere\n- Go Pattern Detector 🔍 — uses fast AST pattern matching (ast-grep), and only triggers deeper agent analysis when it finds a match\nTour + workflow source links:\nhttps://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring/\n#GitHubNext #AI #DevOps #Automation"
     }
   }
 }