fix: add includeVFS parameter to getRelations() - VFS now visible

CRITICAL BUG FIX - VFS Files Were Completely Invisible

Workshop Team Issue:
- Import created 569 VFS files
- vfs.readdir('/') returned 0 items
- VFS was 100% unusable

Root Cause:
v4.4.0 added includeVFS to brain.find() but FORGOT brain.getRelations().
PathResolver.getChildren() calls getRelations() to find VFS relationships,
but those were being excluded by default - making ALL VFS files invisible!

Fix:
1. Add includeVFS parameter to GetRelationsParams interface
2. Wire includeVFS filtering in brain.getRelations()
   - Excludes VFS relationships by default (metadata.isVFS != true)
   - Include them when includeVFS: true
3. Update VFS to mark all relationships with metadata: { isVFS: true }
   - 7 relate() calls updated in VirtualFileSystem.ts
4. Update PathResolver to use includeVFS: true
   - resolveChild() line 200
   - getChildren() line 229

Impact:
- VFS is now fully functional again
- Consistent with v4.4.0 architecture (VFS separate from knowledge graph)
- All APIs now have includeVFS where needed

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

src/vfs/PathResolver.ts

@@ -199,7 +199,8 @@ export class PathResolver {
     // Get all relationships where parentId contains other entities
     const relations = await this.brain.getRelations({
       from: parentId,
-      type: VerbType.Contains
+      type: VerbType.Contains,
+      includeVFS: true  // v4.5.1: Required to see VFS relationships
     })
 
     // Find the child with matching name
@@ -227,7 +228,8 @@ export class PathResolver {
     // Production-ready: Use graph relationships (VFS creates these in mkdir/writeFile)
     const relations = await this.brain.getRelations({
       from: dirId,
-      type: VerbType.Contains
+      type: VerbType.Contains,
+      includeVFS: true  // v4.5.1: Required to see VFS relationships
     })
 
     const validChildren: VFSEntity[] = []