[dev] [tofikwest] tofik/enhance-vendor-risk-assestment

[github-actions]

This is an automated pull request to merge tofik/enhance-vendor-risk-assestment into dev.
It was created by the [Auto Pull Request] action.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
app	Ready	Preview, Comment	Dec 24, 2025 3:05pm

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
portal	Skipped		Dec 24, 2025 3:05pm

[cursor]

PR Summary

Vendor Risk Assessment flow and UI

• Backend now dedupes by reusing an existing task unless it’s still in_progress, creates an immediate placeholder in_progress task with structured description, then updates it to todo with research results; preserves creator/assignee on reuse and adjusts logging/return fields.
• Frontend renders in_progress vendor risk assessment tasks as a non-interactive skeleton row and polls every 3s until completion.

Stability and data hygiene

• Sanitize vendor websites before triggering batch assessments (ensure protocol, validate URL; only send if valid).
• Fix unstable React list keys across vendor risk assessment cards (certifications, timeline, links) to prevent key collisions.

^{Written by Cursor Bugbot for commit e16542d. This will update automatically on new commits. Configure here.}

[graphite-app]

Graphite Automations

"Auto-assign PRs to Author" took an action on this PR • (12/24/25)

1 reviewer was added to this PR based on Mariano Fuentes's automation.

[cursor]

Early return before hooks violates React Rules

The conditional early return at lines 129-131 occurs before the useState hooks are called. This violates React's Rules of Hooks, which require hooks to be called in the same order on every render. When a task is generating (in_progress status), the skeleton is returned without calling hooks. When generation completes and status changes, hooks will suddenly be called, causing React to throw a "Rendered more hooks than during the previous render" error. The polling mechanism in TaskItems.tsx will trigger this crash when the task finishes.