feat: import release commits from repository api

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

@@ -26,6 +26,8 @@ Add the developer back-office workflow for importing shipped commits and matchin
 - Add developer-only frontend screens:
   - `/app/developer/release-commits`
   - 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.
 - Support filters for:
   - communication status
   - linked update
@@ -54,6 +56,7 @@ Add the developer back-office workflow for importing shipped commits and matchin
 - A release update can have many linked commits.
 - Imported commits default to `Unreviewed`.
 - Import must use either a submitted commit payload or configured repository connection settings. Do not discover or read a local `.git` directory from the deployed app filesystem.
+- Repository import currently targets a Gitea-compatible REST API derived from the configured repository URL.
 - Repository URL and access credentials must come from configuration/secrets.
 - Do not generate user-facing update entries automatically from commits.
 
@@ -69,7 +72,10 @@ npm run build
 ## Done When
 
 - [x] Developers can import commits idempotently.
+- [x] Developers can fetch commits from the configured repository API.
 - [x] Developers can list and filter imported commits.
+- [x] Developers can select commits and copy SHA/details for external summarization.
+- [x] Developers can create a draft update entry from selected commits.
 - [x] Developers can link commits to release updates.
 - [x] Developers can unlink commits.
 - [x] Developers can mark commits internal-only.