Make the log parser importable (bflog, domain)

CONTRIBUTING.md

@@ -19,7 +19,7 @@ Thanks for helping improve Spawnpoint!
   only — see the rollback note in README "Updating"), plus a probe entry in
   `setup.sh`'s `probe_for` so pre-installer databases skip it correctly.
 - Parser changes should come with a test in
-  `internal/parser/bflog/parser_test.go`; real-world log fixtures are welcome
+  `bflog/parser_test.go`; real-world log fixtures are welcome
   (see `fixtures/README.md`, sanitize nicknames/chat first).
 
 ## Bugs and ideas

README.md

@@ -370,9 +370,9 @@ app is only reachable through it — see
 ```text
 apps/api/              HTTP API + server-rendered UI (theme, charts, pages)
 apps/worker/           log watcher / importer / reingester
-internal/parser/bflog/ Battlefield XML parser + vehicle-kill attribution
+bflog/                 Battlefield XML parser + vehicle-kill attribution (public: importable by other tools)
 internal/storage/      PostgreSQL ingestion, identity linking, analytics
-internal/domain/       normalized event types
+domain/                normalized event types (public)
 migrations/            schema (applied by setup.sh/update.sh, tracked in schema_migrations)
 fixtures/              parser fixtures
 deployments/           production + dev docker-compose stacks, systemd templates, backups

apps/api/export.go

@@ -11,7 +11,7 @@ import (
 	"strings"
 	"time"
 
-	"github.com/hootmeow/spawnpoint/internal/domain"
+	"github.com/hootmeow/spawnpoint/domain"
 )
 
 // playerExport lets a player download their own stats — the self-serve

apps/api/main.go

@@ -23,7 +23,7 @@ import (
 	_ "github.com/lib/pq"
 
 	"github.com/hootmeow/spawnpoint/internal/notify"
-	"github.com/hootmeow/spawnpoint/internal/parser/bflog"
+	"github.com/hootmeow/spawnpoint/bflog"
 	"github.com/hootmeow/spawnpoint/internal/storage/postgres"
 )
 

apps/api/player.go

@@ -14,7 +14,7 @@ import (
 	"strings"
 	"time"
 
-	"github.com/hootmeow/spawnpoint/internal/domain"
+	"github.com/hootmeow/spawnpoint/domain"
 )
 
 type pairCountRow struct {

apps/api/upload.go

@@ -16,7 +16,7 @@ import (
 	"time"
 
 	"github.com/hootmeow/spawnpoint/internal/notify"
-	"github.com/hootmeow/spawnpoint/internal/parser/bflog"
+	"github.com/hootmeow/spawnpoint/bflog"
 	"github.com/hootmeow/spawnpoint/internal/storage/postgres"
 )
 

apps/worker/main.go

@@ -22,7 +22,7 @@ import (
 
 	"github.com/hootmeow/spawnpoint/internal/gamespy"
 	"github.com/hootmeow/spawnpoint/internal/notify"
-	"github.com/hootmeow/spawnpoint/internal/parser/bflog"
+	"github.com/hootmeow/spawnpoint/bflog"
 	"github.com/hootmeow/spawnpoint/internal/storage/postgres"
 )
 

internal/parser/bflog/parser.go → bflog/parser.go

@@ -7,7 +7,7 @@ import (
 	"strconv"
 	"strings"
 
-	"github.com/hootmeow/spawnpoint/internal/domain"
+	"github.com/hootmeow/spawnpoint/domain"
 )
 
 const battlefieldNamespace = "http://www.dice.se/xmlns/bf/1.1"

internal/parser/bflog/parser_test.go → bflog/parser_test.go

@@ -4,7 +4,7 @@ import (
 	"strings"
 	"testing"
 
-	"github.com/hootmeow/spawnpoint/internal/domain"
+	"github.com/hootmeow/spawnpoint/domain"
 )
 
 func TestParseBasicBattlefieldLog(t *testing.T) {

fixtures/README.md

@@ -9,7 +9,7 @@ fixtures/
 ```
 
 Both directories are currently empty placeholders — the parser's unit tests
-(`internal/parser/bflog/parser_test.go`) use inline XML instead. If you have a
+(`bflog/parser_test.go`) use inline XML instead. If you have a
 real round log you're comfortable sharing (nicknames and chat lines are
 visible in it, so sanitize first), a fixture-based compatibility test is a
 welcome contribution:

internal/notify/round.go

@@ -7,7 +7,7 @@ import (
 	"strings"
 	"time"
 
-	"github.com/hootmeow/spawnpoint/internal/domain"
+	"github.com/hootmeow/spawnpoint/domain"
 	"github.com/hootmeow/spawnpoint/internal/storage/postgres"
 )
 

internal/storage/postgres/store.go

@@ -19,7 +19,7 @@ import (
 
 	_ "github.com/lib/pq"
 
-	"github.com/hootmeow/spawnpoint/internal/domain"
+	"github.com/hootmeow/spawnpoint/domain"
 )
 
 const (