Add crestapps-orchardcore to external plugin registry

[MikeAlhayek]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the staged branch for this pull request.

---

Description

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull request overview

Adds the crestapps-orchardcore external plugin to the repository’s external plugin registry so it appears in the generated plugin marketplace used by the project.

Changes:

• Appended a new external plugin entry (crestapps-orchardcore) to plugins/external.json.
• Updated the generated marketplace registry (.github/plugin/marketplace.json) to include the new external plugin entry.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
plugins/external.json	Adds the external registry entry for crestapps-orchardcore with GitHub source + metadata.
.github/plugin/marketplace.json	Reflects the generated marketplace update including crestapps-orchardcore.

[aaronpowell]

It looks like you've incorrectly branched from the main branch not staged, and as a result all the materialised plugins are included in this PR.

You can attempt to fix this with a rebase:

git fetch origin staged
git rebase --onto origin/staged origin/main <branch name>
git push --force-with-lease

If that does not resolve it, you can run npm run plugin:clean which will delete the materialised plugins and you can commit that change.

[MikeAlhayek]

@aaronpowell fixed it in #1153