fix: align deploy workflow with manifest metadata extraction

[gentlementlegen]

This updates the deploy workflow to use the issue-27 manifest metadata flow and explicit event exclusions where required.

Resolves ubiquity-os/action-deploy-plugin#27

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates the plugin template configuration across three files: the GitHub Actions workflow now excludes specific events from plugin execution; manifest.json is updated with plugin-specific metadata including name, description, event listeners configuration, and a skipBotEvents flag; and package.json dependency versions are bumped with reorganization between regular and development dependencies.

Possibly related issues

• Generate manifest metadata from code/package.json (commands, listeners, skipBotEvents, name, description) action-deploy-plugin#27: This PR manually updates the exact manifest fields (name, description, ubiquity:listeners, skipBotEvents) that the issue proposes should be auto-generated from code and package.json, establishing the manifest structure but not the generation automation mechanism.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	Changes partially address issue #27: manifest.name/description updated from package.json, skipBotEvents added to manifest, ubiquity:listeners array added. However, commands generation and strict validation mentioned in criteria are not evidenced.	Verify that manifest.commands generation from code is implemented, ubiquity:listeners is populated from typed sources, and CI validation prevents manual edits.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title accurately describes the main change: aligning the deploy workflow with manifest metadata extraction as outlined in issue #27.
Description check	✅ Passed	Description references the correct issue using the required keyword 'Resolves' and explains the workflow update, but links to external action repo instead of internal issue.
Out of Scope Changes check	✅ Passed	Changes align with issue #27 scope: workflow event exclusions, manifest metadata updates, dependency bumps, and package.json description sync are all directly related to manifest generation objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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 and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2d4f93811f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Stop excluding every supported event from metadata

This excludes both events the plugin declares and handles (src/types/context.ts:10, src/index.ts:11-15), which is why this commit’s generated manifest now has "ubiquity:listeners": []. In environments where dispatch is driven by manifest listeners, that leaves the plugin with no subscribed events and prevents /hello handlers from being invoked.

Useful? React with 👍 / 👎.

[ubiquity-os-beta]

 [ 2.555 UUSD ] 

@gentlementlegen

Contributions Overview

View	Contribution	Count	Reward
Review	Specification	1	2.555

Conversation Incentives

Comment	Formatting	Relevance	Priority	Reward
This updates the deploy workflow to use the issue-27 manifest me…	2.04 content: content: p: score: 0 elementCount: 2 a: score: 1 elementCount: 1 result: 1 regex: wordCount: 20 wordValue: 0.1 result: 1.04 authorship: 1	Relevance: 0.5 Readability: 44.4	1	2.555