feat: dev releases from develop branch to PyPI

- New workflow: .github/workflows/dev-release.yml
  - Triggers on every push to develop (+ manual dispatch)
  - Calculates version: X.Y.Z.devN (N = commits since last tag)
  - Patches pyproject.toml at build time (source stays clean)
  - Publishes to PyPI via OIDC (same pypi environment)
  - Install dev builds: pip install --pre specsmith

- Updated docs/site/releasing.md: dev release process documented
- Updated WARP rules: dev releases are automatic, stable via tags only

Stable releases remain tag-triggered from main only.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: tbitcs

.github/workflows/dev-release.yml

@@ -0,0 +1,58 @@
+name: Dev Release
+
+on:
+  push:
+    branches: [develop]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  dev-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Install build tools
+        run: pip install build
+
+      - name: Set dev version
+        run: |
+          # Append .devN suffix based on commit count since last tag
+          BASE_VERSION=$(python -c "from specsmith import __version__; print(__version__)")
+          COMMIT_COUNT=$(git rev-list --count HEAD ^$(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~100))
+          DEV_VERSION="${BASE_VERSION}.dev${COMMIT_COUNT}"
+          echo "DEV_VERSION=${DEV_VERSION}" >> $GITHUB_ENV
+
+          # Patch pyproject.toml with dev version
+          sed -i "s/version = \"${BASE_VERSION}\"/version = \"${DEV_VERSION}\"/" pyproject.toml
+          echo "Building version: ${DEV_VERSION}"
+
+      - run: python -m build
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v7
+        with:
+          name: dev-dist
+          path: dist/
+
+  pypi-dev-publish:
+    needs: dev-build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    continue-on-error: true
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dev-dist
+          path: dist/
+      - name: Publish dev release to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

.warp/rules/documentation-updates.md

@@ -56,10 +56,11 @@ Before every release:
 
 ## Branch Protection
 
-- **NEVER tag a release on develop.** Tags must only be created on main.
-- **NEVER push tags from develop.** The release workflow publishes to PyPI — only main branch releases are allowed.
-- All feature work happens on develop. Releases merge develop → main first, then tag on main.
-- The release workflow has an `if:` guard but this is a process rule, not just a technical one.
+- **NEVER tag a stable release on develop.** Tags must only be created on main.
+- **NEVER push tags from develop.** The stable release workflow publishes to PyPI — only main branch releases are allowed.
+- All feature work happens on develop. Stable releases merge develop → main first, then tag on main.
+- **Dev releases are automatic.** Every push to develop triggers `.devN` pre-release to PyPI.
+- Dev releases use `X.Y.Z.devN` version suffix and require `pip install --pre` to install.
 
 ## Rule
 

docs/site/releasing.md

@@ -148,12 +148,26 @@ After pushing the tag:
 
 ## Automated Publishing
 
+### Stable Releases (main branch)
 When a tag matching `v*` is pushed to `main`, the release workflow automatically:
 
 1. **Builds** sdist + wheel
 2. **Publishes to PyPI** via OIDC trusted publishing (no tokens needed)
 3. **Creates GitHub Release** with auto-generated notes and artifacts
 
+Install: `pip install specsmith`
+
+### Dev Releases (develop branch)
+Every push to `develop` triggers the dev-release workflow:
+
+1. **Calculates** dev version: `X.Y.Z.devN` (N = commits since last tag)
+2. **Builds** sdist + wheel with dev version
+3. **Publishes to PyPI** as a pre-release
+
+Install: `pip install --pre specsmith`
+
+Dev releases let users test features before they ship in a stable release. The `.devN` suffix ensures they sort before the next stable version.
+
 ## Lessons Learned
 
 - **PyPI README is baked at upload time** — if README changes after a release, they won't appear on PyPI until the next release. Always finalize README before tagging.