fix: correct Swagger basePath to prevent double /api/v1 prefix

The basePath was /api/v1 while route annotations already included the
full /api/v1/* paths, causing Swagger UI to send requests to
/api/v1/api/v1/stats which fell through to the HTML catch-all handler.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: xdefrag

cmd/lore/main.go

@@ -1,7 +1,7 @@
 // @title			Lore API
 // @version		1.0
 // @description	REST API for the Lore Stellar blockchain token explorer. Provides access to MTLAP (Persons), MTLAC (Companies), and MTLAX (Synthetic) accounts, relationships, reputation scores, and statistics.
-// @BasePath		/api/v1
+// @BasePath		/
 
 package main
 

internal/api/docs/docs.go

@@ -667,7 +667,7 @@ const docTemplate = `{
 var SwaggerInfo = &swag.Spec{
 	Version:          "1.0",
 	Host:             "",
-	BasePath:         "/api/v1",
+	BasePath:         "/",
 	Schemes:          []string{},
 	Title:            "Lore API",
 	Description:      "REST API for the Lore Stellar blockchain token explorer. Provides access to MTLAP (Persons), MTLAC (Companies), and MTLAX (Synthetic) accounts, relationships, reputation scores, and statistics.",

internal/api/docs/swagger.json

@@ -6,7 +6,7 @@
         "contact": {},
         "version": "1.0"
     },
-    "basePath": "/api/v1",
+    "basePath": "/",
     "paths": {
         "/api/v1/accounts": {
             "get": {

internal/api/docs/swagger.yaml

@@ -1,4 +1,4 @@
-basePath: /api/v1
+basePath: /
 definitions:
   api.AccountDetailResponse:
     properties: