feat: Grant Data Quality Score (#166) - #183

Process completed with exit code 1.

AssertionError: expected { id: '1', …(12) } to match object { difficulty: 'advanced', …(2) } (11 matching properties omitted from actual) - Expected + Received { "difficulty": "advanced", - "organization": "Stellar Development Foundation", "technologies": [ "Rust", "Soroban", ], } ❯ src/lib/tasks-list-api.test.ts:41:23

AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ src/lib/notification-store.test.ts:39:40

EnvironmentTeardownError: Cannot load '/src/lib/activity-store.ts' imported from /home/runner/work/Task-Bounty/Task-Bounty/frontend/src/lib/activity-store.test.ts after the environment was torn down. This is not a bug in Vitest. The last recorded callstack: - /src/lib/activity-store.ts - /home/runner/work/Task-Bounty/Task-Bounty/frontend/src/lib/activity-store.test.ts - /home/runner/work/Task-Bounty/Task-Bounty/frontend/src/test/regression.test.ts ❯ src/lib/activity-store.test.ts:2:1 This error originated in "src/test/regression.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'futureDateIso' is defined but never used

'INVALID_TASK_SCHEMA_PRESENT_DEADLINE' is defined but never used

'INVALID_TASK_SCHEMA_PAST_DEADLINE' is defined but never used

'now' is assigned a value but never used

'ErrorCodes' is defined but never used

'createError' is defined but never used

'modified' is assigned a value but never used

'ActivityRecord' is defined but never used

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element