Add GitHub code quality pipeline

[tuyen-at-work]

No description provided.

[Copilot]

Pull request overview

Adds a GitHub Actions “Code Quality” pipeline to run type-checking, unit tests with coverage reporting, dependency review on PRs, and CodeQL analysis for the TypeScript/JavaScript codebase.

Changes:

• Add a new code-quality.yml workflow running dependency review, typecheck, tests/coverage, build, and CodeQL.
• Extend Vitest coverage reporting to emit json-summary and ignore generated coverage/ output.
• Add a typecheck npm script for CI-friendly TypeScript validation.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
vitest.config.ts	Adds json-summary coverage reporter to generate machine-readable coverage output for CI summaries.
package.json	Introduces a typecheck script used by the workflow.
.gitignore	Ignores coverage/ artifacts produced by Vitest in CI and locally.
.github/workflows/code-quality.yml	New CI workflow for dependency review, unit-quality checks, coverage artifacts/summary, and CodeQL.
.github/codeql/codeql-config.yml	Configures CodeQL query packs and scoping to src/.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[tuyen-at-work]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied both review changes in fe21e7b:

1. Added pull-requests: read to the dependency-review job permissions so the action can fetch PR metadata/diffs.
2. Removed the hardcoded coverage thresholds and Status column from the step summary — the table now just shows metric values, with a note that thresholds are enforced by the test runner (Vitest config).

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.