- Created TODO files for Testing, DBAL, Frontend, Packages, Database, and Lua Scripting.
- Updated README with a quick reference table for all TODO files and their priorities.
- Added specific tasks for improving testing coverage, implementing DBAL features, enhancing frontend components, and refining package management.
- Included documentation tasks to ensure thorough coverage and clarity across all areas.
- Implemented initial unit tests for the useAuth hook and improved password generation logic.
- Enhanced package loader functionality to support modular package seed data retrieval.
- Updated page renderer to include public role in permission checks.
- Added comments for future unit tests in workflow engine and other critical areas.
- Add missing radix-ui dependencies for shadcn/ui components
- Fix mockImplementation() to include callback in package-loader test
- Remove broken @/dbal/* alias from tsconfig (DBAL path needs reconfiguration)
- Add node types to tsconfig
- Create useAuth hook for authentication state management
- Export useAuth and useIsMobile correctly from hooks/index.ts
- Fix listWorkflowRuns to listWorkflowRunsForRepo (correct Octokit API)
- Add level property to AuthUser interface for permission system
- Fix package-integration.test.ts import paths (../../ → ../../../../)
- Add localStorage mock to useKV.test.ts
- Use unique keys in falsy value tests to avoid KV store collisions
Add AuthProvider component for user authentication management
Implement users API route with DBAL integration
Create layout component for application structure and metadata
Add Level1Client component for navigation handling
- Deleted Test.xml and TAG files from the Testing directory as they are no longer needed.
- Removed cmake_install.cmake script which contained installation instructions for the project.
- Cleared compile_commands.json as it is outdated and not relevant to the current build process.
- Successfully organized all MetaBuilder documentation into a clear, hierarchical structure.
- Created new navigation files including a master index and a new contributor path.
- Updated existing documentation files to reflect the new structure.
- Reduced root-level clutter by organizing configuration files into dedicated directories.
- Added new configuration files for ESLint, Next.js, Playwright, and Vite.
- Created example schemas and size limits reports for better project insights.
- Removed deprecated Vite config backups to streamline the project.
- Created a new troubleshooting guide in README.md for common issues and testing problems.
- Updated package.json to include new act commands for linting, type checking, building, and diagnosing workflows.
- Added a pre-commit hook script to validate workflows before commits.
- Enhanced run-act.sh script with logging, Docker checks, and improved output formatting.
- Improved test-workflows.sh with an interactive menu and performance tracking.
- Introduced setup-act.sh for quick setup and testing of act integration.
- Created COMPONENT_VIOLATION_ANALYSIS.md to document the analysis and refactoring strategy for oversized components, detailing current issues, refactoring plans, and implementation checklists for each component.
- Introduced STATE_MANAGEMENT_GUIDE.md to establish a unified state management strategy, outlining current state distribution, a decision tree for state categorization, and best practices for local, global, database, and cache state management.
- Introduced DOCUMENTATION_FINDINGS.md for a detailed analysis of project documentation, covering architecture, technology stack, completed features, and known issues.
- Created security documentation in README.md and SECURITY.md, outlining security policies, best practices, and incident response procedures.
- Added TESTING_GUIDELINES.md to establish unit testing best practices, including directory structure, parameterized tests, and test coverage enforcement.
- Created multiple test files for utility functions and hooks, ensuring coverage for all core functionalities.
- Developed test infrastructure scripts for analyzing and reporting test coverage.
- Added detailed testing guidelines and quick reference documentation for developers.
- Established a unit test checklist to track implementation progress and ensure best practices.
- Updated the documentation index to include new testing resources and guides.
