chore: add PROJECT_TOKEN secret and P0 label after PR #391 merges

[castrojo]

After #391 merges, two manual steps are required for hive to be fully operational:

1. Add PROJECT_TOKEN secret

hive-status-sync.yml posts to the todo.projectbluefin.io project board. It needs the same PROJECT_TOKEN already configured in projectbluefin/dakota.

Settings → Secrets and variables → Actions → New repository secret:

• Name: PROJECT_TOKEN
• Value: same token as in projectbluefin/dakota

2. Add P0 label

All lifecycle labels are auto-created by bonedigger on first issue open, except P0 which hive-status-sync queries to surface critical issue counts in the project dashboard.

gh label create P0 --color b60205 --description "Critical — blocks the build or a release" --repo projectbluefin/common

Verify

After adding the secret, trigger the workflow manually:
Settings → Actions → Hive Status Sync → Run workflow

Should post a status update to the todo.projectbluefin.io project.