fix: add starterProjects to AI stacks for command palette visibility

[akurinnoy]

Description of Changes

Add starterProjects section to picoclaw, zeroclaw, openclaw, and hermes devfiles. This works around eclipse-che/che#23479 — devfile commands are unavailable in the Che command palette when a workspace has no starterProjects section.

Stack	Starter project	Notes
picoclaw	https://github.com/sipeed/picoclaw.git	Upstream repo (~40 MB)
zeroclaw	https://github.com/zeroclaw-labs/zeroclaw.git	Upstream repo (~160 MB)
openclaw	https://github.com/che-incubator/openclaw-placeholder.git	Placeholder — upstream is ~2.3 GB, times out during clone
hermes	https://github.com/che-incubator/hermes-placeholder.git	Placeholder — upstream is ~617 MB, unreliable clone

Openclaw and hermes use lightweight placeholder repos because their upstream repositories are too large for the DevWorkspace project-clone init container to complete within the default 300s startup timeout.

Related Issue(s)

• Devfile commands are unavailable if a workspace is started from a raw devfile without a project section. eclipse-che/che#23479

Acceptance Criteria

• Contributing guide
• Test automation
• Documentation
• Check Tools Provider

Tests Performed

• Deployed modified registry to CRC cluster (OpenShift, Dev Spaces)
• Created workspaces from all four AI stacks (picoclaw, zeroclaw, openclaw, hermes)
• Confirmed devfile commands appear in the Che command palette and execute correctly
• Verified openclaw and hermes start quickly with placeholder repos

How To Test

1. Build and deploy the registry with these changes
2. Create a workspace from any of the four AI stacks (picoclaw, zeroclaw, openclaw, hermes)
3. Open the Che command palette — devfile commands should be listed and runnable

Notes To Reviewer

• Minimal change — only adds a starterProjects block between attributes and components in each devfile
• Placeholder repos (openclaw-placeholder, hermes-placeholder) should be retired once Devfile commands are unavailable if a workspace is started from a raw devfile without a project section. eclipse-che/che#23479 is resolved

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Added starter project templates for Hermes Agent, OpenClaw, PicoClaw, and ZeroClaw.
  • New workspaces can be initialized directly from each project’s Git repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c007f1de-9395-4ccb-984f-4f9c049c4a51

📥 Commits

Reviewing files that changed from the base of the PR and between e0c090b and 9ad7fbd.

📒 Files selected for processing (4)

• stacks/hermes/1.0.0/devfile.yaml
• stacks/openclaw/1.0.0/devfile.yaml
• stacks/picoclaw/1.0.0/devfile.yaml
• stacks/zeroclaw/1.0.0/devfile.yaml

---

📝 Walkthrough

Walkthrough

Added starterProjects entries to the Hermes, OpenClaw, PicoClaw, and ZeroClaw devfiles. Each entry defines a project name and Git repository URL.

Changes

Starter project configuration

Layer / File(s)	Summary
Git starter project entries stacks/hermes/1.0.0/devfile.yaml, stacks/openclaw/1.0.0/devfile.yaml, stacks/picoclaw/1.0.0/devfile.yaml, stacks/zeroclaw/1.0.0/devfile.yaml	Each devfile now defines a starterProjects entry with its corresponding Git remote.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• devfile/registry#690: Adds the PicoClaw starter project configuration to the same devfile.
• devfile/registry#691: Adds the ZeroClaw starter project configuration to the same devfile.

Suggested labels: lgtm, approved

Suggested reviewers: ibuziuk

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes adding starterProjects to AI stacks and the resulting command palette visibility fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/devfile-commands

---

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.}

[michael-valdron]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akurinnoy, ibuziuk, michael-valdron

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [michael-valdron]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment