docs(ai): map invocation lifecycle scenarios to PR changes

[Wei Meng (m5i-work)]

Summary

Moves the approval-sensitive scenario impact mapping out of #9900 and #9901 so those feature PRs do not need approval for .github/ changes.

This PR changes only .github/skills/foundry-extension-scenario-pr-regression/references/impact-mapping.md:

• maps invocations*.go to cmd:invocations
• maps invoke_response*.go and invoke_invocation*.go to both cmd:invoke and cmd:invocations
• normalizes the file's CRLF line endings to LF so the new rows pass git diff --check

Ignoring line endings, the change is only three mapping rows. No production code, live tests, provisioning, or CI jobs are added.

Stack / approval boundary

• feat(ai): add unified invocation lifecycle commands #9900: shared commands and Responses support; no .github/ diff
• feat(ai): add Invocations protocol lifecycle support #9901: Invocations protocol support; no .github/ diff
• This follow-up: mapping-only change requiring the separate .github/ owners

This PR is stacked after #9901 and can be reviewed in parallel. It does not block merging #9900 or #9901. Retarget to main when the feature stack has merged.

Validation

• git diff --check
• cspell 8.13.1 using the repository's miscellaneous-file configuration
• checked mappings against the existing cmd:invocations tag and offline scenario files

Related to #9676.

[azure-pipelines]

Azure Pipelines:
22 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[github-actions]

🔗 Linked Issue Required

Thanks for the contribution! Please link a GitHub issue to this PR by adding Fixes #123 to the description or using the sidebar.
No issue yet? Feel free to create one!