docs: Update rule files to reflect simplified git integration approach

- Remove automatic git workflow features, update to manual --from-branch option, change Part 2 references to completed status

docs/configuration.md

@@ -44,10 +44,6 @@ Taskmaster uses two primary methods for configuration:
           "azureBaseURL": "https://your-endpoint.azure.com/",
           "vertexProjectId": "your-gcp-project-id",
           "vertexLocation": "us-central1"
-        },
-        "tags": {
-          "enabledGitworkflow": false,
-          "autoSwitchTagWithBranch": false
         }
       }
       ```
@@ -86,19 +82,7 @@ Taskmaster uses two primary methods for configuration:
 
 ## Tagged Task Lists Configuration (v0.17+)
 
-Taskmaster includes a tagged task lists system for multi-context task management. The following settings control this functionality:
-
-### Tags Configuration Section
-
-```json
-"tags": {
-  "enabledGitworkflow": false,
-  "autoSwitchTagWithBranch": false
-}
-```
-
-- **`enabledGitworkflow`** (boolean): Enable git branch integration features (Part 2 feature)
-- **`autoSwitchTagWithBranch`** (boolean): Automatically switch tag context when git branch changes
+Taskmaster includes a tagged task lists system for multi-context task management.
 
 ### Global Tag Settings
 
@@ -110,6 +94,14 @@ Taskmaster includes a tagged task lists system for multi-context task management
 
 - **`defaultTag`** (string): Default tag context for new operations (default: "master")
 
+### Git Integration
+
+Task Master provides manual git integration through the `--from-branch` option:
+
+- **Manual Tag Creation**: Use `task-master add-tag --from-branch` to create a tag based on your current git branch name
+- **User Control**: No automatic tag switching - you control when and how tags are created
+- **Flexible Workflow**: Supports any git workflow without imposing rigid branch-tag mappings
+
 ## State Management File
 
 Taskmaster uses `.taskmaster/state.json` to track tagged system runtime information:
@@ -118,14 +110,12 @@ Taskmaster uses `.taskmaster/state.json` to track tagged system runtime informat
 {
   "currentTag": "master",
   "lastSwitched": "2025-06-11T20:26:12.598Z",
-  "branchTagMapping": {},
   "migrationNoticeShown": true
 }
 ```
 
 - **`currentTag`**: Currently active tag context
 - **`lastSwitched`**: Timestamp of last tag switch
-- **`branchTagMapping`**: Mapping between git branches and tag names
 - **`migrationNoticeShown`**: Whether migration notice has been displayed
 
 This file is automatically created during tagged system migration and should not be manually edited.
@@ -133,7 +123,7 @@ This file is automatically created during tagged system migration and should not
 ## Example `.env` File (for API Keys)
 
 ```
-# Required API keys for providers configured in .taskmasterconfig
+# Required API keys for providers configured in .taskmaster/config.json
 ANTHROPIC_API_KEY=sk-ant-api03-your-key-here
 PERPLEXITY_API_KEY=pplx-your-key-here
 # OPENAI_API_KEY=sk-your-key-here
@@ -208,7 +198,7 @@ Google Vertex AI is Google Cloud's enterprise AI platform and requires specific
    VERTEX_LOCATION=us-central1
    ```
 
-5. **In .taskmasterconfig**:
+5. **In .taskmaster/config.json**:
    ```json
    "global": {
      "vertexProjectId": "my-gcp-project-123",