V33 Gate 3: Refresh MCP docs from tool contract

Regenerate MCP API reference and OpenAPI artifacts from the package-owned AssetPack create tool contract, preserving source-safe Reading and settlement-boundary detail for downstream interface docs.

Validation: pnpm run docs:refresh; pnpm run check:v33-gate3; focused BTD and MCP contract tests; git diff --check; staged actual-secret-shaped scan.

Author: geraldarthurdavis

.bitcode/v33-mcp-api-tool-contracts.json

@@ -125,7 +125,7 @@
   ],
   "sourceEvidence": [
     {
-      "digest": "sha256:89e6b3da4670910348568e172186313fcf7e619af7448f4aacceb28405d4e7b9",
+      "digest": "sha256:ed7ff68bb55bd47afc9c538b346a3df3b4559c4278f21f5551cb00a212d98c03",
       "relativePath": "packages/btd/src/mcp-tool-contract.ts",
       "requiredTokens": [
         {

packages/btd/src/mcp-tool-contract.ts

@@ -146,7 +146,9 @@ export function buildBtdMcpToolContractInputs(): BtdMcpToolContractInput[] {
       description: [
         'Create and execute a Bitcode AssetPack pipeline for complete software engineering Reads.',
         '',
-        'This tool admits source-safe Reading requests, repository/provider ingress, attachments, streaming preference, and Shippable subtype focus.',
+        'This is Bitcode\'s primary Reading pipeline entry point for feature implementation, review, bug repair, technical writing, architecture diagrams, API specifications, frontend scaffolding, scope analysis, implementation planning, and refactor proposals.',
+        'It admits source-safe Reading requests, repository/provider ingress, attachments, streaming preference, and Shippable subtype focus.',
+        'Supported subtypes include pull_request, pr_review, issue, comment, blog_post, diagram, api_spec, frontend_scaffolder, scope_analysis, implementation_plan, and refactor_proposal.',
         'It queues the package-owned AssetPack pipeline and returns source-safe execution, preview, and monitoring metadata.',
         'Protected AssetPack contents remain locked until settlement and rights transfer are admitted by the Protocol/BTD layer.',
       ].join('\n'),

packages/executions-mcp/src/mcp-server/docs/mcp/mcp-api-reference.md

@@ -15,35 +15,15 @@ Core SDIVF pipeline execution with PTRR agent coordination
 
 #### `bitcode://pipelines/asset-pack/create`
 
-Create and execute a Bitcode asset-pack pipeline for complete software engineering reads.
-
-This is Bitcode's most powerful pipeline, capable of:
-• Feature implementation with written assets and optional pull request delivery
-• Comprehensive code reviews with detailed suggestions
-• Bug fixes with root cause analysis and testing
-• Technical documentation and blog posts
-• Architecture diagrams and API specifications
-• Frontend scaffolding for React/Vue/Angular
-• Project scope analysis and implementation planning
-• Code refactoring proposals with impact analysis
-
-Supports multimodal inputs including Figma designs, documents, images, audio, and video.
-Real-time streaming provides live updates during read measurement, asset synthesis, validation, Finish, and connected-interface delivery readiness.
-
-Admitted subtypes:
-• pull_request - Complete feature implementation with PR
-• pr_review - Comprehensive code review with suggestions
-• issue - Bug analysis and fixes with testing
-• comment - Code explanation and documentation
-• blog_post - Technical writing and documentation
-• diagram - Architecture and flow diagrams
-• api_spec - OpenAPI specification generation
-• frontend_scaffolder - Component scaffolding
-• scope_analysis - Project complexity analysis
-• implementation_plan - Detailed technical planning
-• refactor_proposal - Code improvement recommendations
-
-**Complexity**: expert | **Measured BTD Estimate**: 200 $BTD
+Create and execute a Bitcode AssetPack pipeline for complete software engineering Reads.
+
+This is Bitcode's primary Reading pipeline entry point for feature implementation, review, bug repair, technical writing, architecture diagrams, API specifications, frontend scaffolding, scope analysis, implementation planning, and refactor proposals.
+It admits source-safe Reading requests, repository/provider ingress, attachments, streaming preference, and Shippable subtype focus.
+Supported subtypes include pull_request, pr_review, issue, comment, blog_post, diagram, api_spec, frontend_scaffolder, scope_analysis, implementation_plan, and refactor_proposal.
+It queues the package-owned AssetPack pipeline and returns source-safe execution, preview, and monitoring metadata.
+Protected AssetPack contents remain locked until settlement and rights transfer are admitted by the Protocol/BTD layer.
+
+**Complexity**: moderate | **Measured BTD Estimate**: 200 $BTD
 
 **Example**:
 ```json

packages/executions-mcp/src/mcp-server/docs/mcp/mcp-openapi.json

@@ -19,8 +19,8 @@
   "paths": {
     "/mcp/tools/bitcode/pipelines/asset-pack/create": {
       "post": {
-        "summary": "Create and execute a Bitcode asset-pack pipeline for complete software engineering reads.",
-        "description": "Create and execute a Bitcode asset-pack pipeline for complete software engineering reads.\n\nThis is Bitcode's most powerful pipeline, capable of:\n• Feature implementation with written assets and optional pull request delivery\n• Comprehensive code reviews with detailed suggestions\n• Bug fixes with root cause analysis and testing\n• Technical documentation and blog posts\n• Architecture diagrams and API specifications\n• Frontend scaffolding for React/Vue/Angular\n• Project scope analysis and implementation planning\n• Code refactoring proposals with impact analysis\n\nSupports multimodal inputs including Figma designs, documents, images, audio, and video.\nReal-time streaming provides live updates during read measurement, asset synthesis, validation, Finish, and connected-interface delivery readiness.\n\nAdmitted subtypes:\n• pull_request - Complete feature implementation with PR\n• pr_review - Comprehensive code review with suggestions\n• issue - Bug analysis and fixes with testing\n• comment - Code explanation and documentation\n• blog_post - Technical writing and documentation\n• diagram - Architecture and flow diagrams\n• api_spec - OpenAPI specification generation\n• frontend_scaffolder - Component scaffolding\n• scope_analysis - Project complexity analysis\n• implementation_plan - Detailed technical planning\n• refactor_proposal - Code improvement recommendations",
+        "summary": "Create and execute a Bitcode AssetPack pipeline for complete software engineering Reads.",
+        "description": "Create and execute a Bitcode AssetPack pipeline for complete software engineering Reads.\n\nThis is Bitcode's primary Reading pipeline entry point for feature implementation, review, bug repair, technical writing, architecture diagrams, API specifications, frontend scaffolding, scope analysis, implementation planning, and refactor proposals.\nIt admits source-safe Reading requests, repository/provider ingress, attachments, streaming preference, and Shippable subtype focus.\nSupported subtypes include pull_request, pr_review, issue, comment, blog_post, diagram, api_spec, frontend_scaffolder, scope_analysis, implementation_plan, and refactor_proposal.\nIt queues the package-owned AssetPack pipeline and returns source-safe execution, preview, and monitoring metadata.\nProtected AssetPack contents remain locked until settlement and rights transfer are admitted by the Protocol/BTD layer.",
         "operationId": "bitcode___pipelines_asset_pack_create",
         "tags": [
           "Pipeline Management"
@@ -124,7 +124,7 @@
           }
         },
         "x-mcp-tool": {
-          "complexity": "expert",
+          "complexity": "moderate",
           "measuredBtdEstimate": {
             "estimated": 200,
             "factors": [
@@ -135,8 +135,6 @@
           },
           "useCases": [
             "Feature Development",
-            "Test Generation",
-            "Documentation",
             "Code Refactoring"
           ],
           "relatedTools": [

packages/executions-mcp/src/mcp-server/docs/mcp/mcp-specification.json

@@ -19,7 +19,7 @@
       "tools": {
         "bitcode://pipelines/asset-pack/create": {
           "name": "bitcode://pipelines/asset-pack/create",
-          "description": "Create and execute a Bitcode asset-pack pipeline for complete software engineering reads.\n\nThis is Bitcode's most powerful pipeline, capable of:\n• Feature implementation with written assets and optional pull request delivery\n• Comprehensive code reviews with detailed suggestions\n• Bug fixes with root cause analysis and testing\n• Technical documentation and blog posts\n• Architecture diagrams and API specifications\n• Frontend scaffolding for React/Vue/Angular\n• Project scope analysis and implementation planning\n• Code refactoring proposals with impact analysis\n\nSupports multimodal inputs including Figma designs, documents, images, audio, and video.\nReal-time streaming provides live updates during read measurement, asset synthesis, validation, Finish, and connected-interface delivery readiness.\n\nAdmitted subtypes:\n• pull_request - Complete feature implementation with PR\n• pr_review - Comprehensive code review with suggestions\n• issue - Bug analysis and fixes with testing\n• comment - Code explanation and documentation\n• blog_post - Technical writing and documentation\n• diagram - Architecture and flow diagrams\n• api_spec - OpenAPI specification generation\n• frontend_scaffolder - Component scaffolding\n• scope_analysis - Project complexity analysis\n• implementation_plan - Detailed technical planning\n• refactor_proposal - Code improvement recommendations",
+          "description": "Create and execute a Bitcode AssetPack pipeline for complete software engineering Reads.\n\nThis is Bitcode's primary Reading pipeline entry point for feature implementation, review, bug repair, technical writing, architecture diagrams, API specifications, frontend scaffolding, scope analysis, implementation planning, and refactor proposals.\nIt admits source-safe Reading requests, repository/provider ingress, attachments, streaming preference, and Shippable subtype focus.\nSupported subtypes include pull_request, pr_review, issue, comment, blog_post, diagram, api_spec, frontend_scaffolder, scope_analysis, implementation_plan, and refactor_proposal.\nIt queues the package-owned AssetPack pipeline and returns source-safe execution, preview, and monitoring metadata.\nProtected AssetPack contents remain locked until settlement and rights transfer are admitted by the Protocol/BTD layer.",
           "category": "Pipeline Management",
           "subcategory": "asset-pack",
           "inputSchema": {
@@ -107,15 +107,13 @@
           ],
           "useCases": [
             "Feature Development",
-            "Test Generation",
-            "Documentation",
             "Code Refactoring"
           ],
           "relatedTools": [
             "bitcode://monitoring/pipeline/status",
             "bitcode://intelligence/effectiveness/track"
           ],
-          "complexity": "expert",
+          "complexity": "moderate",
           "measuredBtdEstimate": {
             "estimated": 200,
             "factors": [