Fix missing YAMCS personal credential prompt

[Paul Lizer (paullizer)]

Summary

• Fix YAMCS chat failing with a generic validation error before requesting each user's personal proxy identity.
• Translate stored credential references to the catalog's canonical action reference in the initialized runtime adapter. Preserve existing bindings, fingerprints, and authorization checks.
• Bump the application version from 0.261.340 to 0.261.341.

Linked issue

No associated GitHub issue.

Release Notes & Latest Features

• Bug Fix
• User-facing: yes. No new feature card or screenshot is needed.
• Release notes have not been changed; awaiting approval.

Version bump

• Application VERSION patch segment bumped to 0.261.341.
• Deployer version not needed: deployers/ is unchanged.

Testing / validation

• Regression reproduced the catalog ValueError before the fix and passed afterward.
• 9 real bootstrap/import checks passed, including normal/optimized Python and web/scheduler initialization.
• 38 personal-credential and Semantic Kernel continuation tests passed after installing declared local dependencies.
• Coverage exercises real runtime/catalog credential requests, colon-bearing action IDs, and rejection of foreign personal actions and unauthorized group references.
• Changed Python files pass py_compile; staged diff passes whitespace checks.
• The hosted app is unchanged. Retest the credential card and Save and continue flow after deployment.

Documentation

• Feature documentation updated.
• Fix documentation added under docs/explanation/fixes/.
• Release notes update pending approval.

Security checklist

• No secrets, credentials, local proxy deployment files, or local-only artifacts are included.
• Catalog ownership, group membership, governance, and enabled-action checks remain in force.
• No Flask routes, frontend settings payloads, or browser runtime assets changed.

Targets paullizer-react-v2-ui as requested; no application deployment is included.