feat: Reorganize data layer and enhance testing infrastructure

[serendipity1004]

Summary

• Consolidate data modules into centralized lib/data/ directory for better organization
• Implement new mock-api layer to separate data access from business logic
• Enhance tag system with comprehensive validation utilities and better type safety
• Update comprehensive test infrastructure to match new data organization
• Remove deprecated GitHub workflow files for cleaner repository

Technical Changes

• Data Layer Reorganization: Moved all data modules to src/lib/data/ for centralized access
• Mock API Layer: Created src/lib/mock-api/ to separate data access patterns from data definitions
• Enhanced Tag System: Improved tag validation, normalization, and utility functions
• Test Updates: Comprehensive test suite updates to match new data architecture
• Type Safety: Improved TypeScript interfaces and validation across data layer

Test Coverage

• All existing tests updated and passing
• New test patterns established for data layer architecture
• Mock API functions properly tested with realistic data scenarios

🤖 Generated with Claude Code

[vercel]

@serendipity1004 is attempting to deploy a commit to the Code Factory Pro Team on Vercel.

A member of the Team first needs to authorize it.

[gemini-code-assist]

Summary of Changes

Hello @serendipity1004, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a significant architectural refactor by reorganizing the application's data layer and establishing a clear separation between data definitions and data access logic. It centralizes core data models and synchronous retrieval functions, while simultaneously implementing a dedicated mock API layer to simulate asynchronous operations and complex business logic. This change aims to improve maintainability, scalability, and testability across the codebase, particularly for project and tag management.

Highlights

• Data Layer Centralization: All core data definitions and synchronous access functions for projects, tags, and users have been consolidated into src/lib/data/. This provides a single source of truth for data structures and basic retrieval.
• Dedicated Mock API Layer: A new src/lib/mock-api/ directory has been introduced to house asynchronous API-like functions for projects and users. This layer simulates network delays and complex operations, effectively separating data access patterns from raw data definitions.
• Enhanced Tag System: The tag system has been significantly improved with new Tag and Category interfaces, along with comprehensive utility functions for validation, normalization, and retrieval, ensuring better type safety and organization.
• Comprehensive Test Infrastructure Update: The entire test suite has been updated to align with the new data layer and mock API architecture, ensuring robust testing of both synchronous data access and asynchronous API interactions.
• Repository Cleanup: Deprecated GitHub workflow files have been removed, contributing to a cleaner and more maintainable repository.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The code changes reorganize the data layer and enhance the testing infrastructure. The new data structures in lib/data are well-defined, and the mock API in lib/mock-api provides a clean interface. The updated tests are thorough. I've left comments on TypeScript typings to enhance type safety.

[gemini-code-assist]

Casting projects to any bypasses TypeScript's type checking, potentially hiding bugs. Ensure the Project type from getAllProjects aligns with the ProjectGrid component's expected type. Update the types to match or create a mapping function to transform the project data into the format expected by ProjectGrid.

[gemini-code-assist]

Using any for fullDescriptionJson weakens type safety. Use a more specific type like Record<string, unknown> or a custom interface representing the JSON structure to make the data structure more explicit and easier to work with.

Suggested change

	fullDescriptionJson?: any
	fullDescriptionJson?: Record<string, unknown>