Add worker deployment CLI deprecation notice

.github/workflows/npm-release.yml

@@ -1,18 +1,13 @@
-name: NPM Release
+name: NPM Release Disabled
 
 on:
-  push:
   workflow_dispatch:
 
-permissions:
-  id-token: write
-  contents: write
+permissions: {}
 
 jobs:
-  release:
-    uses: udx/reusable-workflows/.github/workflows/npm-release-ops.yml@master
-    with:
-      release_branch: "latest"
-      dist_dir: "."
-    secrets:
-      slack_webhook_url: ${{ secrets.SLACK_WEBHOOK_URL }}
+  release-disabled:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Report release status
+        run: echo "NPM releases are disabled for this deprecated CLI."

CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to this project will be documented in this file.
 
+## [Unreleased]
+
+### Added
+
+- Added a repository notice that the `@udx/worker-deployment` CLI is entering
+  maintenance mode and new workflow work should prefer repo-owned Rabbit/worker
+  contracts and `dev.kit` guidance.
+
+### Changed
+
+- Disabled the automated npm release workflow to prevent repo-driven package
+  releases while the currently published CLI remains available.
+
 ## [3.0.4] - 2026-02-05
 
 ### Fixed

README.md

@@ -1,5 +1,14 @@
 # Worker Deploy
 
+[![Status: maintenance mode](https://img.shields.io/badge/status-maintenance%20mode-yellow)](https://github.com/udx/worker-deployment/blob/latest/docs/deprecation.md)
+
+> Deprecation notice: the `@udx/worker-deployment` CLI is entering
+> maintenance mode. Existing automation can keep using it during the transition,
+> and the current npm package remains available, but no new package releases are
+> planned. New UDX workflow work should prefer repo-owned Rabbit/worker
+> contracts and `dev.kit` guidance instead of adopting this CLI directly. See
+> [docs/deprecation.md](https://github.com/udx/worker-deployment/blob/latest/docs/deprecation.md).
+
 Run any Docker container with automatic cloud authentication.
 Requires Node/npm and Docker.
 

docs/commands/worker-run.md

@@ -1,5 +1,10 @@
 # worker-run
 
+> Deprecation notice: direct CLI usage is in maintenance mode. Keep existing
+> automation working during migration, but prefer repo-owned Rabbit/worker
+> contracts and `dev.kit` guidance for new workflow work. See
+> [../deprecation.md](../deprecation.md).
+
 Runs a Docker container using `deploy.yml` and auto-detected credentials.
 
 ## Usage

docs/deprecation.md

@@ -0,0 +1,32 @@
+# Worker Deployment CLI Deprecation Notice
+
+`@udx/worker-deployment` is entering maintenance mode.
+
+Existing repositories and automation can keep using the currently published npm
+CLI while their workflow contracts are migrated, but no new package releases are
+planned. New UDX workflow work should avoid adopting the CLI as a fresh
+integration point. Prefer repo-owned Rabbit/worker contracts, checked-in
+deployment manifests, and `dev.kit` guidance for discovery and execution.
+
+## What this means
+
+- Existing `worker run`, `worker config`, `worker gen`, and `worker images`
+  usage remains documented for transition support.
+- The current npm package remains available for existing users.
+- The automated npm release workflow has been disabled to prevent repo-driven
+  package releases.
+- New feature work should happen in the owning workflow, worker, or repo
+  contract rather than expanding this CLI.
+- No removal date is set yet.
+
+## Migration direction
+
+Move repository workflows toward checked-in, reviewable contracts:
+
+- workflow and deployment manifests owned by the repository
+- Rabbit/worker execution contracts for repeatable automation
+- `dev.kit` repo context for discovery, validation, and next-step guidance
+
+When updating a repository that still calls this CLI directly, keep the existing
+command working first, then move the durable behavior into the repo-owned
+contract that should replace it.

docs/index.md

@@ -2,6 +2,7 @@
 
 Short, focused docs live here.
 
+- docs/deprecation.md
 - docs/commands/worker-config.md
 - docs/commands/worker-run.md
 - docs/commands/worker-gen.md