AGENTS.md: drop the flavor: full-only caveat on ucrt64

Match the preceding action.yml and README updates. With
`please.sh create-sdk-artifact --architecture=ucrt64` now a working
invocation, all four flavors take the `getViaGit` path successfully
on the `ucrt64` axis, so the table cell and the explanatory
paragraph no longer need to single `full` out.

The ci-artifacts fast path remains suppressed for `ucrt64` because
the `ci-artifacts` release of `git-sdk-64` still carries no UCRT64
asset; reword the paragraph to spell out what that means in practice
(every flavor goes through `please.sh`).

The table-column realignment is a no-op produced by `npm run format`
since the longest cell in the notes column shrank.

Assisted-by: Opus 4.7
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Author: dscho

AGENTS.md

@@ -112,28 +112,27 @@ The Action supports four flavors of the SDK:
 The `architecture` input drives both the underlying `git-sdk-*` repo
 and the `MSYSTEM` / bin-path layout inside the SDK:
 
-| `architecture` | repo            | MSYSTEM      | mingw bin path    | notes                                                                                  |
-| -------------- | --------------- | ------------ | ----------------- | -------------------------------------------------------------------------------------- |
-| `i686`         | `git-sdk-32`    | `MINGW32`    | `/mingw32/bin`    | only `build-installers` and `full`                                                     |
-| `x86_64`       | `git-sdk-64`    | `MINGW64`    | `/mingw64/bin`    | the default; fast path available for `minimal`                                         |
-| `aarch64`      | `git-sdk-arm64` | `CLANGARM64` | `/clangarm64/bin` | only `full` for now                                                                    |
-| `ucrt64`       | `git-sdk-64`    | `UCRT64`     | `/ucrt64/bin`     | UCRT64 migration; cloned from the `ucrt64` branch of `git-sdk-64`; only `full` for now |
+| `architecture` | repo            | MSYSTEM      | mingw bin path    | notes                                                             |
+| -------------- | --------------- | ------------ | ----------------- | ----------------------------------------------------------------- |
+| `i686`         | `git-sdk-32`    | `MINGW32`    | `/mingw32/bin`    | only `build-installers` and `full`                                |
+| `x86_64`       | `git-sdk-64`    | `MINGW64`    | `/mingw64/bin`    | the default; fast path available for `minimal`                    |
+| `aarch64`      | `git-sdk-arm64` | `CLANGARM64` | `/clangarm64/bin` | only `full` for now                                               |
+| `ucrt64`       | `git-sdk-64`    | `UCRT64`     | `/ucrt64/bin`     | UCRT64 migration; cloned from the `ucrt64` branch of `git-sdk-64` |
 
 The `ucrt64` axis is part of the larger UCRT64 migration tracked in
 https://github.com/git-for-windows/git-sdk-64/pull/117 and its
 follow-up comment
 https://github.com/git-for-windows/git-sdk-64/pull/117#issuecomment-4642726384.
 It shares the `git-sdk-64` repository with `x86_64` but is materialised
-from a different long-lived branch, so caches and on-disk directories
-must stay distinct (the artifact name is `git-sdk-ucrt64-<flavor>`
-rather than `git-sdk-64-<flavor>`). The `ci-artifacts` release of
-`git-sdk-64` contains no UCRT64 asset, so the CI-artifacts fast path
-is forcibly skipped for this axis; every flavor takes the
-`getViaGit` path. `build-extra`'s `please.sh create-sdk-artifact` does
-not yet understand `--architecture=ucrt64` either, so right now only
-`flavor: full` (which goes straight through `git worktree add`)
-produces a working SDK. The non-`full` flavors will start working once
-`build-extra` and the `ci-artifacts` pipeline catch up.
+from a separate transitional `ucrt64` branch (which will eventually
+replace `main`), so caches and on-disk directories must stay distinct
+between the two variants (the artifact name is
+`git-sdk-ucrt64-<flavor>` rather than `git-sdk-64-<flavor>`). The
+`ci-artifacts` release of `git-sdk-64` contains no UCRT64 asset, so
+the CI-artifacts fast path is forcibly skipped for this axis; every
+flavor takes the `getViaGit` path, with `please.sh create-sdk-artifact
+--architecture=ucrt64` carving the subset flavors out of the full SDK
+clone exactly as it does for the other architectures.
 
 ## Relationship to other Git for Windows repositories