fix: correct package name in package-lock.json

[CybotTM]

Summary

• Fix package-lock.json name from fix-timetracker-audit (branch name) to timetracker
• Caused by npm audit fix using the working directory name as package name
• Addresses review comments on PR fix: resolve Node.js audit CI failures #274

Test plan

• Verify package-lock.json has correct name

[gemini-code-assist]

Code Review

This pull request updates the package name in package-lock.json from "fix-timetracker-audit" to "timetracker". The review feedback indicates that while this change is correct, the root cause is the absence of name and version fields in package.json, which are required by npm and should be added to ensure consistency.

[gemini-code-assist]

While this change correctly sets the package name in package-lock.json, it addresses a symptom rather than the root cause. The underlying issue is that package.json is missing the name and version fields. These are considered required fields by npm (see docs). When they are missing, npm infers the package name from the directory name, which can lead to inconsistencies like the one this PR is fixing.

To fix this permanently, please add the name and version fields to package.json. This will provide a single source of truth for your project's identity.

For example, you could add the following to the top of your package.json:

{
  "name": "timetracker",
  "version": "1.0.0",
  ...
}

After updating package.json, running npm install will regenerate package-lock.json correctly based on this information.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.49%. Comparing base (9d24074) to head (955a7e2).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main     #275   +/-   ##
=========================================
  Coverage     81.49%   81.49%           
  Complexity     2579     2579           
=========================================
  Files           172      172           
  Lines          7107     7107           
=========================================
  Hits           5792     5792           
  Misses         1315     1315           

Flag	Coverage Δ
integration	47.47% <ø> (ø)
unit	50.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.