Add README, CI pipelines, linting, and basic test coverage

[thedgarg31]

🚧 Current State

• The repository lacks key project essentials like a README, contribution guidelines, CI workflows, or test suite.
• This makes onboarding difficult and reduces confidence when making changes.

✅ Proposed Enhancements

1. README.md

   • Provide an overview: project goals, tech stack, installation/setup steps, usage instructions, and contribution guidelines.

2. Continuous Integration (CI)

   • Add GitHub Actions workflows to run linting, build verifications, and tests on pushes and PRs.

3. Code Linting & Formatting

   • Introduce tools (e.g. ESLint + Prettier for Node) to enforce consistent coding style.
   • Enforce style checks either in CI or via pre-commit hooks.

4. Unit Testing & Sample Tests

   • Add a testing framework like Jest or Mocha.
   • Include at least two basic tests covering core functionality or sanity/smoke checks.

5. Developer Documentation

   • Explain how to set up the environment, run tests, check linting, and submit contributions.
   • Optionally add issue/PR templates.

🔎 Expected Benefits

• Improves project onboarding for new contributors
• Establishes automated quality checks and consistent code standards
• Forms a stable foundation for future feature development and reliability

🧠 Suggested Stack

• CI: GitHub Actions (lint.yml, test.yml)
• Lint/Format: ESLint + Prettier
• Testing: Jest or Mocha based on existing Node.js setup

🎯 Difficulty Level

Hard – requires setting up documentation, CI/CD, linting, and writing initial tests.

🌟 Why This Is Unique

• No existing issue addressing foundational tooling and documentation is currently visible in the repo.
• Lays crucial groundwork for maintainability, professional polish, and open-source friendliness.