docs: fix stale build-tag references (teams -> server) in specs/029 and related docs

All //go:build teams, -tags teams, internal/teams/ references updated to
//go:build server, -tags server, internal/serveredition/ to match the
actual build tags used throughout the codebase.

Related #603

Author: Dumbris

docs/features/settings-page.md

@@ -12,7 +12,7 @@ friendly, prioritized form sections instead of raw JSON:
   isolation, sensitive-data detection, output validation, output sanitisation,
   activity retention, logging, TLS, …).
 - **Raw JSON** — the full Monaco editor, kept as an escape hatch.
-- **Server edition** — server build only.
+- **Server Edition** — server edition only.
 
 ## How saving works
 

docs/plans/2026-03-08-repo-restructure-design.md

@@ -13,8 +13,8 @@ MCPProxy personal and teams editions will be built from the **same repository**
 ## Binary Architecture
 
 - `go build ./cmd/mcpproxy` → **Personal edition** (default)
-- `go build -tags teams ./cmd/mcpproxy` → **Teams edition**
-- Teams-only code lives in `internal/teams/` with `//go:build teams` guards
+- `go build -tags server ./cmd/mcpproxy` → **Teams edition**
+- Teams-only code lives in `internal/serveredition/` with `//go:build server` guards
 - Teams features self-register via `init()` pattern
 - Binary self-identifies edition in version output, startup logs, `/api/v1/status`
 
@@ -24,7 +24,7 @@ MCPProxy personal and teams editions will be built from the **same repository**
 mcpproxy-go/
 ├── cmd/mcpproxy/
 │   ├── main.go                  ← shared entry point
-│   └── teams_register.go       ← //go:build teams
+│   └── teams_register.go       ← //go:build server
 ├── internal/
 │   ├── teams/                   ← teams-only code (all build-tagged)
 │   │   ├── auth/                ← OAuth authorization server

specs/029-mcpproxy-teams/data-model.md

@@ -6,7 +6,7 @@ This restructure introduces no new data entities. It adds build-time metadata on
 
 | Field | Type | Source | Description |
 |-------|------|--------|-------------|
-| `Edition` | `string` | Build tag | `"personal"` (default) or `"teams"` (with `-tags teams`) |
+| `Edition` | `string` | Build tag | `"personal"` (default) or `"teams"` (with `-tags server`) |
 | `Version` | `string` | ldflags | Semantic version from git tag |
 | `Commit` | `string` | ldflags | Short git commit hash |
 | `BuildDate` | `string` | ldflags | ISO 8601 UTC build timestamp |

specs/029-mcpproxy-teams/plan.md

@@ -5,7 +5,7 @@
 
 ## Summary
 
-Restructure the MCPProxy repository to support two editions (Personal and Teams) built from the same codebase using Go build tags. Personal is the default build; Teams requires `-tags teams`. Add Dockerfile for teams, `native/` directory skeleton for future Swift/C# tray apps, extended Makefile, and edition self-identification.
+Restructure the MCPProxy repository to support two editions (Personal and Teams) built from the same codebase using Go build tags. Personal is the default build; Teams requires `-tags server`. Add Dockerfile for teams, `native/` directory skeleton for future Swift/C# tray apps, extended Makefile, and edition self-identification.
 
 ## Technical Context
 
@@ -60,13 +60,13 @@ specs/029-mcpproxy-teams/
 ```text
 cmd/mcpproxy/
 ├── main.go                      # Shared entry point (modify: add edition variable)
-├── teams_register.go            # NEW: //go:build teams — registers teams features
+├── teams_register.go            # NEW: //go:build server — registers teams features
 └── edition.go                   # NEW: default edition = "personal"
-    edition_teams.go             # NEW: //go:build teams — overrides to "teams"
+    edition_teams.go             # NEW: //go:build server — overrides to "teams"
 
 internal/
 ├── teams/                       # NEW: teams-only skeleton
-│   ├── doc.go                   # Package doc, //go:build teams
+│   ├── doc.go                   # Package doc, //go:build server
 │   ├── registry.go              # Feature registry (init pattern)
 │   └── registry_test.go         # Verify registration works
 ├── httpapi/

specs/029-mcpproxy-teams/quickstart.md

@@ -15,7 +15,7 @@ go build -ldflags "..." -o mcpproxy ./cmd/mcpproxy
 ```bash
 make build-teams
 # or directly:
-go build -tags teams -ldflags "..." -o mcpproxy-teams ./cmd/mcpproxy
+go build -tags server -ldflags "..." -o mcpproxy-teams ./cmd/mcpproxy
 ./mcpproxy-teams version
 # MCPProxy v0.21.0 (teams) linux/amd64
 ```
@@ -45,7 +45,7 @@ curl http://localhost:8080/api/v1/status | jq .edition
 ```bash
 # Run tests (both editions)
 go test ./internal/... -v                    # personal (default)
-go test -tags teams ./internal/... -v        # teams (includes teams tests)
+go test -tags server ./internal/... -v        # teams (includes teams tests)
 
 # Lint
 ./scripts/run-linter.sh

specs/029-mcpproxy-teams/research.md

@@ -2,7 +2,7 @@
 
 ## Go Build Tags Pattern
 
-**Decision**: Use `//go:build teams` file-level tags to isolate teams-only code.
+**Decision**: Use `//go:build server` file-level tags to isolate teams-only code.
 
 **Rationale**: Go build tags are the idiomatic way to compile different feature sets from the same codebase. The `init()` registration pattern allows teams packages to self-register without modifying shared code paths.
 

specs/029-mcpproxy-teams/spec.md

@@ -224,11 +224,11 @@ The proxy provides a web interface where users log in via their identity provide
 **Backward Compatibility**
 
 - **FR-037**: When operating in personal mode (default), the system MUST behave identically to the current single-user version with no team features active.
-- **FR-038**: The system MUST be built as a separate binary from the personal edition using Go build tags (`-tags teams`), from the same repository and `cmd/mcpproxy` entry point.
+- **FR-038**: The system MUST be built as a separate binary from the personal edition using Go build tags (`-tags server`), from the same repository and `cmd/mcpproxy` entry point.
 
 **Build & Distribution**
 
-- **FR-039**: The personal edition MUST be the default build output (`go build ./cmd/mcpproxy`). The teams edition MUST require an explicit build tag (`go build -tags teams ./cmd/mcpproxy`).
+- **FR-039**: The personal edition MUST be the default build output (`go build ./cmd/mcpproxy`). The teams edition MUST require an explicit build tag (`go build -tags server ./cmd/mcpproxy`).
 - **FR-040**: The teams edition MUST be distributed as a Docker image (`ghcr.io/smart-mcp-proxy/mcpproxy-teams`), a `.deb` package for Ubuntu/Debian, and a Linux binary tarball.
 - **FR-041**: The personal edition MUST be distributed as macOS DMG installer (with native Swift tray app), Windows MSI/EXE installer (with native C# tray app), Linux binary tarball, and via Homebrew.
 - **FR-042**: Both editions MUST be released under a single GitHub release tag (e.g., `v0.21.0`) with assets clearly named by edition (`mcpproxy-*` for personal, `mcpproxy-teams-*` for teams).
@@ -272,7 +272,7 @@ The proxy provides a web interface where users log in via their identity provide
 - Agent token maximum per user follows the same limit as the personal edition (10 tokens per user).
 - Admin designation is static per configuration (email list or IdP claim) — there is no in-app role assignment UI in v1.
 - Server template definitions are static (shipped with the binary + admin-defined in config) — there is no template marketplace or community sharing.
-- Both editions are built from the same repository (`mcpproxy-go`) using Go build tags. Teams-only code lives in `internal/serveredition/` with `//go:build teams` guards. No `pkg/` migration is needed.
+- Both editions are built from the same repository (`mcpproxy-go`) using Go build tags. Teams-only code lives in `internal/serveredition/` with `//go:build server` guards. No `pkg/` migration is needed.
 - Data retention for activity logs follows the same policy as the personal edition — configurable, with no default auto-purge.
 
 ## Scope Boundaries
@@ -291,7 +291,7 @@ The proxy provides a web interface where users log in via their identity provide
 - Activity log with user identity and filtering
 - Web UI: login, dashboard, admin panel
 - Backward-compatible personal mode
-- Same-repo build tag architecture (`-tags teams`)
+- Same-repo build tag architecture (`-tags server`)
 - Single GitHub release with labeled assets per edition
 - Docker image and deb package for teams distribution
 - Native tray apps: Swift (macOS), C# (Windows) for personal distribution