Fix/stop command telegram forum topic

[r266-tech]

Summary

Describe the problem and fix in 2–5 bullets:

• Problem:
• Why it matters:
• What changed:
• What did NOT change (scope boundary):

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related #

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
If none, write None.

Security Impact (required)

• New permissions/capabilities? (Yes/No)
• Secrets/tokens handling changed? (Yes/No)
• New/changed network calls? (Yes/No)
• Command/tool execution surface changed? (Yes/No)
• Data access scope changed? (Yes/No)
• If any Yes, explain risk + mitigation:

Repro + Verification

Environment

• OS:
• Runtime/container:
• Model/provider:
• Integration/channel (if any):
• Relevant config (redacted):

Steps

Expected

Actual

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios:
• Edge cases checked:
• What you did not verify:

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? (Yes/No)
• Config/env changes? (Yes/No)
• Migration needed? (Yes/No)
• If yes, exact upgrade steps:

Failure Recovery (if this breaks)

• How to disable/revert this change quickly:
• Files/config to restore:
• Known bad symptoms reviewers should watch for:

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

• Risk:
  • Mitigation:

---

Note

Medium Risk
Touches critical CI and release automation (including Docker publishing and new gating/sharding), which could break builds or alter release behavior if misconfigured; no product runtime logic changes are included.

Overview
CI/CD overhaul: switches composite setup-node-env default to Node 24 (with cache key suffix), updates many workflows/actions to newer major versions, disables sticky-disk caching on PRs, and simplifies job gating to run heavy jobs only when relevant scopes change.

New automation: adds changed-extensions detection plus per-extension fast tests, splits Linux tests into shards, adds a CLI startup memory smoke job, and adds a Node 22 compatibility lane on pushes. Docker releases gain a manual tag backfill path gated by an environment and move builds to GitHub-hosted runners with official Docker actions.

Repo governance & hygiene: introduces CODEOWNERS (including secops/release-manager review requirements), expands issue template fields (model/provider routing), adds spam auto-close+lock handling, ignores .env in Docker build contexts, and updates secret scanning allowlists for Sparkle appcast signatures. Also adds a Parallels Discord roundtrip skill doc and assorted ignore/tooling config files (.jscpd.json, .npmignore, .prettierignore, .gitignore tweaks).

^{Written by Cursor Bugbot for commit d33c166. This will update automatically on new commits. Configure here.}