Use shellshock publish release command

[jerrod-storm]

This pull request updates the release workflow and metadata for the project, focusing on improving release management and providing better context for versioning. The most important changes are grouped below:

Release Workflow Improvements:

• The GitHub release creation step in .github/workflows/_create_release.yaml now uses the custom ./shell/shock publish-release script instead of the standard gh release create command, streamlining and potentially customizing the release process.

Metadata and Versioning Enhancements:

• The manifest.json file now includes a new naming object that describes the meaning of each version segment (major, minor, patch), providing clearer context for release versions.

Submodule Update:

• The shell/.shock submodule was updated to a newer commit, which may bring in bug fixes or new features for release publishing.

[Copilot]

Pull request overview

Updates the release workflow to use the project’s shell/shock release publisher and expands manifest metadata to better describe version semantics.

Changes:

• Switched GitHub Release creation to ./shell/shock publish-release in the release workflow.
• Added a naming section to manifest.json to explain version segment meaning.
• Bumped the shell/.shock submodule to a newer commit.

Reviewed changes

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

File	Description
shell/.shock	Updates the shock submodule commit used by release tooling.
manifest.json	Adds version-segment naming metadata alongside latest/stable.
.github/workflows/_create_release.yaml	Uses shock publish-release instead of gh release create.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.