[clubanderson]

Adds .github/workflows/hive-action-smoke.yml, a dispatch-only copy of hivecommons/hive's v6 smoke workflow pinned to hivecommons/hive/.github/actions/hive@0531679 (v6 head), with the relay handle defaulting to hivecommons-hive.

Why: the hive v6 readiness live exercise (hivecommons/hive#9700 → hivecommons/hive#7563) needs the workflow_dispatch comment relay to run in a repository that console's hive manages. The relay posts @hivecommons-hive status … on the issue given as input (#24483 for the exercise).

No effect on existing CI; the workflow only runs on manual dispatch.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[github-actions]

🐝 Hi @clubanderson! I'm kubestellar-hive[bot], an automation bot for this repo.

Trusted users — org members and contributors with write access — can mention @kubestellar-hive in a comment to trigger repo automation.
On issues, that mention queues an automated fix attempt. On pull requests, it records extra context for existing automation.
This is not an interactive Q&A bot, so mentions should be treated as requests for automation rather than a conversation.

Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies.

[github-actions]

👋 Hey @clubanderson — thanks for opening this PR!

🤖 This project is developed exclusively using AI coding assistants.

Please do not attempt to code anything for this project manually.
All contributions should be authored using an AI coding tool such as:

• Claude Code (Opus 4.5 / 4.6) — recommended
• GitHub Copilot
• Cursor
• Other AI coding assistants

This ensures consistency in code style, architecture patterns, test coverage,
and commit quality across the entire codebase.

---

This is an automated message.

[netlify]

✅ Deploy Preview for kubestellarconsole canceled.

Name	Link
🔨 Latest commit	a5cb452
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellarconsole/deploys/6ad63b247bb2b70424904b85

[netlify]

✅ Deploy Preview for kubestellarconsole canceled.

Name	Link
🔨 Latest commit	a5cb452
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellarconsole/deploys/6ad63b247bb2b70424904b85

[Copilot]

🟢 Approval recommended

The dispatch-only workflow matches the pinned action’s interface and exercise requirements, with no blocking issues identified.

No open issues 🎉

What changed in this PR

Adds a manually dispatched smoke workflow for the hive v6 readiness exercise without changing existing CI.

Changes:

• Pins the hive action to a specific commit and configures comment or OIDC dispatch.
• Defaults the relay handle to hivecommons-hive and validates OIDC receipt output.

File	Description
.github/​workflows/​hive-action-smoke.yml	Adds manual status relay and OIDC receipt checks.

_{Review effort: Balanced}

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey

[github-actions]

Post-merge build verification passed ✅

Both Go and frontend builds compiled successfully against merge commit 1ec33b327e0f4a5977c96ba70ea7063b7803071b.

[hivecommons-hive]

Trust-surface change — routing to a maintainer for an explicit decision. Code itself reads safe; the decision is about granting a third-party action write tokens in this repo.

What I verified in .github/workflows/hive-action-smoke.yml (the only file, +80/−0):

• Dispatch-only: triggers solely on workflow_dispatch (line 7); it can never run from a PR or push, so untrusted forks cannot invoke it.
• Permissions: the job gets id-token: write, issues: write, pull-requests: write (lines 46–49). That is the minimum the stated comment/OIDC transports need, but it does hand an issue/PR-write token and an OIDC identity for this repo to an external action.
• Pinned: hivecommons/hive/.github/actions/hive@05316797e4… is a full-SHA pin (line 58), not a mutable tag. I could not independently verify the SHA's contents (that repo is outside my review scope).
• No injection path: inputs flow only into with: parameters; the one run: step reads the action output via env (HIVE_RECEIPT, lines 72–75) rather than inline interpolation, so no shell-injection from inputs.
• The header comment says this mirrors hivecommons/hive's own smoke workflow for the hive#9700 v6 readiness exercise, and the diff matches that stated purpose — no unrelated changes.

Question for a maintainer (one sentence): do you accept adding a manually-dispatched workflow that gives the SHA-pinned external hivecommons/hive action issues: write, pull-requests: write, and id-token: write in kubestellar/console for the v6 readiness exercise — and if yes, should it be removed after the exercise concludes?

— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88