The service accepts a submitted repository or archive, runs jscpd on it, and returns a structured duplication report as JSON. Scans run reliably and failures return clear error messages.

This is task 1 of 5 of the project "Duplication validation SaaS with AI-era insights".

SaaS service for code quality validation based on jscpd. The service should have fresh ideas that can be suggested to end users in AI coding era.

Navigation map:

1. Wrap jscpd in a scan API — this task
2. Add projects, accounts, and scan history — a later task, not part of this one
3. Build a duplication dashboard with hotspots — a later task, not part of this one
4. Add AI-era duplication insights — a later task, not part of this one
5. Integrate pull request checks and alerts — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When a session tracks code health, every check scores it as one composite: duplication, complexity and dead code in the code you commit, plus your tests (the share failing) and their coverage once ololo can run them. So name both commands: a test: line that runs the suite and a coverage: line that runs it with coverage measured, in AGENTS.md or README.md (or test and coverage scripts in package.json). The task's health bonus is paid on that score.

When this task is done, write .ololo/task-1-done.md with a short description of what you changed and why (at least 10 words).

Users can sign in, register projects, and trigger scans that are stored with timestamps. Each project shows its previous scan results so changes can be compared over time.

This is task 2 of 5 of the project "Duplication validation SaaS with AI-era insights".

SaaS service for code quality validation based on jscpd. The service should have fresh ideas that can be suggested to end users in AI coding era.

Navigation map:

1. Wrap jscpd in a scan API — done before this task
2. Add projects, accounts, and scan history — this task
3. Build a duplication dashboard with hotspots — a later task, not part of this one
4. Add AI-era duplication insights — a later task, not part of this one
5. Integrate pull request checks and alerts — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-2-done.md with a short description of what you changed and why (at least 10 words).

Users can view duplication rates, trends across scans, and a ranked list of the files and blocks with the most duplicated code. Each hotspot links to the exact duplicated locations.

This is task 3 of 5 of the project "Duplication validation SaaS with AI-era insights".

SaaS service for code quality validation based on jscpd. The service should have fresh ideas that can be suggested to end users in AI coding era.

Navigation map:

1. Wrap jscpd in a scan API — done before this task
2. Add projects, accounts, and scan history — done before this task
3. Build a duplication dashboard with hotspots — this task
4. Add AI-era duplication insights — a later task, not part of this one
5. Integrate pull request checks and alerts — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-3-done.md with a short description of what you changed and why (at least 10 words).

The service flags duplicate blocks that look generated by AI assistants, such as near-identical functions across modules, and suggests concrete extraction or refactoring options. Users see these suggestions alongside the standard report.

This is task 4 of 5 of the project "Duplication validation SaaS with AI-era insights".

SaaS service for code quality validation based on jscpd. The service should have fresh ideas that can be suggested to end users in AI coding era.

Navigation map:

1. Wrap jscpd in a scan API — done before this task
2. Add projects, accounts, and scan history — done before this task
3. Build a duplication dashboard with hotspots — done before this task
4. Add AI-era duplication insights — this task
5. Integrate pull request checks and alerts — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-4-done.md with a short description of what you changed and why (at least 10 words).

Scans run automatically on pull requests and post a summary with a pass or fail status against user-set duplication thresholds. Teams can receive notifications when a threshold is breached.

This is task 5 of 5 of the project "Duplication validation SaaS with AI-era insights".

SaaS service for code quality validation based on jscpd. The service should have fresh ideas that can be suggested to end users in AI coding era.

Navigation map:

1. Wrap jscpd in a scan API — done before this task
2. Add projects, accounts, and scan history — done before this task
3. Build a duplication dashboard with hotspots — done before this task
4. Add AI-era duplication insights — done before this task
5. Integrate pull request checks and alerts — this task

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-5-done.md with a short description of what you changed and why (at least 10 words).