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/types/brainy.types.ts

@@ -324,6 +324,17 @@ export interface GetRelationsParams {
    * Only return relationships belonging to this service.
    */
   service?: string
+
+  /**
+   * Include VFS relationships (v4.5.1)
+   *
+   * By default, getRelations() excludes VFS relationships (since v4.4.0).
+   * Set this to true when you need to traverse VFS structure.
+   *
+   * @default false
+   * @since v4.5.1
+   */
+  includeVFS?: boolean
 }
 
 // ============= Batch Operations =============