Merge branch 'main' into dependabot/uv/cryptography-46.0.6

Author: nhorton

.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
     {
       "name": "deepwork",
       "description": "Framework for AI-powered multi-step workflows with quality gates",
-      "version": "0.9.8",
+      "version": "0.10.0",
       "source": "./plugins/claude",
       "author": {
         "name": "DeepWork"

.deepreview

@@ -14,6 +14,8 @@ prompt_best_practices:
       - "platform/**/*.md"
       - "src/deepwork/standard_jobs/**/*.md"
       - "library/jobs/**/*.md"  # library job step instructions are prompt-heavy files
+      - "library/jobs/*/job.yml"          # inline step instructions in job.yml are prompt-heavy
+      - "src/deepwork/standard_jobs/*/job.yml"  # standard job inline instructions
       - "**/.deepreview"       # .deepreview files contain inline agent instructions — prompt-heavy content
   review:
     strategy: individual
@@ -249,6 +251,7 @@ update_documents_relating_to_src_deepwork:
       - "CLAUDE.md"
       - "doc/architecture.md"
       - "doc/mcp_interface.md"
+      - "doc/job_yml_guidance.md"  # Describes job.yml runtime behavior — must stay in sync with parser/schema
       - "doc/doc-specs.md"
       - "doc/platforms/**"
       - "src/deepwork/hooks/README.md"
@@ -264,6 +267,7 @@ update_documents_relating_to_src_deepwork:
       - CLAUDE.md (project structure, tech stack, CLI commands, architecture)
       - doc/architecture.md (detailed architecture, module descriptions, data flow)
       - doc/mcp_interface.md (MCP tool parameters, return values, server config)
+      - doc/job_yml_guidance.md (job.yml field descriptions, runtime behavior, review cascade)
       - doc/doc-specs.md (doc spec format, parser behavior, quality criteria)
       - doc/platforms/claude/ (Claude-specific hooks, CLI config, learnings)
       - doc/platforms/gemini/ (Gemini-specific hooks, CLI config, learnings)
@@ -430,44 +434,43 @@ deepreview_config_quality:
         and a specific recommendation.
 
 job_schema_instruction_compatibility:
-  description: "Verify deepwork_jobs instruction files, templates, and examples are compatible with the job schema."
+  description: "Verify deepwork_jobs job.yml inline instructions are compatible with the job schema."
   match:
     include:
       - "src/deepwork/jobs/job.schema.json"
-      - "src/deepwork/standard_jobs/deepwork_jobs/steps/*.md"
-      - "src/deepwork/standard_jobs/deepwork_jobs/templates/*"
       - "src/deepwork/standard_jobs/deepwork_jobs/job.yml"
+      - "src/deepwork/standard_jobs/deepwork_reviews/job.yml"
+      - "src/deepwork/standard_jobs/deepwork_jobs/templates/job.yml.*"  # Templates users copy — must match schema
+      - "library/jobs/*/job.yml"
   review:
     strategy: matches_together
     additional_context:
       unchanged_matching_files: true
     instructions: |
-      When the job schema or deepwork_jobs instruction files change, verify they
-      are still compatible with each other.
+      When the job schema, standard job definitions, or library job definitions
+      change, verify they are still compatible with each other.
 
       Read src/deepwork/jobs/job.schema.json to understand the current schema.
-      Then read each instruction file, template, and example in
-      src/deepwork/standard_jobs/deepwork_jobs/ and check:
+      Then read each job.yml (standard and library) and check:
 
-      1. **Field references**: Every field name mentioned in prose instructions,
-         templates, or examples must exist in the schema at the correct level.
-         Pay special attention to root-level vs step-level fields — a field
-         that exists on steps may not exist at the root, and vice versa.
+      1. **Field references**: Every field name referenced in inline step
+         instructions must exist in the schema at the correct level.
+         Pay special attention to step_arguments vs workflow vs step fields.
 
       2. **Required vs optional**: If instructions say a field is required,
          verify the schema agrees. If instructions say a field is optional,
          verify the schema doesn't require it.
 
-      3. **Schema structure**: Template files and examples that show YAML
-         structure must match the schema's property names and nesting.
+      3. **Schema structure**: Any YAML examples shown in inline instructions
+         must match the schema's property names and nesting.
 
       4. **Terminology consistency**: Instructions should use the same field
          names as the schema (e.g., if the schema uses
          "common_job_info_provided_to_all_steps_at_runtime", instructions
          should not call it "description" or "job_description").
 
       Output Format:
-      - PASS: All instruction files are compatible with the schema.
+      - PASS: All job definitions are compatible with the schema.
       - FAIL: Incompatibilities found. List each with the file path, line
         reference, the incompatible content, and what the schema actually says.
 
@@ -526,3 +529,35 @@ nix_claude_wrapper:
       Output Format:
       - PASS: The claude wrapper is correctly configured with both plugin dirs.
       - FAIL: Describe what is missing or broken.
+
+mcp_interface_consumer_sync:
+  description: "When MCP tool interfaces change, verify that skills, hooks, and platform content still reference correct parameter names, types, and behavior."
+  match:
+    include:
+      - "src/deepwork/jobs/mcp/tools.py"
+      - "src/deepwork/jobs/mcp/schemas.py"
+      - "src/deepwork/jobs/mcp/server.py"
+  review:
+    strategy: matches_together
+    additional_context:
+      unchanged_matching_files: true
+    instructions: |
+      When the MCP tool interfaces (tools.py, schemas.py, server.py) change,
+      verify that downstream consumers still accurately describe the MCP
+      interface. Check each of these files for stale parameter names, removed
+      fields, renamed concepts, or outdated behavior descriptions:
+
+      - platform/skill-body.md
+      - plugins/claude/skills/deepwork/SKILL.md
+      - plugins/gemini/skills/deepwork/SKILL.md
+      - plugins/claude/hooks/post_compact.sh
+      - doc/mcp_interface.md
+
+      For each file, compare any MCP parameter names, tool names, response
+      fields, or workflow behavior descriptions against the actual schemas
+      and tool implementations. Flag anything that no longer matches.
+
+      Output Format:
+      - PASS: All consumer files are consistent with the current MCP interface.
+      - FAIL: List each inconsistency with the file, the stale content, and
+        what it should say based on the current implementation.

.github/workflows/README.md

@@ -102,18 +102,8 @@ All checks will pass in both PR and merge queue contexts (either by running or b
 
 ### prepare-release.yml
 - **Triggers**: `workflow_dispatch` with inputs: `version`, `release_type` (stable/alpha/beta/rc), `prerelease_number`, `ref`
-- **Stable releases**: Creates a `release/<version>` branch, bumps versions in pyproject.toml/plugin.json/marketplace.json, updates CHANGELOG.md, runs `uv sync`, and opens a PR with the `release` label
-- **Pre-releases**: Checks out the specified `ref` branch, bumps versions (PEP 440 for PyPI, semver for plugin.json), pins `.mcp.json` to the pre-release PyPI package, force-pushes to the `pre-release` branch, tags, and creates a GitHub Release directly (no PR)
-
-### publish-release.yml
-- **Triggers**: `pull_request` (closed) — only when merged with the `release` label
-- **Jobs**: Extracts version from PR title, creates a git tag, extracts release notes from CHANGELOG.md, and creates a GitHub Release
-- Uses `RELEASE_TOKEN` (PAT) so the created release triggers `release.yml`
-
-### prepare-release.yml
-- **Triggers**: `workflow_dispatch` with inputs: `version`, `release_type` (stable/alpha/beta/rc), `prerelease_number`, `ref`
-- **Stable releases**: Creates a `release/<version>` branch, bumps versions in pyproject.toml/plugin.json/marketplace.json, updates CHANGELOG.md, runs `uv sync`, and opens a PR with the `release` label
-- **Pre-releases**: Checks out the specified `ref` branch, bumps versions (PEP 440 for PyPI, semver for plugin.json), pins `.mcp.json` to the pre-release PyPI package, force-pushes to the `pre-release` branch, tags, and creates a GitHub Release directly (no PR)
+- **Stable releases**: Creates a `release/<version>` branch, bumps versions in pyproject.toml/__init__.py/plugin.json/marketplace.json, updates CHANGELOG.md, runs `uv sync`, and opens a PR with the `release` label
+- **Pre-releases**: Checks out the specified `ref` branch, bumps versions in pyproject.toml/__init__.py/plugin.json/marketplace.json (PEP 440 for PyPI, semver for plugin.json/marketplace.json), pins `.mcp.json` to the pre-release PyPI package, force-pushes to the `pre-release` branch, tags, and creates a GitHub Release directly (no PR)
 
 ### publish-release.yml
 - **Triggers**: `pull_request` (closed) — only when merged with the `release` label

.github/workflows/claude-code-test.yml

@@ -68,34 +68,36 @@ jobs:
           job = parse_job_definition(Path('tests/fixtures/jobs/fruits'))
 
           assert job.name == 'fruits'
-          assert job.version == '1.0.0'
-          assert len(job.steps) == 2
-          assert [s.id for s in job.steps] == ['identify', 'classify']
-
-          # Identify step: user input -> file output
-          identify = job.steps[0]
-          assert identify.inputs[0].is_user_input()
-          assert identify.inputs[0].name == 'raw_items'
-          assert identify.outputs[0].name == 'identified_fruits.md'
-          assert identify.dependencies == []
-
-          # Classify step: file input from identify -> file output
-          classify = job.steps[1]
-          assert classify.inputs[0].is_file_input()
-          assert classify.inputs[0].file == 'identified_fruits.md'
-          assert classify.inputs[0].from_step == 'identify'
-          assert classify.outputs[0].name == 'classified_fruits.md'
-          assert classify.dependencies == ['identify']
+          assert job.summary is not None
+
+          # Step arguments (shared input/output definitions)
+          arg_names = [a.name for a in job.step_arguments]
+          assert 'raw_items' in arg_names
+          assert 'identified_fruits' in arg_names
+          assert 'classified_fruits' in arg_names
 
           # Workflow definition
-          assert len(job.workflows) == 1
-          assert job.workflows[0].name == 'full'
-          assert job.workflows[0].steps == ['identify', 'classify']
-
-          # Validations pass
-          job.validate_dependencies()
-          job.validate_file_inputs()
-          job.validate_workflows()
+          assert 'full' in job.workflows
+          wf = job.workflows['full']
+          assert wf.step_names == ['identify', 'classify']
+
+          # Identify step: raw_items input -> identified_fruits output
+          identify = wf.get_step('identify')
+          assert identify is not None
+          assert 'raw_items' in identify.inputs
+          assert 'identified_fruits' in identify.outputs
+
+          # Classify step: identified_fruits input -> classified_fruits output
+          classify = wf.get_step('classify')
+          assert classify is not None
+          assert 'identified_fruits' in classify.inputs
+          assert 'classified_fruits' in classify.outputs
+
+          # Validations pass (parse_job_definition already runs these, but verify they don't raise)
+          job.validate_unique_step_names()
+          job.validate_argument_refs()
+          job.validate_sub_workflows()
+          job.validate_step_exclusivity()
 
           print('All fruits fixture validations passed!')
           "

.github/workflows/prepare-release.yml

@@ -203,6 +203,15 @@ jobs:
           # Verify the change
           grep "^version = " pyproject.toml
 
+      # --- Both: update __init__.py version ---
+      - name: Update __init__.py version
+        run: |
+          VERSION="${{ steps.versions.outputs.pypi_version }}"
+          sed -i "s/^__version__ = \".*\"/__version__ = \"$VERSION\"/" src/deepwork/__init__.py
+
+          # Verify the change
+          grep "^__version__" src/deepwork/__init__.py
+
       # --- Both: update plugin.json files ---
       - name: Update plugin versions
         run: |
@@ -264,6 +273,7 @@ jobs:
         run: |
           VERSION="${{ steps.versions.outputs.pypi_version }}"
           git add CHANGELOG.md pyproject.toml uv.lock .claude-plugin/marketplace.json \
+            src/deepwork/__init__.py \
             $(find . -path '*/.claude-plugin/plugin.json')
           git commit -m "Release v${VERSION}"
           git push -u origin "release/${VERSION}"
@@ -305,7 +315,7 @@ jobs:
 
           # Force-push to the `pre-release` branch.
           # This is the branch users subscribe to via:
-          #   /plugin marketplace add Unsupervisedcom/deepwork#pre-release
+          #   claude plugin marketplace add Unsupervisedcom/deepwork#pre-release
           git push origin HEAD:refs/heads/pre-release --force
 
           # Tag for the GitHub Release
@@ -323,8 +333,8 @@ jobs:
 
             **To use this pre-release**, subscribe to the pre-release plugin channel:
             ```
-            /plugin marketplace add Unsupervisedcom/deepwork#pre-release
-            /plugin install deepwork@deepwork-plugins
+            claude plugin marketplace add Unsupervisedcom/deepwork#pre-release
+            claude plugin install deepwork@deepwork-plugins
             ```
           draft: false
           prerelease: true