Revise basicAgent documentation with NodeDev details

Updated agent documentation to include NodeDev instructions and architecture details.

Author: snakex64

.github/agents/basicAgent.agent.md

@@ -0,0 +1,67 @@
+---
+# Fill in the fields below to create a basic custom agent for your repository.
+# The Copilot CLI can be used for local testing: https://gh.io/customagents/cli
+# To make this agent available, merge this file into the default repository branch.
+# For format details, see: https://gh.io/customagents/config
+
+name: Basic dev agent
+description: Used for general purpose NodeDev development
+---
+
+# NodeDev - Copilot Instructions
+
+1) You must always read the documentation files when they are related to your current task. They are described in the "Documentation" section of this document.
+2) You must always run the tests and make sure they are passing before you consider your job as completed, no matter how long you have been at the task or any following instruction to make it short or end the task early.
+3) Disabling, removing, skipping, deleting, bypassing or converting to warnings ANY tests IS NOT ALLOWED and is not considered the right way of fixing a problematic test. The test must be functional and actually testing what it is intended to test.
+4) Document newly added content or concepts in this `.github/agents/basicAgent.agent.md` file or any related documentation file.
+5) When the user corrects major mistakes done during your development, document them in this file to ensure it is never done again.
+
+## Programming style
+
+1) Always use C# nullable
+2) Prefer small polymorphic classes rather than big helper style classes
+3) Write many tests for any newly added feature, whether in the core as unit tests or in the UI as e2e tests
+
+## Overview
+NodeDev is a visual programming environment built with Blazor and Blazor.Diagrams. It allows users to create software using a node-based visual interface instead of traditional text-based code. The system generates native IL code for near-native execution performance.
+
+## Architecture
+
+### Core Components
+- **NodeDev.Core**: Core business logic, node definitions, graph management, type system, and IL code generation
+- **NodeDev.Blazor**: UI components built with Blazor (Razor components, diagrams, project explorer)
+- **NodeDev.Blazor.Server**: Server-side Blazor hosting
+- **NodeDev.Blazor.MAUI**: MAUI-based desktop application wrapper
+- **NodeDev.Tests**: Unit tests for core functionality
+- **NodeDev.EndToEndTests**: Playwright-based E2E tests with Reqnroll (SpecFlow successor)
+
+### UI Structure
+The main UI consists of:
+- **AppBar**: Top toolbar with project controls (New, Open, Save, Options)
+- **ProjectExplorer**: Left panel showing project structure (classes, methods, properties)
+- **GraphCanvas**: Central canvas where nodes are placed and connected
+- **ClassExplorer**: Shows details of the currently selected class
+
+### Graph System
+- Uses Blazor.Diagrams library for visual node editing
+- **GraphNodeModel**: Represents a node in the diagram (wraps Core.Node)
+- **GraphPortModel**: Represents input/output ports on nodes
+- **GraphCanvas**: Main component managing the diagram, node creation, and connections
+
+### Node System
+- **Flow Nodes**: Control execution (Entry, Return, Branch, While, For, etc.) - have Exec connections
+- **Data Nodes**: Compute values without flow (Math operations, comparisons) - no Exec connections
+- **Mixed Nodes**: Both Exec and data (DeclareVariable, SetProperty, etc.)
+- **Generic Types**: Automatically resolve based on connections (T, T1, T2 → concrete types)
+
+## Testing
+- E2E tests use Playwright with Reqnroll for BDD-style scenarios
+- Tests start a Blazor Server instance and automate browser interactions
+- Components use `data-test-id` attributes for test targeting
+- Mouse event sequences critical for drag operations: MoveAsync → DownAsync → MoveAsync(with steps) → UpAsync
+
+## Documentation
+Detailed topic-specific documentation is maintained in the `docs/` folder:
+
+- `docs/e2e-testing.md` - End-to-end testing patterns, node interaction, connection testing, and screenshot validation
+- `docs/node-types-and-connections.md` - Comprehensive guide to node types, connection system, port identification, and testing strategies