fix(cli): publish the Project package with its metadata and configuration

[DecisionNerd]

Summary

gf publish exported the Project package with the DataComponents profile. That profile drops the workspace/research_metadata and workspace/configuration participants, which count as settings components. The Project summary is derived from the Project package (ADR 0051), so every published research repository's summary had no title, licence or ontology mode, and a plain gf clone owner/repo received no metadata or configuration.

• The Project package is now every committed participant except the research component kind. The selection is built from the Complete selection preview, so participants added later are published without another change. Complete itself is refused for a Project with research Branches because its research registry carries operational heads. Research still travels only through the per-Version research interchange packages that gf clone --ref / --version-uuid fetch.
• The summary reports research_present: false, which is exact: ADR 0051 defines it as "this package carries a research component", and a repository's research presence is its manifest lineage field (ADR 0052).
• ADR 0053 records the corrected selection and why a Complete package with a projected registry, or a summary derived from the Version package, were rejected.

Closes #1749

Evidence

Check	Result
published_research_repository_summary_carries_project_metadata: publish a research Project with a title and licence through gf publish to the reference Hub, bind the served summary to the manifest, and assert title, licence, both settings components, research_present: false and the lineage field	fails on main (title is None), passes with the fix
cargo test -p graphforge-cli --lib	113 passed, 1 ignored
cargo test -p graphforge-cli --test hub_fixture (fixture drift)	3 passed; fixture unchanged
make check	exit 0

• CI Gate on PR head

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: CurateLabs/graphforge/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7f3cef31-e458-4628-9f2f-112b1f58d8b4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}