refactor: point draft-release.yml at release/draft@v1

.github/workflows/draft-release.yml

@@ -4,7 +4,7 @@
 # See docs/ReleaseProcess.md for why this is the only way in and why a
 # release is a deliberate decision, not something every merge does.
 #
-# Nothing is rebuilt here - it just triggers; draft-release takes the
+# Nothing is rebuilt here - it just triggers; release/draft takes the
 # artifacts CI already produced, for this commit or for a named version.
 #
 # 'uses' can't take an expression, so bumping the major version is an edit
@@ -41,12 +41,12 @@ jobs:
           fetch-depth: 0 # The changelog needs all the history and tags
 
       - name: Draft the release
-        uses: TaffarelJr/.actions/draft-release@v1
+        uses: TaffarelJr/.actions/release/draft@v1
         with:
           version: ${{ inputs.version }}
         env:
           # Must be set here, at the workflow level - an env var set on a
-          # *nested* composite action's own step (draft-release calling
+          # *nested* composite action's own step (release/draft calling
           # ai-inference) does not reliably reach the action it calls; only
           # one set by the calling workflow cascades down through every
           # layer. This is what lets the Copilot CLI, several layers deep,

docs/ReleaseProcess.md

@@ -291,7 +291,7 @@ store, or rotate.
 The permission alone is not enough, though: `draft-release.yml` still
 passes `GH_TOKEN: ${{ github.token }}` explicitly, at the workflow level.
 An environment variable set on a *nested* composite action's own step —
-`draft-release` calling `ai-inference` — does not reliably reach the
+`release/draft` calling `ai-inference` — does not reliably reach the
 action it calls; only one set by the calling workflow cascades down
 through every layer, which is what actually lets the Copilot CLI, several
 layers deep, see the token.
@@ -314,7 +314,7 @@ and the release drafting — lives in the separate
 [`TaffarelJr/.actions`][actionsRepo] repo as composite actions,
 and is shared by every consumer, `.github` included.
 This repo's own `draft-release.yml` is a shell:
-it checks out the history and calls the `draft-release` action,
+it checks out the history and calls the `release/draft` action,
 and is identical in every repo in the chain.
 
 A layer contributes two things, both in its own workflows:

scripts/Common-GitHub.psm1

@@ -756,7 +756,7 @@ function Get-ManualCiWorkflow {
             Steps = @(
                 "Build and test this repo's own code."
                 "Produce a version.txt and upload a 'packages' artifact -"
-                "or whatever names draft-release's build-workflow/artifact-name."
+                "or whatever names release/draft's build-workflow/artifact-name."
                 'Via a short-lived branch and PR; rulesets require it.'
             )
         }