Simplify release notes workflow

docs/FEATURES/release-communications.md

@@ -112,7 +112,7 @@ The system should not rely only on the user's last login timestamp. Login is one
 - Developer-only release communication back office:
   - `/app/developer/updates`
   - `/app/developer/updates/:id`
-  - `/app/developer/release-commits`
+  - `/app/developer/release-notes`
 
 Feature-owned frontend code belongs under:
 
@@ -235,9 +235,8 @@ GET /api/developer/release-updates/{id}
 PUT /api/developer/release-updates/{id}
 POST /api/developer/release-updates/{id}/publish
 POST /api/developer/release-updates/{id}/archive
-POST /api/developer/release-updates/{id}/send-email
 GET /api/developer/release-commits
-POST /api/developer/release-commits/import
+POST /api/developer/release-commits/refresh
 POST /api/developer/release-commits/{sha}/link
 POST /api/developer/release-commits/{sha}/unlink
 POST /api/developer/release-commits/{sha}/internal-only

docs/TASKS/release-communications/003-developer-commit-reconciliation.md

@@ -24,7 +24,7 @@ Add the developer back-office workflow for importing shipped commits and matchin
   - mark a commit internal-only
   - mark a commit ignored
 - Add developer-only frontend screens:
-  - `/app/developer/release-commits`
+  - `/app/developer/release-notes`
   - linked commits on `/app/developer/updates/:id`
 - Add repository-backed import from configured HTTPS repository settings.
 - Add a selected-commit workflow to copy commit SHA/details and create a draft update entry linked to those commits.