Add version and changelog update policy

Add a new policy that triggers when files in src/ are modified,
requiring evaluation of whether version bumps and changelog entries
are needed. The policy enforces explicit action - either updating
pyproject.toml and CHANGELOG.md, or justifying why no update is needed.

Author: claude

.deepwork.policy.yml

@@ -40,4 +40,32 @@
     3. Run `deepwork install --platform claude` to sync changes
     4. Verify the changes propagated correctly
 
-    See CLAUDE.md section "CRITICAL: Editing Standard Jobs" for details.
+    See CLAUDE.md section "CRITICAL: Editing Standard Jobs" for details.
+
+- name: "Version and Changelog Update"
+  trigger: "src/**/*"
+  safety:
+    - "pyproject.toml"
+    - "CHANGELOG.md"
+  instructions: |
+    Source code in src/ has been modified. **You MUST evaluate whether version and changelog updates are needed.**
+
+    **Evaluate the changes:**
+    1. Is this a bug fix, new feature, breaking change, or internal refactor?
+    2. Does this change affect the public API or user-facing behavior?
+    3. Would users need to know about this change when upgrading?
+
+    **If version update is needed:**
+    1. Update the `version` field in `pyproject.toml` following semantic versioning:
+       - PATCH (0.1.x): Bug fixes, minor internal changes
+       - MINOR (0.x.0): New features, non-breaking changes
+       - MAJOR (x.0.0): Breaking changes
+    2. Add an entry to `CHANGELOG.md` under an appropriate version header:
+       - Use categories: Added, Changed, Fixed, Removed, Deprecated, Security
+       - Include a clear, user-facing description of what changed
+       - Follow the Keep a Changelog format
+
+    **If NO version update is needed** (e.g., tests only, comments, internal refactoring with no behavior change):
+    - Explicitly state why no version bump is required
+
+    **This policy requires explicit action** - either update both files or justify why no update is needed.