release: bump to 1.0.0-alpha.1 and promote published version to latest dist-tag

Adds a post-publish step that runs:
  npm dist-tag add daemora@<version> latest

so plain `npm install daemora` resolves to the freshly published
version instead of the legacy 2026.1.2-beta.2 JS release pinned to
`latest` from before the rewrite.

Author: UmarFarooq75

.github/workflows/publish.yml

@@ -156,6 +156,20 @@ jobs:
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
+      # Promote the just-published version to `latest` so plain
+      # `npm install daemora` (no tag) gets the new code. Without this,
+      # `latest` stays pinned to whatever stable was published before
+      # (e.g. 2026.1.2-beta.2) and pre-release publishes would only be
+      # reachable via `npm install daemora@alpha`.
+      - name: Promote to latest dist-tag
+        if: |
+          steps.config.outputs.skip != 'true' &&
+          inputs.dry_run != true
+        run: |
+          npm dist-tag add "daemora@${{ steps.config.outputs.version }}" latest
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
       - name: Dry run (no publish)
         if: |
           steps.config.outputs.skip != 'true' &&

package.json

@@ -1,6 +1,6 @@
 {
   "name": "daemora",
-  "version": "1.0.0-alpha.0",
+  "version": "1.0.0-alpha.1",
   "description": "Self-hosted AI agent platform — autonomous, multi-channel, multi-model.",
   "type": "module",
   "license": "AGPL-3.0-or-later",