From c5a41227291775a9110fa49861ad9dcceb529f20 Mon Sep 17 00:00:00 2001
From: Anthony Ronning <101225832+AnthonyRonning@users.noreply.github.com>
Date: Thu, 27 Aug 2026 21:48:57 +0000
Subject: [PATCH] docs: refresh Maple release skills after v3.3.9

---
 .agents/skills/develop-maple-proxy/SKILL.md |  7 +--
 .agents/skills/release-maple/SKILL.md       | 55 +++++++++++++++++++--
 2 files changed, 55 insertions(+), 7 deletions(-)

diff --git a/.agents/skills/develop-maple-proxy/SKILL.md b/.agents/skills/develop-maple-proxy/SKILL.md
index 566c530ae..ce0fcca55 100644
--- a/.agents/skills/develop-maple-proxy/SKILL.md
+++ b/.agents/skills/develop-maple-proxy/SKILL.md
@@ -89,9 +89,10 @@ bodies as untrusted and potentially sensitive.
 ## Preserve publishing boundaries
 
 Maple's current GitHub Release workflow builds, checksums, attests, uploads,
-and re-verifies four native proxy archives. The first post-integration release
-is still the live publication canary. Never create a proxy GitHub tag or
-Release; a proxy-only binary fix ships through a normal Maple patch release.
+and re-verifies four native proxy archives. Maple v3.3.9 proved this integrated
+publication path for macOS arm64, Linux arm64, Linux x86_64, and Windows
+x86_64. Never create a proxy GitHub tag or Release; a proxy-only binary fix
+ships through a normal Maple patch release.
 
 Crates.io publishing remains separately versioned and manual. On an authorized
 publish, inspect the exact package first:
diff --git a/.agents/skills/release-maple/SKILL.md b/.agents/skills/release-maple/SKILL.md
index 61e7db54a..178fae5d9 100644
--- a/.agents/skills/release-maple/SKILL.md
+++ b/.agents/skills/release-maple/SKILL.md
@@ -109,9 +109,14 @@ gh api --method POST repos/OpenSecretCloud/Maple/releases/generate-notes \
 ```
 
 Confirm the notes span the intended changes and recheck that `head_sha` is
-still `origin/master`. Present the tag, commit, previous tag, and notes to the
-user before creating the release unless the current request already gives
-unambiguous authority for that exact release.
+still `origin/master`. GitHub's generated body is changelog input, not a
+complete public release description. Draft a concise user-facing summary and
+highlights from the exact release diff, place them above the generated notes,
+and review the complete Markdown in a temporary `notes_file`. Do not publish a
+PR-list-only description when the release has meaningful product changes.
+Present the tag, commit, previous tag, and final notes to the user before
+creating the release unless the current request already gives unambiguous
+authority for that exact release.
 
 ## Publish once
 
@@ -122,7 +127,7 @@ gh release create "$tag" \
   --repo OpenSecretCloud/Maple \
   --target "$head_sha" \
   --title "$tag" \
-  --generate-notes
+  --notes-file "$notes_file"
 ```
 
 Do not create or push a local tag first. Record the release URL and confirm the
@@ -169,6 +174,27 @@ before reporting Maple web production current. A failure in either sibling is
 reported and repaired in that workflow without changing the completed release
 artifacts.
 
+Confirm the production ref and inspect Cloudflare's exact-commit check:
+
+```bash
+pages_sha="$(gh api repos/OpenSecretCloud/Maple/git/ref/heads/pages-production --jq .object.sha)"
+[[ "$pages_sha" == "$head_sha" ]]
+
+gh api "repos/OpenSecretCloud/Maple/commits/$head_sha/check-runs" --jq '
+  [.check_runs[]
+   | select(.name == "Cloudflare Pages")
+   | select(.app.name == "Cloudflare Workers and Pages")
+   | {status, conclusion, started_at, completed_at, details_url}]'
+```
+
+Require a completed successful Cloudflare Pages check corresponding to the
+production-branch promotion, not merely an older preview check on the same
+commit. Inspect its `details_url` when the commit has multiple Pages checks.
+A raw `curl` from an automated VM may be denied by Cloudflare edge policy; a
+Cloudflare-owned successful production check is deployment proof, while an
+allowed-browser smoke is separate live-application evidence. Record either
+boundary instead of turning an edge-policy 403 into a release failure.
+
 On failure, read the failed logs before acting:
 
 ```bash
@@ -206,6 +232,27 @@ separately from the Maple application version. Do not report crates.io or GHCR
 as updated unless their independent publisher was explicitly authorized and
 verified.
 
+Verify that the hosted updater serves the same metadata as the GitHub Release:
+
+```bash
+updater_dir="$(mktemp -d)"
+
+curl --fail --silent --show-error --location --max-time 20 \
+  https://updates.trymaple.ai/latest.json >"$updater_dir/hosted.json"
+curl --fail --silent --show-error --location --max-time 20 \
+  https://github.com/OpenSecretCloud/Maple/releases/latest/download/latest.json \
+  >"$updater_dir/github.json"
+
+jq -e --arg version "$version" '.version == $version' \
+  "$updater_dir/hosted.json" "$updater_dir/github.json"
+jq -S . "$updater_dir/hosted.json" >"$updater_dir/hosted.canonical.json"
+jq -S . "$updater_dir/github.json" >"$updater_dir/github.canonical.json"
+cmp "$updater_dir/hosted.canonical.json" "$updater_dir/github.canonical.json"
+```
+
+Do not report updater publication complete from workflow status alone: require
+the public endpoint to return the intended version and content.
+
 Zapstore starts only after `Release` succeeds and is strictly best effort. Its
 queued, running, skipped, or failed state must not delay release completion,
 trigger a release retry, or be reported as a Maple release failure. Inspect it