fix: use CI_TOKEN for issue creation in security-scan workflow

.gitea/workflows/security-scan.yml

@@ -178,16 +178,16 @@ jobs:
           ISSUE_BODY="${ISSUE_BODY}4. Verify with: \`make security-check\`\n"
 
           # Create issue using Gitea API
-          # Note: Requires GITEA_TOKEN secret to be configured
-          if [ -n "${{ secrets.GITEA_TOKEN }}" ]; then
+          # Note: Requires CI_TOKEN secret to be configured
+          if [ -n "${{ secrets.CI_TOKEN }}" ]; then
             curl -X POST \
-              -H "Authorization: token ${{ secrets.GITEA_TOKEN }}" \
+              -H "Authorization: token ${{ secrets.CI_TOKEN }}" \
               -H "Content-Type: application/json" \
               -d "{\"title\":\"${ISSUE_TITLE}\",\"body\":\"${ISSUE_BODY}\",\"labels\":[\"security\",\"dependencies\",\"automated\"]}" \
               "${{ github.server_url }}/api/v1/repos/${{ github.repository }}/issues"
           else
-            echo "⚠️ GITEA_TOKEN not configured - skipping issue creation"
-            echo "Please add GITEA_TOKEN as repository secret for automated issue creation"
+            echo "⚠️ CI_TOKEN not configured - skipping issue creation"
+            echo "Please add CI_TOKEN as repository secret for automated issue creation"
           fi
 
       - name: Notify on failure