update site links;retries on publish

Author: houstonhaynes

.github/workflows/publish.yml

@@ -11,6 +11,11 @@ on:
         type: boolean
         default: false
         required: true
+      verify_only:
+        description: Verify existing public packages without rebuilding or uploading
+        type: boolean
+        default: false
+        required: true
 
 permissions:
   contents: read
@@ -21,7 +26,7 @@ concurrency:
 
 jobs:
   support:
-    if: github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/tags/v')
+    if: ${{ !inputs.verify_only && (github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/tags/v')) }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
@@ -38,7 +43,7 @@ jobs:
           path: artifacts/nuget-release/0.1.0/public-support/logs/
 
   validate:
-    if: github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/tags/v')
+    if: ${{ !inputs.verify_only && (github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/tags/v')) }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
@@ -67,7 +72,7 @@ jobs:
             artifacts/nuget-release/0.1.0/pack-logs/
 
   publish:
-    if: (github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')) || (github.event_name == 'workflow_dispatch' && inputs.publish)
+    if: ${{ !inputs.verify_only && ((github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')) || (github.event_name == 'workflow_dispatch' && inputs.publish)) }}
     needs: [validate, support]
     runs-on: ubuntu-latest
     environment: production
@@ -94,7 +99,36 @@ jobs:
         env:
           NUGET_API_KEY: ${{ steps.login.outputs.NUGET_API_KEY }}
         run: dotnet run --project tools/NuGetRelease -- publish --confirm 0.1.0
+      - name: Retain publication logs
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: nuget-publication-logs
+          path: artifacts/nuget-release/0.1.0/publish-logs/
+
+  verify-public:
+    if: >-
+      always() && !cancelled() &&
+      (needs.publish.result == 'success' ||
+       (github.event_name == 'workflow_dispatch' && inputs.verify_only && github.ref == 'refs/heads/main'))
+    needs: publish
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-dotnet@v6
+        with:
+          global-json-file: global.json
       - name: Confirm public availability
-        run: dotnet run --project tools/NuGetRelease -- availability
+        timeout-minutes: 65
+        run: dotnet run --project tools/NuGetRelease -- availability --wait-minutes 60
       - name: Compile against NuGet.org alone
         run: dotnet run --project tools/NuGetRelease -- examples --fable --public
+      - name: Retain public consumer evidence
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: nuget-public-consumers
+          path: |
+            artifacts/nuget-release/0.1.0/consumers-public/results.json
+            artifacts/nuget-release/0.1.0/consumers-public/logs/
+            artifacts/nuget-release/0.1.0/consumers-public/resolved-packages/

README.md

@@ -120,9 +120,9 @@ let listAccounts (apiToken: string) =
 
 [`tests/HawaiiApi/Program.fs`](tests/HawaiiApi/Program.fs) exercises the same clients against a loopback server, including a multipart asset upload.
 
-## NuGet release preparation
+## NuGet packages
 
-The first 0.1.0 release is being prepared. The [package catalog](https://fsprojects.github.io/FSharp.CloudEdge/libraries/packages/) lists the intended package IDs and URLs. The [maintainer release guide](docs/nuget-release.md) covers publisher access, the F#/.NET release tool, and the current upstream Fable packaging blocker. Public installation is pending those checks and publication.
+**FSharp.CloudEdge 0.1.0 is available on NuGet.** [Browse all packages](https://www.nuget.org/packages?q=FSharp.CloudEdge), or use the [package catalog](https://fsprojects.github.io/FSharp.CloudEdge/libraries/packages/) for individual package IDs and versioned links. The [installation guide](https://fsprojects.github.io/FSharp.CloudEdge/guide/packages/) explains which packages to reference; examples use `0.1.*` to accept patches. The [maintainer release guide](docs/nuget-release.md) covers publisher access and the F#/.NET release tooling.
 
 ## Local Build
 

docs/nuget-release.md

@@ -1,14 +1,14 @@
 # NuGet release and publisher setup
 
-FSharp.CloudEdge's first release targets **0.1.0** for the 47 projects selected in `FSharp.CloudEdge.Bindings.slnx`. **GitHub Actions builds, validates, and publishes the packages.** Like Furnace, the workflow supports `v*` release tags and manual dispatch. A `v0.1.0` tag must match the configured package version. Local commands below reproduce the checks when investigating a failure; maintainers do not need to upload packages manually.
+FSharp.CloudEdge **0.1.0** is published for the 47 projects selected in `FSharp.CloudEdge.Bindings.slnx`. [Browse the packages on NuGet](https://www.nuget.org/packages?q=FSharp.CloudEdge). **GitHub Actions builds, validates, and publishes the packages.** Like Furnace, the workflow supports `v*` release tags and manual dispatch. A release tag must match the configured package version. Local commands below reproduce the checks when investigating a failure; maintainers do not need to upload packages manually.
 
 NuGet account ownership and publishing authorization are setup tasks independent of GitHub repository administration. This workflow uses **NuGet Trusted Publishing** with GitHub OIDC. GitHub obtains temporary publishing credentials for each run.
 
 ## Release dependencies and validation
 
 The release uses the published **0.1.0** versions of `Xantham.Fable.Core` and `Xantham.Fable.Core.TS` from nuget.org. `publicDependencies` in `config/nuget-release.json` records those versions. Publishing CloudEdge does not require publishing or modifying Xantham.
 
-Release validation builds the 19 site example projects against the candidate CloudEdge packages and public external dependencies, then compiles the Fable examples and checks the site's code snippets. Isolated package caches and resolved-package reports make those checks reproducible. The intended first CloudEdge release remains **0.1.0** until its packages have been published successfully.
+Release validation builds the 19 site example projects against the candidate CloudEdge packages and public external dependencies, then compiles the Fable examples and checks the site's code snippets. Isolated package caches and resolved-package reports make those checks reproducible. Verification of the published **0.1.0** release uses the same consumers with nuget.org as their only source.
 
 The `support` check restores both public Xantham packages, compiles `tests/SupportPackage/Smoke.fs` with .NET and Fable, and executes its key-value and indexer checks in JavaScript. This covers the support bindings used by CloudEdge; upstream inline helper functions are outside this release gate.
 
@@ -48,7 +48,7 @@ Sign into NuGet.org as **houstonhaynes** and create a **Trusted Publishing** pol
 | Scope | Push new packages and package versions |
 | Glob Patterns and Packages | `FSharp.CloudEdge.*` |
 
-Enter the filename only, without `.github/workflows/`. Enter `FSharp.CloudEdge.*` as one line in **Glob Patterns and Packages**. The first release creates 47 new package IDs, so the policy must permit new packages as well as new versions. [NuGet Trusted Publishing setup](https://learn.microsoft.com/en-us/nuget/nuget-org/trusted-publishing).
+Enter the filename only, without `.github/workflows/`. Enter `FSharp.CloudEdge.*` as one line in **Glob Patterns and Packages**. The policy covers all 47 package IDs and permits new packages as well as new versions. [NuGet Trusted Publishing setup](https://learn.microsoft.com/en-us/nuget/nuget-org/trusted-publishing).
 
 In **fsprojects/FSharp.CloudEdge → Settings → Environments**, create the **`production` environment**, matching the policy and publication job. Configure environment branch/tag rules to permit `main` and `v*` release tags as appropriate. The repository owner is `fsprojects`; the NuGet package owner and login user are `houstonhaynes`. These fields identify different things.
 
@@ -86,13 +86,15 @@ Inspect the README, license, dependency versions, source assets, and emitted imp
 
 ## Publish and verify the public feed
 
+**0.1.0 has already been uploaded.** Use **verify_only** to check that release again. The upload instructions below apply to a new, unpublished release version.
+
 Run the **NuGet** workflow on `main` with **publish disabled** first. It builds candidates, checks consumers, and uploads the packages and verification evidence as an artifact. Fix failures before requesting the actual release.
 
 After committing and merging fixes into `main`, use **Actions → NuGet → Run workflow**, choose `main`, and leave **publish** unchecked. The equivalent command is `gh workflow run publish.yml --ref main -f publish=false`. Here `publish.yml` is the workflow filename and `-f publish=false` supplies its boolean input. Rerunning the old tag's job uses the old commit; dispatching on `main` picks up the merged fixes without changing the package version or moving the tag. Enable **publish** only when ready to upload.
 
 GitHub runs the public support binding check alongside candidate package and consumer validation. The publication job requires both jobs to succeed. Package compilation uses two MSBuild processes on the standard runner; uploads remain ordered by dependency.
 
-When account ownership, the Trusted Publishing policy, and candidate checks are complete, push the release tag **`v0.1.0`**, or run the workflow manually with **publish enabled**. GitHub repeats validation, obtains temporary credentials, then uploads packages in the manifest's dependency order. A partial upload is possible: NuGet publication is not a transaction across 47 packages. The workflow stops on an upload error rather than silently skipping an existing version. Inspect ownership, versions, and package contents before deciding how to resume.
+For a new release, when account ownership, the Trusted Publishing policy, and candidate checks are complete, push the matching **`v*` release tag**, or run the workflow manually with **publish enabled**. GitHub repeats validation, obtains temporary credentials, then uploads packages in the manifest's dependency order. A partial upload is possible: NuGet publication is not a transaction across 47 packages. The workflow stops on an upload error rather than silently skipping an existing version. Inspect ownership, versions, and package contents before deciding how to resume.
 
 NuGet package versions are immutable. Do not publish a placeholder `0.1.0` as a test. If an uploaded version is wrong, unlisting does not free that version for replacement; publish a corrected version. [NuGet publication behavior](https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/publish-nuget-package).
 
@@ -103,6 +105,8 @@ dotnet run --project tools/NuGetRelease -- availability
 dotnet run --project tools/NuGetRelease -- examples --fable --public
 ```
 
-The workflow performs these public checks after pushing. A processing delay can make the checks fail even after an upload succeeds. Resolve public availability and repeat the checks before announcing success; do not republish different bytes with the same version.
+The workflow performs these public checks in a separate `verify-public` job after pushing. Availability checks wait up to 60 minutes for NuGet processing, retrying pending packages and temporary network/server failures every 30 seconds. `availability` alone checks once; `availability --wait-minutes 60` enables the same wait locally. NuGet validation and indexing are asynchronous after a successful upload. [NuGet processing](https://learn.microsoft.com/en-us/nuget/nuget-org/publish-a-package#package-validation-and-indexing).
+
+If public verification times out after successful uploads, rerun only the failed verification job. To verify packages from a previous run, dispatch the workflow on `main` with **verify_only** checked; that mode skips candidate builds, authentication, and uploads, even if **publish** is also checked. The command is `gh workflow run publish.yml --ref main -f verify_only=true`. Publication logs and public consumer results are retained as separate artifacts. A verification failure does not undo an upload or require a version bump; do not repeat the upload of an existing version.
 
-Finally, update the release-availability paragraph in `site/content/guide/packages.md`, deploy the site, and announce the release. Package IDs, `0.1.0` references, and NuGet URLs can be prepared beforehand with that pending-release notice. The beginner path should not claim public installation works until the public consumer checks pass.
+For future releases, update the availability paragraph in `site/content/guide/packages.md` and the catalog's versioned NuGet links after public verification, then deploy the site and announce the release.

site/Site.fs

@@ -8,6 +8,8 @@ open Partas.Nacara.Theme
 
 let baseUrl = "/FSharp.CloudEdge/"
 
+let private nugetUrl = "https://www.nuget.org/packages?q=FSharp.CloudEdge"
+
 let private themeCss name =
     File.ReadAllText (Path.Combine (__SOURCE_DIRECTORY__, "theme", name))
 
@@ -262,7 +264,11 @@ let theme =
                     Menu.page "libraries/control-plane/clients.md"
                 ]
         ]
-    |> Theme.navbarEnd [ NavbarIcon ("GitHub", "https://github.com/fsprojects/FSharp.CloudEdge", Icons.github) ]
+    |> Theme.navbarEnd
+        [
+            NavbarLink ("NuGet", nugetUrl)
+            NavbarIcon ("GitHub", "https://github.com/fsprojects/FSharp.CloudEdge", Icons.github)
+        ]
     |> Theme.editUrl "https://github.com/fsprojects/FSharp.CloudEdge/edit/main/site"
     |> Theme.lightTokens lightColours
     |> Theme.darkTokens darkColours
@@ -275,6 +281,8 @@ let theme =
         Html.p
             [
                 Html.text "FSharp.CloudEdge · MIT · "
+                Html.a [ prop.href nugetUrl; prop.text "NuGet" ]
+                Html.text " · "
                 Html.a [ prop.href "https://github.com/fsprojects/FSharp.CloudEdge"; prop.text "GitHub" ]
                 Html.text " · Built with Nacara"
             ]

site/content/guide/first-worker.md

@@ -14,7 +14,7 @@ order: 4
 
 ## Project Folder
 
-Create the application anywhere convenient. It restores `FSharp.CloudEdge.Runtime.Workers` from the `0.1.*` patch series on NuGet; no sibling library checkout is required. See [Packages](packages.md) for release availability and candidate-feed testing.
+Create the application anywhere convenient. It restores [`FSharp.CloudEdge.Runtime.Workers`](https://www.nuget.org/packages/FSharp.CloudEdge.Runtime.Workers) from the `0.1.*` patch series on NuGet; no sibling library checkout is required. See [Packages](packages.md) for installation guidance and links to the full package family.
 
 1. Open a terminal in the folder where you keep your projects.
 2. Create `hello-worker` and enter it.

site/content/guide/packages.md

@@ -8,9 +8,9 @@ Application projects reference the FSharp.CloudEdge libraries by NuGet package I
 
 ## Release availability
 
-The first `0.1.0` release is being prepared. Package links and examples name the intended public versions; they do not assert that publication has completed. The release uses the published `Xantham.Fable.Core` and `Xantham.Fable.Core.TS` **0.1.0** packages from nuget.org. Until CloudEdge publication and public validation are complete, use the [contributor source build](local-build.md).
+All **47 packages** in the **0.1.0** release are published on nuget.org. [Browse all FSharp.CloudEdge packages on NuGet](https://www.nuget.org/packages?q=FSharp.CloudEdge), or use the [package catalog](../libraries/packages.md) to find a specific library.
 
-The release order is: validate candidate packages and consumers, publish dependencies before their consumers, confirm every `0.1.0` package restores from nuget.org, then announce availability. A package page appearing in search is separate from a clean restore succeeding.
+The release uses the published `Xantham.Fable.Core` and `Xantham.Fable.Core.TS` **0.1.0** packages. Application projects restore these dependencies through NuGet; contributors can use the [source build](local-build.md) when regenerating or changing the bindings.
 
 ## Add the package your application uses
 
@@ -34,7 +34,7 @@ The NuGet feed is `https://api.nuget.org/v3/index.json`. A package page such as
 
 ## Fable and npm dependencies
 
-CloudEdge's runtime and Fable support candidates contain their F# source as well as .NET assemblies. Fable uses that source when compiling the application to JavaScript. NuGet restores the published Xantham support dependencies transitively. Release validation compiles the site's actual examples against this package combination. Application developers do not run the binding generators.
+CloudEdge's runtime and Fable support packages contain their F# source as well as .NET assemblies. Fable uses that source when compiling the application to JavaScript. NuGet restores the published Xantham support dependencies transitively. Release validation compiles the site's actual examples against this package combination. Application developers do not run the binding generators.
 
 NuGet does not install the upstream JavaScript SDKs. Where an example imports an npm SDK, install the exact package version shown on its library page. Worker-native APIs such as `Request`, D1, and R2 are supplied by the Workers runtime. The platform type declarations describe those APIs; they are not a JavaScript runtime implementation to bundle.
 

site/content/index.md

@@ -14,6 +14,7 @@ layout: splash
 <div class="ce-actions">
 <a class="ce-btn ce-btn--primary" href="#building-blocks">See what you can build <svg aria-hidden="true" viewBox="0 0 24 24" width="16" height="16" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 5v14"/><path d="m19 12-7 7-7-7"/></svg></a>
 <a class="ce-btn ce-btn--secondary" href="/FSharp.CloudEdge/libraries/">Library line-up</a>
+<a class="ce-btn ce-btn--secondary" href="https://www.nuget.org/packages?q=FSharp.CloudEdge">Browse packages on NuGet</a>
 </div>
 </div>
 <figure class="ce-code" aria-label="A Durable Object that counts requests, written in F#">

site/content/libraries/index.md

@@ -30,4 +30,4 @@ The capability pages describe integration boundaries and areas that need runtime
 
 See [installation and release availability](../guide/packages.md).
 
-The [NuGet package catalog](packages.md) lists every package ID and its versioned `0.1.0` URL.
+[Browse all FSharp.CloudEdge packages on NuGet](https://www.nuget.org/packages?q=FSharp.CloudEdge). The [package catalog](packages.md) lists every package ID and its versioned `0.1.0` URL.

site/content/libraries/packages.md

@@ -3,7 +3,9 @@ title: NuGet Package Catalog
 description: Versioned package IDs and links for the FSharp.CloudEdge 0.1.0 release.
 ---
 
-The selected release contains **47 packages**, all version **0.1.0**: 31 runtime bindings, three AI contract libraries, one Workers support library, shared API models, and eleven control-plane clients. These links name the intended public package versions. Check [release availability](../guide/packages.md#release-availability) before restoring the first release.
+The **0.1.0** release contains **47 published packages**: 31 runtime bindings, three AI contract libraries, one Workers support library, shared API models, and eleven control-plane clients.
+
+[Browse all FSharp.CloudEdge packages on NuGet](https://www.nuget.org/packages?q=FSharp.CloudEdge). The links below open each package's **0.1.0** page; the [installation guide](../guide/packages.md) shows how to add them to your project.
 
 | Package ID | Version | Target | Consumer |
 | --- | --- | --- | --- |