fix: add missing Continue support to release workflow and agent scripts

[rohitsoni007]

🧩 Related Issue

Fixes #942

📝 Description
Added: add continue support for Spec kit
This pull request addresses the issue mentioned in #942 by implementing the following changes:

✅ Changes Summary

.github/workflows/scripts/create-release-packages.sh
README.md
scripts/bash/update-agent-context.sh
scripts/powershell/update-agent-context.ps1
src/specify_cli/init.py
.github/workflows/scripts/create-github-release.sh

updated: 19 oct
update for auto adding /command in continue

working example after build release:-

[dkolb]

Quick note: I reviewed the SpecKit README and CLI docs while preparing an internal reference for Spec-Driven Development in another project. The README's specify and slash-command sections match the summary used in our project's docs/speckit.md. Thanks for keeping the CLI examples up to date — they were very helpful.

[rohitsoni007]

also added commit to same pull request further fix and enhance to turn automatically detected in continue chat window when pressing /
update for auto adding /command in continue
now command file top will be looked like

name: speckit.analyze
description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
invokable: true

only for continnue agent
please review and merge pr

[localden]

I feel like this function needs to be more generic, that is - have a separate function for insertion of custom YAML frontmatter into prompt files, and then invoke it with the argument of invokable and a value of true.

[rohitsoni007]

I've refactored the code to extract the YAML frontmatter insertion logic into a separate, more generic function called insert_yaml_frontmatter. This function can now be reused for other field insertions in the future.

The new function takes four parameters:

• body: The content to process
• name: The name to use for the speckit.{name} entry
• field_name: The field name to insert (e.g., "invokable")
• field_value: The value for that field (e.g., "true")

This approach makes the code more maintainable and follows the DRY principle. When the agent is "continue" and a description is present, it still inserts the name: speckit.{name} and invokable: true fields into the YAML frontmatter of the prompt files, but now does so by calling the generic function with the appropriate parameters.

This also makes it easier to add other custom fields in the future without duplicating the AWK logic.

[maxxrdrgz]

@rohitsoni-dev if you would like some assistance, please let me know. I'm an avid Continue user and was going to get to this eventually, but am glad to see someone else has taken the initiative.

[rohitsoni007]

@maxxrdrgz Appreciate your offer to help! I've actually just finished implementing to add support for continue.
I am also the regular user of continue. I am using to run local AI model on my system.
currently all work is already done, pushed and are ready for merge.