Fix docs workflow failure by correcting blog metadata and broken spec links (#34702)

* Plan docs build fix for blog metadata length

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Shorten blog SEO description to satisfy schema

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Fix broken outcomes spec links in docs

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Author: Copilot

docs/src/content/docs/blog/2026-05-25-agent-of-the-day.md

@@ -5,7 +5,7 @@ authors:
   - copilot
 date: 2026-05-25
 metadata:
-  seoDescription: "Architecture Guardian: a daily GitHub Actions workflow that detects oversized functions, large files, excess exports, and import cycles in Go and JavaScript code."
+  seoDescription: "Architecture Guardian: a daily GitHub workflow that detects oversized functions, large files, excess exports, and import cycles in Go and JavaScript code."
   linkedPostText: "Architecture Guardian keeps Go & JS code clean, automatically"
 ---
 

docs/src/content/docs/reference/model-tables.md

@@ -28,8 +28,10 @@ Vendor aliases map a short name to one or more provider-scoped glob patterns. Th
 | `opus` | `copilot/*opus*`, `anthropic/*opus*` |
 | `gpt-4.1` | `copilot/gpt-4.1*`, `openai/gpt-4.1*` |
 | `gpt-5` | `copilot/gpt-5*`, `openai/gpt-5*` |
+| `gpt-5.5` | `copilot/gpt-5.5*`, `openai/gpt-5.5*` |
 | `gpt-5.4` | `copilot/gpt-5.4*`, `openai/gpt-5.4*` |
 | `gpt-5.3` | `copilot/gpt-5.3*`, `openai/gpt-5.3*` |
+| `gpt-5.2` | `copilot/gpt-5.2*`, `openai/gpt-5.2*` |
 | `gpt-5-mini` | `copilot/gpt-5*mini*`, `openai/gpt-5*mini*` |
 | `gpt-5-nano` | `copilot/gpt-5*nano*`, `openai/gpt-5*nano*` |
 | `gpt-5-codex` | `copilot/gpt-5*codex*`, `openai/gpt-5*codex*` |
@@ -47,6 +49,7 @@ Vendor aliases map a short name to one or more provider-scoped glob patterns. Th
 | `gemini-3-flash` | `copilot/gemini-3*flash*`, `google/gemini-3*flash*`, `gemini/gemini-3*flash*` |
 | `gemini-3.1-pro` | `copilot/gemini-3.1*pro*`, `google/gemini-3.1*pro*`, `gemini/gemini-3.1*pro*` |
 | `gemini-3.1-flash` | `copilot/gemini-3.1*flash*`, `google/gemini-3.1*flash*`, `gemini/gemini-3.1*flash*` |
+| `gemini-3.5-flash` | `copilot/gemini-3.5*flash*`, `google/gemini-3.5*flash*`, `gemini/gemini-3.5*flash*` |
 | `antigravity` | `copilot/antigravity*`, `google/antigravity*`, `gemini/antigravity*` |
 | `computer-use` | `copilot/*computer-use*`, `google/*computer-use*`, `gemini/*computer-use*`, `openai/*computer-use*` |
 | `robotics` | `copilot/*robotics*`, `google/*robotics*`, `gemini/*robotics*` |
@@ -125,14 +128,22 @@ Before per-model multipliers are applied, raw token counts are weighted by token
 | Model | Multiplier |
 |-------|-----------|
 | `gpt-4o` | 0.33 |
+| `gpt-4o-2024-05-13` | 0.33 |
+| `gpt-4o-2024-08-06` | 0.33 |
+| `gpt-4o-2024-11-20` | 0.33 |
 | `gpt-4o-mini` | 0.33 |
+| `gpt-4o-mini-2024-07-18` | 0.33 |
 | `gpt-4.1` | 1 |
 | `gpt-4.1-2025-04-14` | 1 |
 | `gpt-41-copilot` | 1 |
 | `gpt-4.1-mini` | 1 |
 | `gpt-4.1-nano` | 1 |
 | `gpt-4-turbo` | 1 |
 | `gpt-4` | 1 |
+| `gpt-4-0613` | 1 |
+| `gpt-4-o-preview` | 1 |
+| `gpt-3.5-turbo` | 0 |
+| `gpt-3.5-turbo-0613` | 0 |
 | `gpt-5` | 1 |
 | `gpt-5-2025-08-07` | 1 |
 | `gpt-5-search-api` | 1 |

docs/src/content/docs/reference/outcomes.md

@@ -42,7 +42,7 @@ Accepted outcomes are intentionally simpler than a full value model. They do not
 
 The table below is the quick lookup for what `accepted` currently means for each safe output type and whether that meaning comes from a dedicated rule, a fallback rule, a limited check, or no implemented rule yet.
 
-Rows marked `fallback rule` use a generic existence check, not a type-specific rule. For exact rules, edge cases, and conformance details, see [Safe Output Outcome Evaluation Specification](/gh-aw/specs/safe-output-outcome-evaluation/).
+Rows marked `fallback rule` use a generic existence check, not a type-specific rule. For exact rules, edge cases, and conformance details, see [Safe Output Outcome Evaluation Specification](https://github.com/github/gh-aw/blob/main/specs/safe-output-outcome-evaluation.md).
 
 Outcome evaluation is based on visible repository state and visible actor identity. A non-bot actor may still be AI-assisted; the lookup reflects what the system can observe, not hidden authoring provenance.
 
@@ -107,4 +107,4 @@ Those questions may matter later, but they are separate from the base outcomes m
 - [Cost Management](/gh-aw/reference/cost-management/) explains how workflow cost is measured and reduced.
 - [OpenTelemetry](/gh-aw/reference/open-telemetry/) describes the span attributes and artifacts that carry workflow telemetry.
 - [Safe Outputs](/gh-aw/reference/safe-outputs/) explains how workflows produce constrained actions.
-- [Safe Output Outcome Evaluation Specification](/gh-aw/specs/safe-output-outcome-evaluation/) defines the detailed evaluation logic for each safe output type.
+- [Safe Output Outcome Evaluation Specification](https://github.com/github/gh-aw/blob/main/specs/safe-output-outcome-evaluation.md) defines the detailed evaluation logic for each safe output type.

pkg/actionpins/data/action_pins.json

@@ -198,6 +198,11 @@
       "version": "v1.308.0",
       "sha": "97ecb7b512899eb71ab1bf2310a624c6f1589ac6"
     },
+    "safedep/pmg@v1": {
+      "repo": "safedep/pmg",
+      "version": "v1",
+      "sha": "46cc70db535107183c9e752bb55d1d5c5f1a9290"
+    },
     "super-linter/super-linter@v8.6.0": {
       "repo": "super-linter/super-linter",
       "version": "v8.6.0",

pkg/workflow/data/action_pins.json

@@ -198,6 +198,11 @@
       "version": "v1.308.0",
       "sha": "97ecb7b512899eb71ab1bf2310a624c6f1589ac6"
     },
+    "safedep/pmg@v1": {
+      "repo": "safedep/pmg",
+      "version": "v1",
+      "sha": "46cc70db535107183c9e752bb55d1d5c5f1a9290"
+    },
     "super-linter/super-linter@v8.6.0": {
       "repo": "super-linter/super-linter",
       "version": "v8.6.0",