feat(release): draft a set version on dispatch, for lockstep with cryptos-manager (#204)

Refs CryptOS-PKI/cryptos-manager#210

Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Co-authored-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>

Author: Bugs5382

.github/workflows/release-drafter.yml

@@ -12,7 +12,18 @@ name: Release Drafter
 on:
   push:
     branches: [main]
+  # cryptos-manager and cryptos-web are versioned in lockstep, but each repo
+  # resolves its next version from its own labels, so the two drafts can come
+  # out different. Dispatching with a version (no leading "v", e.g.
+  # 0.1.0-rc.2) sets this repo's draft to it. Both drafts must carry the same
+  # version before either is published; the merge freeze keeps a later push
+  # from resolving it again.
   workflow_dispatch:
+    inputs:
+      version:
+        description: "Draft this version instead of the one resolved from labels (no leading v, e.g. 0.1.0-rc.2)"
+        required: false
+        default: ""
 
 permissions:
   contents: read
@@ -44,3 +55,4 @@ jobs:
           first-version: 0.1.0
           prerelease: true
           prerelease-identifier: rc
+          version: ${{ inputs.version }}

README.md

@@ -9,7 +9,7 @@
 
 This is the **only** web UI in the project, by design. CryptOS CA nodes ([`cryptos-node`](https://github.com/CryptOS-PKI/cryptos-node)) do not ship a web frontend in the OS image — they expose mTLS gRPC and that's it. When a fleet operator wants a web UI, they stand up the Fleet Manager (`manager/` backend + this frontend), link nodes to it, and use this UI for day-to-day operations.
 
-Conceptually `manager/` and `web/` are one application split across two repos. The split exists so the backend and frontend can be built, tested, and released on their own cadences while still ending up in a single deployable container image (the frontend bundle is pinned to a specific commit and embedded into `manager/` via `embed.FS`).
+Conceptually `manager/` and `web/` are one application split across two repos. The split exists so the backend and frontend can be built and tested on their own while still ending up in a single deployable container image: the frontend bundle is embedded into `manager/` via `embed.FS`. The two are released in lockstep. The manager's `vX.Y.Z` image embeds this repo's `vX.Y.Z`, so this repo's release is published first, at the same version. Release Drafter resolves each repo's next version from its own labels; if the two drafts differ, dispatch the Release Drafter workflow with a `version` input (for example `0.1.0-rc.2`) to bring one in line.
 
 ## 📂 Layout