feat: add status to insight project

[gaspergrom]

Note

Medium Risk
Adds a new non-null status field to the materialized project_insights_copy_ds schema and wires it through query/copy pipes, which can impact consumers expecting the old schema. Also shifts the copy schedule time and makes minor query formatting fixes with low behavioral risk.

Overview
Project insights now includes project status. The PR adds a status column to project_insights_copy_ds and propagates it through project_insights_copy.pipe and the project_insights.pipe endpoint so callers can read the current project state (e.g. active/archived).

It also fixes a malformed TAGS line in project_insights.pipe, adjusts health_score_retention.pipe WHERE-clause formatting (no intended logic change), and moves the project_insights_copy daily COPY_SCHEDULE from 0 2 * * * to 0 3 * * *.

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

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

Pull request overview

Adds the project status field to the Project Insights dataset served via Tinybird, so consumers can differentiate e.g. active vs archived projects when fetching insights.

Changes:

• Add status to the materialized project_insights_copy_ds dataset (copy pipe + datasource schema/docs).
• Expose status in the project_insights.pipe endpoint response.
• Shift the project_insights_copy copy schedule from 0 2 * * * to 0 3 * * *.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
services/libs/tinybird/pipes/project_insights_copy.pipe	Includes status in base + final selects and adjusts the COPY_SCHEDULE.
services/libs/tinybird/pipes/project_insights.pipe	Returns status from project_insights_copy_ds in the endpoint query.
services/libs/tinybird/datasources/project_insights_copy_ds.datasource	Adds status to schema and documents the new column.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.