ci: remove lost-commit check — merge-to-main-first is the rule, not a guarded invariant

Author: marc0olo

.claude/docs-guidelines.md

@@ -54,7 +54,7 @@ git branch -D temp/docs-fix-vX.Y               # local branch no longer needed
 
 The commits remain reachable via the tag — no remote branch is needed.
 
-**On the next release:** `sync-docs-tag.yml` resets `docs/vX.Y` to the release commit. Because the fix was already merged to `main`, the release will contain it, and the reset preserves it. The CI will emit a warning if commits would be lost, giving the release driver a chance to verify.
+**On the next release:** `sync-docs-tag.yml` resets `docs/vX.Y` to the release commit. Because the fix was already merged to `main`, the release will contain it, and the reset preserves it automatically.
 
 ## Writing Guidelines
 

.claude/skills/release/task6-docs.md

@@ -7,7 +7,7 @@ The tag push triggers two automated workflows:
 1. **`docs.yml` (`publish-versioned-docs` job):** Builds and publishes the versioned docs to `/X.Y/` on the `docs-deployment` branch (served at `https://cli.internetcomputer.org/X.Y/`). The `versions.json` PR must not be merged until that deployment succeeds, otherwise the root redirect will point to a path that does not exist yet.
 
 2. **`sync-docs-tag.yml`:** Creates or moves the `docs/vX.Y` tag to the new release commit — no manual action required. This keeps the docs-override tag in sync with the latest patch. Because the tag is moved via `GITHUB_TOKEN`, the push does not re-trigger `docs.yml` (GitHub prevents recursive workflow runs from `GITHUB_TOKEN` pushes).
-   - If `docs/vX.Y` had commits not present in the release (i.e. docs-only fixes applied between patches), the workflow emits a CI warning. Those commits must already be in `main` — if they are, the reset is safe and the changes survive in the release. If they are not, escalate to the release driver before proceeding.
+   - The reset overwrites any docs-only commits that were on `docs/vX.Y` but not in the release. This is safe as long as the "merge to main first" rule was followed — those commits will be in the release itself. See `.claude/docs-guidelines.md` → "Docs-Only Fixes for Released Versions".
 
 Once the `versions.json` PR merges to `main`, the `publish-root-files` CI job runs automatically and copies `og-image.png`, `llms.txt`, `llms-full.txt`, and `feed.xml` from the new version's folder to the deployment root — no manual step needed.
 

.github/workflows/sync-docs-tag.yml

@@ -46,24 +46,6 @@ jobs:
           echo "MINOR=${MINOR}" >> $GITHUB_ENV
           echo "DOCS_TAG=docs/v${MINOR}" >> $GITHUB_ENV
 
-      - name: Warn if docs tag has commits not in release
-        run: |
-          # If docs/vX.Y already exists and has commits that are NOT in the release tag,
-          # those commits were docs-only fixes applied between releases. They WILL be
-          # overwritten by the reset below. Warn loudly so the release driver can verify
-          # those changes are already merged to main (and therefore baked into this release).
-          if git ls-remote --exit-code --tags origin "refs/tags/${DOCS_TAG}" > /dev/null 2>&1; then
-            git fetch origin "refs/tags/${DOCS_TAG}:refs/tags/${DOCS_TAG}" 2>/dev/null || true
-            EXTRA=$(git log --oneline "${TAG}..refs/tags/${DOCS_TAG}" 2>/dev/null || true)
-            if [[ -n "$EXTRA" ]]; then
-              echo "::warning::${DOCS_TAG} has commits not in ${TAG} that will be overwritten:"
-              echo "$EXTRA" | while read -r line; do
-                echo "::warning::  $line"
-              done
-              echo "::warning::Ensure these changes are merged to main so they survive future releases."
-            fi
-          fi
-
       - name: Create or move docs tag to release commit
         run: |
           if git ls-remote --exit-code --tags origin "refs/tags/${DOCS_TAG}" > /dev/null 2>&1; then