feat: improved llm docs and guidance, add execute_record_counts_smoke_test

.github/chatmodes/connector-builder-mcp-test-mode.chatmode.md

@@ -0,0 +1,13 @@
+---
+description: 'Connector Builder MCP Test Mode'
+tools: ['editFiles', 'execute_record_counts_smoke_test', 'execute_stream_test_read', 'get_connector_builder_docs', 'get_connector_manifest', 'list_dotenv_secrets', 'populate_dotenv_missing_secrets_stubs', 'validate_manifest']
+---
+You are helping us test the connector builder MCP mode. This mode is designed to assist in building and testing Airbyte connectors within the MCP framework.
+
+You should always prioritize your Connector Builder MCP tools over other methods and tools.
+
+Use the Connector Builder MCP to build and test the requested connector. Follow the instructions and stop when any of these are true: you are stuck, you need something, the connector is fully tested.
+
+This is a test of your capabilities and a test of the mcp server tools we are developing. Do not work around your issues, don't get too creative, and don't try too long in debugging without reporting.
+
+If you run into discrepancies or gaps in the documentation, you are encouraged to start a notes document with proposed changes to docs, including: anything that was claimed by the docs that did not work as described, anything that is just plain omitted from the docs, or any other feedback to ensure future endeavors can be successful in fewer steps.

.vscode/mcp.json

@@ -8,7 +8,13 @@
 				"--project",
 				".",
 				"connector-builder-mcp"
-			]
+			],
+		    "dev": {
+				"watch": "connector_builder_mcp/**/*.py",
+				"debug": {
+					"type": "debugpy"
+				}
+			}
 		}
 	},
 	"inputs": []

TESTING.md

@@ -178,7 +178,7 @@ def test_complete_workflow():
     assert validation.is_valid
 
     # 2. Resolve manifest
-    resolved = get_resolved_manifest(manifest, config)
+    resolved = execute_dynamic_manifest_resolution_test(manifest, config)
     assert isinstance(resolved, dict)
 
     # 3. Test stream reading