feat: add base syntax file and remove outdated Cline rules documentation

Signed-off-by: juliano.barbosa <julianomb@gmail.com>

cline_docs/activeContext.md

@@ -1,41 +1,40 @@
 # Active Context: Neovim Configuration
 
 ## Current Work
-- Initial Memory Bank documentation completed
-- Project structure and requirements fully documented
-- All core documentation files populated with comprehensive information
+- Investigating runtime issues with vim.diagnostic module
+- Troubleshooting syntax.vim file location
+- Analyzing VIMRUNTIME configuration impact
 
 ## Recent Changes
-- Populated all Memory Bank documentation files:
-  - productContext.md: Full Neovim IDE configuration requirements
-  - systemPatterns.md: Detailed architecture and implementation patterns
-  - techContext.md: Complete technical specifications and dependencies
-  - progress.md: Implementation roadmap and tracking
-- Established comprehensive documentation framework
-- Defined complete system architecture and patterns
-- Specified all technical requirements and constraints
+- Identified specific runtime issues affecting LSP functionality:
+  - vim.diagnostic module loading failure
+  - Missing syntax.vim file location
+  - VIMRUNTIME configuration concerns
+- Core installation and basic configuration completed
+- Plugin system (lazy.nvim) initialized and operational
+- Basic editor functionality confirmed working
 
 ## Next Steps
-1. Begin Implementation Phase 1: Core Setup
-   - Initialize base Neovim configuration
-   - Set up lazy.nvim plugin management
-   - Configure basic UI elements
-   - Implement key mapping framework
+1. Runtime Issues Resolution
+   - Locate and fix missing syntax.vim file
+   - Resolve vim.diagnostic module loading
+   - Verify VIMRUNTIME environment configuration
+   - Test LSP functionality after fixes
 
-2. Prepare for Plugin Integration
-   - Install required dependencies
-   - Configure LSP infrastructure
-   - Set up completion system
-   - Implement file navigation
+2. System Verification
+   - Run comprehensive :checkhealth
+   - Verify plugin loading behavior
+   - Test LSP server installations
+   - Confirm diagnostic system operation
 
-3. Start Language Support Configuration
-   - Begin with core languages (Python, Lua)
-   - Configure language servers
-   - Set up debugging infrastructure
-   - Implement formatting tools
+3. Documentation Updates
+   - Document runtime configuration process
+   - Create troubleshooting guide
+   - Update configuration comments
+   - Record solutions for future reference
 
-4. Focus on Performance
-   - Implement lazy loading
-   - Optimize startup time
-   - Configure caching
-   - Monitor resource usage
+4. Performance Monitoring
+   - Track startup time
+   - Monitor plugin load times
+   - Observe memory usage
+   - Document performance metrics