Add clarification about repository references in release notes

Co-authored-by: LadyKerr <47188731+LadyKerr@users.noreply.github.com>

Author: Copilot

RELEASE_CREATION_SUMMARY.md

@@ -52,13 +52,15 @@ Use the workflow dispatch from Actions tab, or create manually through releases
 
 ## Release Specifications
 
-- **Repository**: LadyKerr/github-mcp-server
+- **Repository**: LadyKerr/github-mcp-server (fork where release will be created)
 - **Tag**: v0.19.0
 - **Target**: main branch (commit d216b545e91ca12d6b1bf204e7136aa93254bf82)
 - **Title**: GitHub MCP Server v0.19.0
 - **Status**: Published (not draft)
 - **Body**: Complete release notes with documentation, features, and maintenance updates
 
+**Note**: The release notes reference PRs and links to the upstream repository (`github/github-mcp-server`) as those are where the original changes were made. The release itself is created in this fork.
+
 ## Files Created
 
 1. `.github/workflows/create-release-v0.19.0.yml` - Automated workflow

RELEASE_v0.19.0_README.md

@@ -62,6 +62,9 @@ After this PR is merged to `main`:
 - **Title**: GitHub MCP Server v0.19.0
 - **Target**: main branch (commit `d216b545e91ca12d6b1bf204e7136aa93254bf82`)
 - **Type**: Published release (not draft)
+- **Repository**: LadyKerr/github-mcp-server
+
+**Note**: Release notes reference PRs from the upstream repository (`github/github-mcp-server`) where the original changes were made.
 
 ## Release Notes Summary