Initialization: created project base & init command logic

[RepoRover]

This pull request introduces foundational configuration and documentation standards for the bfloo project. The changes establish clear guidelines for code documentation, project conventions, commit message formatting, and continuous integration (CI) and release automation. These updates are designed to ensure code quality, consistency, and maintainability across the codebase.

Documentation and Project Guidelines:

• Added a comprehensive agent and contributor guide in AGENTS.md, detailing project structure, key concepts, code conventions, error handling, testing, and common development tasks.
• Introduced TypeScript JSDoc documentation standards in .github/prompts/ts-jsdoc.prompt.md, providing detailed patterns and rules for documenting all exports and complex types.

Commit and Code Quality Automation:

• Implemented a commit message hook in .husky/commit-msg to enforce an expanded conventional commit format, ensuring all commit messages follow a consistent and descriptive pattern.
• Added a pre-commit hook in .husky/pre-commit to automatically run formatting, linting, and type checking before allowing commits.

CI/CD and Release Automation:

• Added a GitHub Actions workflow in .github/workflows/ci.yml to automate linting, formatting checks, type checking, testing, and building on push and pull requests to main and dev branches.
• Introduced a release workflow in .github/workflows/release.yml to build binaries for multiple platforms, generate checksums, and create GitHub releases automatically on new version tags.

Formatting and Ignore Rules:

• Established Prettier formatting configuration in .prettierrc and specified files/directories to ignore in .prettierignore to maintain consistent code style and prevent formatting of unnecessary files. [1] [2]