refactor: Restructure unit3 project directory to use descriptive naming

- Move unit3 starter and solution code to build-mcp-server subdirectory
- Update documentation paths to reflect new directory structure
- No functional changes to the code

Author: zealoushacker

projects/unit3/solution/README.md renamed to projects/unit3/build-mcp-server/solution/README.md

@@ -16,7 +16,7 @@
 mcp = FastMCP("pr-agent")
 
 # PR template directory (shared between starter and solution)
-TEMPLATES_DIR = Path(__file__).parent.parent / "templates"
+TEMPLATES_DIR = Path(__file__).parent.parent.parent / "templates"
 
 
 @mcp.tool()

projects/unit3/solution/manual_test.md renamed to projects/unit3/build-mcp-server/solution/manual_test.md

@@ -14,7 +14,7 @@
 mcp = FastMCP("pr-agent")
 
 # PR template directory (shared between starter and solution)
-TEMPLATES_DIR = Path(__file__).parent.parent / "templates"
+TEMPLATES_DIR = Path(__file__).parent.parent.parent / "templates"
 
 
 # TODO: Implement tool functions here

projects/unit3/solution/pyproject.toml renamed to projects/unit3/build-mcp-server/solution/pyproject.toml

@@ -32,7 +32,7 @@ The PR Agent demonstrates a key principle of MCP development: instead of hard-co
 Navigate to the starter code directory:
 
 ```bash
-cd projects/unit3/module1/starter
+cd projects/unit3/build-mcp-server/starter
 ```
 
 Install dependencies:
@@ -146,7 +146,7 @@ except Exception as e:
 ## Next Steps
 
 Once you've completed this module:
-1. Review the solution in `/projects/unit3/module1/solution/`
+1. Review the solution in `/projects/unit3/build-mcp-server/solution/`
 2. Compare your approach with the provided implementation
 3. Move on to Module 2 to add Resources for project context