PAB-57: complete project status migration

[pablopunk]

This PR completes the migration from a single project status field to a dual‑state model that tracks desired intent and observed reality independently. The core functional changes are:

• Database migration – Maps every legacy status value to its appropriate desired_status, then drops the now‑retired status column.
• State model – All code references to the old status are replaced by appropriate checks on desiredStatus and/or observedStatus:
  • Desired status (created, running, stopped, deleting) expresses what the system or user wants the project to do.
  • Observed status (unknown, healthy, unhealthy, missing, crashed) reflects the actual runtime health detected by the platform.
• Lifecycle & reconciliation – Components like the live state manager, health checks, queue handlers, and the reconciliation loop now reason about mismatches between desired and observed state, enabling self‑healing (e.g., automatically restarting a project that is desired‑running but observed‑unhealthy).
• API & UI – The health endpoint and project metrics now report desired and observed counts separately, giving operators a clearer picture of system health. The UI uses desiredStatus to determine if a project is starting/stopping/deleting and observedStatus to decide if a preview is actually reachable.
• Actions & handlers – All project‑modifying actions (create, restart, stop, delete, deploy) now operate on desiredStatus (and observedStatus where appropriate), aligning them with the new two‑dimensional model.

This work addresses PAB‑57 and sets the foundation for robust self‑healing and operational visibility.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
doce-dev-www	Ready	Preview, Comment	Jul 17, 2026 3:25pm

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	❌
Security	✅
Business Logic	❌

Access your configuration settings here.

​