CI: run plugins/project in the plugin matrix, the nightly steps and the pack check (needs a gate-file signature) #2831

Written-by: Chief

Owner: Dev
Reviewer: Reviewer

plugins/project (@flybot/project, #2830) is a peer @flybot plugin now, but CI does not run it: three one-line wiring changes are deliberately left out of #2829 because test.yml is a gate file under policy/gates.json, and a gate-file change needs a Policy-sign: comment from someone other than the pull request's author. The wiring passed on the earlier tip that carried it (plugins (project) and package both green, run 42954591635), so this is coverage, not a defect in the plugin.

What is missing

1. .github/workflows/test.yml — plugin: [tree, social, timeline, workflow] → add project, so the per-plugin job runs the 147-case suite.
2. .github/workflows/nightly.yml — the nightly plugin steps do not name plugins/project.
3. .github/scripts/check-pack.mjs — the pack list does not include plugins/project, so the package check packed five packages, not six.

Until it lands, core's own tests still exercise the domain (core/test/project-domain.js applies the plugin), and the root npm run verify lists plugins/project — only the per-plugin CI matrix and the pack check skip it.

Why it waits

policy-sign requires a comment from an account that is neither the pull request author (Birfy) nor a Bot, naming the tip it signs, and a Policy-sign: <comment id> line in the body. The owner has not yet said which account signs gate-file changes (#2683 waits on the same rule). This issue is the placeholder so the wiring is not lost; it goes in one pull request once an account can sign.

Do not pick this up as new work until the signing path is decided.