fix: move engineer job from standard_jobs to library/jobs

AGENTS.md

@@ -39,7 +39,6 @@ When creating or modifying jobs in this repository, you MUST understand which ty
 
 **Current standard jobs**:
 - `deepwork_jobs` - Core job management (define, implement, learn)
-- `engineer` - Domain-agnostic engineering execution (implement, doctor)
 - `deepwork_reviews` - DeepWork job review and quality control workflows
 
 **Editing rules**:
@@ -106,8 +105,7 @@ deepwork/
 │   ├── hooks/            # Hook scripts and wrappers
 │   ├── standard_jobs/    # Built-in job definitions (auto-discovered at runtime)
 │   │   ├── deepwork_jobs/
-│   │   ├── deepwork_reviews/
-│   │   └── engineer/
+│   │   └── deepwork_reviews/
 │   ├── review/           # DeepWork Reviews system (.deepreview pipeline)
 │   ├── schemas/          # Definition schemas (deepreview, doc_spec)
 │   └── utils/            # Utilities (fs, git, yaml, validation)
@@ -224,7 +222,7 @@ Each step:
 
 ### How to Identify Job Types
 
-- **Standard jobs**: Exist in `src/deepwork/standard_jobs/` (currently: `deepwork_jobs`, `deepwork_reviews`, `engineer`)
+- **Standard jobs**: Exist in `src/deepwork/standard_jobs/` (currently: `deepwork_jobs`, `deepwork_reviews`)
 - **Library jobs**: Exist in `library/jobs/`
 - **Bespoke jobs**: Exist ONLY in `.deepwork/jobs/` with no corresponding standard_jobs entry
 

doc/architecture.md

@@ -65,8 +65,7 @@ deepwork/                       # DeepWork tool repository
 │       │   └── gemini_hook.sh  # Shell wrapper for Gemini CLI
 │       ├── standard_jobs/      # Built-in job definitions
 │       │   ├── deepwork_jobs/
-│       │   ├── deepwork_reviews/
-│       │   └── engineer/
+│       │   └── deepwork_reviews/
 │       ├── review/             # DeepWork Reviews system
 │       │   ├── config.py       # .deepreview config parsing + data models
 │       │   ├── discovery.py    # Find .deepreview files in project tree
@@ -618,9 +617,9 @@ DeepWork includes a built-in job called `deepwork_reviews` for managing `.deepre
 - **`add_document_update_rule`** workflow: `analyze_dependencies` → `apply_rule`
   - Adds a review rule to keep a specific documentation file up-to-date when related source files change
 
-### Standard Job: `engineer`
+### Library Job: `engineer`
 
-DeepWork includes a built-in job called `engineer` for domain-agnostic engineering execution. It provides:
+The `engineer` job lives in `library/jobs/engineer/` and is available for users to adopt. It provides domain-agnostic engineering execution:
 
 **Workflows**:
 - **`implement`** workflow: `translate_issue` → `initialize_branch` → `red_tests` → `green_implementation` → `finalize_pr` → `product_sync`

src/deepwork/standard_jobs/engineer/AGENTS.md → library/jobs/engineer/AGENTS.md

@@ -2,8 +2,8 @@
 
 ## Location
 
-This job lives in the DeepWork package source at `src/deepwork/standard_jobs/engineer/`.
-It is loaded directly at runtime by the multi-folder job discovery system.
+This job lives in `library/jobs/engineer/`.
+It is a library job — available for users to adopt but not auto-installed by the DeepWork runtime.
 
 ## File Organization
 
@@ -39,5 +39,5 @@ engineer/
 5. **Requirements bundled**: RFC 2119 spec lives alongside job definition as `requirements.md`
 
 ## Last Updated
-- Date: 2026-03-24
-- From conversation about: Initial creation of the engineer standard job
+- Date: 2026-03-25
+- From conversation about: Moved from standard_jobs to library/jobs