refactor: rename project from Flights to Missions and update related components

This commit transitions the project from Azaion.Flights to Azaion.Missions, updating namespaces, DTOs, services, and database entities accordingly. The Docker configuration and entry points have been modified to reflect the new project structure. Additionally, the README and documentation have been updated to clarify the ongoing renaming process and its implications. All references to flights have been replaced with missions, ensuring consistency across the codebase.
2026-06-21 08:11:06 +00:00 · 2026-05-15 04:35:49 +03:00
parent 4f226e91d5
commit 2840ccb9b6
51 changed files with 381 additions and 352 deletions
@@ -6,7 +6,7 @@

 **Implementation status**: ✅ implemented (with one stricter-than-spec rule -- see Caveats #1).

-> **NOTE (forward-looking)**: file paths and identifiers below reflect the post-rename state. Today's source still uses `Aircraft*` filenames + `[Route("aircrafts")]`. The renames are tracked under Jira AZ-EPIC children B6 (domain rename) and B8 (HTTP routes). The doc IS the spec for that work.
+> **NOTE (forward-looking)**: file paths and identifiers below reflect the post-rename state. B5 (namespace) and B6 (domain) have landed; route attributes still match `[Route("aircrafts")]` until B8 ships.

 **Files** (post-rename):
 - HTTP: `Controllers/VehiclesController.cs`
@@ -94,7 +94,7 @@ None.
 3. **No validation on request DTOs** (no `[Required]`, no range checks): empty `Name`, negative `BatteryCapacity`, invalid enum int values, etc., are accepted.
 4. **Entity returned on the wire** with no DTO mapping -- couples DB column shape to HTTP response shape. Today benign because `Vehicle` has no associations.
 5. **Case-insensitive search via `LOWER(...)`** -- full-table scan; fine while the catalog is small.
-6. **`FuelType` may not fit `GuidedMissile`** -- the existing `{ Electric, Gasoline, Diesel }` set assumes a powered, reusable vehicle. Carry forward as Phase C decision (see plan); may spawn a follow-up ticket to allow a `None` value or make `FuelType` nullable for missiles.
+6. **`FuelType` for `GuidedMissile`** -- decided in B6 (2026-05-15): extend the enum with `SolidPropellant = 3` and keep `FuelType` non-nullable on `Vehicle`. `GuidedMissile` rows persist with `FuelType = SolidPropellant`. Numeric values 0/1/2 are unchanged so existing rows are untouched. Reasoning: nullable would silently propagate to the UI (it assumes a fuel type); a value-typed default keeps every consumer working without a code change.

 ## 8. Dependency Graph

@@ -4,7 +4,7 @@

 **Implementation status**: ✅ implemented. Single policy `FL` is declared and consumed by every controller in the post-rename target scope.

-> **NOTE (forward-looking)**: post-rename + post-GPS-Denied-removal. Today's `JwtExtensions.cs` also declares a `"GPS"` policy reserved for the (now-removed-from-this-repo) GPS-Denied endpoints. After Jira AZ-EPIC child B7 lands, only `"FL"` remains.
+> **NOTE**: B7 has landed (2026-05-15). The `"GPS"` policy and the GPS-Denied entities (`Orthophoto`, `GpsCorrection`) have been removed from this service. Only `"FL"` remains.

 **Files**: `Auth/JwtExtensions.cs`, `Infrastructure/ConfigurationResolver.cs` (consumed for fail-fast value resolution)

@@ -34,12 +34,11 @@ public static IServiceCollection AddJwtAuth(this IServiceCollection services, IC

 Each value is resolved env-var-first, then config-key, then throws `InvalidOperationException` at startup. There is **no dev fallback**. The legacy `JWT_SECRET` env var is no longer consulted.

-Side effects: registers `JwtBearerDefaults.AuthenticationScheme` and **two** named authorization policies in DI (one is removed after B7 lands):
+Side effects: registers `JwtBearerDefaults.AuthenticationScheme` and **one** named authorization policy in DI:

 | Policy | Requirement | Notes |
 |--------|-------------|-------|
-| `"FL"` | JWT contains a `permissions` claim with value `"FL"` | Permanent |
-| `"GPS"` | JWT contains a `permissions` claim with value `"GPS"` | Removed in Jira B7 (legacy GPS-Denied routes are moving out of this repo) |
+| `"FL"` | JWT contains a `permissions` claim with value `"FL"` | Only policy declared by this service. The legacy `"GPS"` policy was removed when B7 landed (2026-05-15). |

 ## 3. JWT model (this service) vs. suite-wide pattern

@@ -7,11 +7,11 @@ name: Decompose Tests
 status: not_started
 sub_step:
  phase: 0
-  name: blocked-on-tracker-auth
-  detail: "atlassian MCP not connected; tracker decision A/B/C/D pending"
+  name: awaiting-invocation
+  detail: ""
 retry_count: 0
 cycle: 1
 tracker: jira

-## Rename tracking (Jira AZ-EPIC + child stories B1–B12)
-See `_docs/_process_leftovers/2026-05-14_rename-flights-to-missions.md` for the leftover entry; it is intentionally retained until B4–B12 ship.
+## Rename tracking (Jira AZ-EPIC + child stories B1-B12)
+See `_docs/_process_leftovers/2026-05-14_rename-flights-to-missions.md`. Local code work for B5, B6, B7, B8, B9, B12 landed 2026-05-15; .woodpecker tag rename done. Cross-repo work pending: B4 (suite), B10-suite, B11 (autopilot + ui), B12 spec catch-up in suite. Leftover stays until those land.
@@ -33,7 +33,16 @@ The rest of the work — code rename, DB migration, HTTP route rename, repo rena

 ## Jira ticket creation status

-**status: tickets-created + local-task-files-written** (2026-05-14)
+**status: in-flight** (last updated 2026-05-15)
+
+- Tickets created 2026-05-14.
+- Local code work in `flights/` workspace landed 2026-05-15: B5, B6, B7, B8, B9, B12 transitioned to Done; their task files moved to `_docs/tasks/done/` with `Status: Done (2026-05-15)` headers. Local `.woodpecker/build-arm.yml` image-tag rename done as part of the same session (the local portion of B10).
+- Cross-repo / suite work still pending: B4 (Gitea repo rename + suite `.gitmodules` + `git mv flights missions`), B10 suite-side (`_infra/` compose service block), B11 (autopilot + ui consumer cutover, suite e2e harness).
+- Cross-repo follow-up surfaced by B12: `azaion-suite/_docs/02_missions.md` Vehicles section needs the rule wording: "exactly one vehicle has is_default = true at any time; toggle on a non-default unsets the previous default in the same transaction." Add as part of the suite-side work.
+
+(Original creation snapshot retained below for traceability.)
+
+**Original status (2026-05-14)**: tickets-created + local-task-files-written

 Local task files were created under the project convention `<repo>/_docs/tasks/{todo,done}/AZ-<n>_<slug>.md` so the existing habit of mirroring tracker tickets as reviewable markdown is preserved. Per-repo work lives in the repo it touches; suite-level / multi-repo work stays in `azaion-suite/_docs/tasks/`.

@@ -58,21 +67,21 @@ In the suite repo (`azaion-suite/_docs/tasks/`):

 | Plan ID | Jira | Type | SP | Status |
 |---------|------|------|----|--------|
-| Epic    | [AZ-539](https://denyspopov.atlassian.net/browse/AZ-539) | Epic  | -- | To Do |
-| B1      | [AZ-540](https://denyspopov.atlassian.net/browse/AZ-540) | Task  | 3  | **Done** (this turn) |
-| B2      | [AZ-541](https://denyspopov.atlassian.net/browse/AZ-541) | Task  | 3  | **Done** (this turn) |
-| B3      | [AZ-542](https://denyspopov.atlassian.net/browse/AZ-542) | Task  | 3  | **Done** (this turn) |
-| B4      | [AZ-543](https://denyspopov.atlassian.net/browse/AZ-543) | Task  | 3  | To Do |
-| B5      | [AZ-544](https://denyspopov.atlassian.net/browse/AZ-544) | Story | 3  | To Do |
-| B6      | [AZ-545](https://denyspopov.atlassian.net/browse/AZ-545) | Story | 5  | To Do |
-| B7      | [AZ-546](https://denyspopov.atlassian.net/browse/AZ-546) | Story | 3  | To Do |
-| B8      | [AZ-547](https://denyspopov.atlassian.net/browse/AZ-547) | Story | 3  | To Do |
-| B9      | [AZ-548](https://denyspopov.atlassian.net/browse/AZ-548) | Story | 5  | To Do |
-| B10     | [AZ-549](https://denyspopov.atlassian.net/browse/AZ-549) | Task  | 2  | To Do |
-| B11     | [AZ-550](https://denyspopov.atlassian.net/browse/AZ-550) | Story | 5  | To Do |
-| B12     | [AZ-551](https://denyspopov.atlassian.net/browse/AZ-551) | Task  | 2  | To Do |
+| Epic    | [AZ-539](https://denyspopov.atlassian.net/browse/AZ-539) | Epic  | -- | To Do (close after B4/B10-suite/B11) |
+| B1      | [AZ-540](https://denyspopov.atlassian.net/browse/AZ-540) | Task  | 3  | **Done** (2026-05-14) |
+| B2      | [AZ-541](https://denyspopov.atlassian.net/browse/AZ-541) | Task  | 3  | **Done** (2026-05-14) |
+| B3      | [AZ-542](https://denyspopov.atlassian.net/browse/AZ-542) | Task  | 3  | **Done** (2026-05-14) |
+| B4      | [AZ-543](https://denyspopov.atlassian.net/browse/AZ-543) | Task  | 3  | To Do (suite repo) |
+| B5      | [AZ-544](https://denyspopov.atlassian.net/browse/AZ-544) | Story | 3  | **Done** (2026-05-15) |
+| B6      | [AZ-545](https://denyspopov.atlassian.net/browse/AZ-545) | Story | 5  | **Done** (2026-05-15) |
+| B7      | [AZ-546](https://denyspopov.atlassian.net/browse/AZ-546) | Story | 3  | **Done** (2026-05-15) |
+| B8      | [AZ-547](https://denyspopov.atlassian.net/browse/AZ-547) | Story | 3  | **Done** (2026-05-15) |
+| B9      | [AZ-548](https://denyspopov.atlassian.net/browse/AZ-548) | Story | 5  | **Done** (2026-05-15) |
+| B10     | [AZ-549](https://denyspopov.atlassian.net/browse/AZ-549) | Task  | 2  | Partial (local `.woodpecker/build-arm.yml` updated 2026-05-15; suite compose still To Do) |
+| B11     | [AZ-550](https://denyspopov.atlassian.net/browse/AZ-550) | Story | 5  | To Do (suite + autopilot + ui repos) |
+| B12     | [AZ-551](https://denyspopov.atlassian.net/browse/AZ-551) | Task  | 2  | **Done** (2026-05-15) -- code + DB index landed; suite spec wording catch-up still pending |

-Total: 1 Epic + 12 child tickets, 35 SP across remaining 9 tickets.
+Total: 1 Epic + 12 child tickets. 9 of 12 children Done. Remaining work: B4, B11, suite-side B10, plus B12's spec catch-up in `azaion-suite/_docs/02_missions.md`.

 ## Replay obligation

@@ -1,50 +0,0 @@
-# Leftover: Step 5 (Decompose Tests) blocked on tracker auth
-
-**Recorded**: 2026-05-14T20:51:00Z (Thursday)
-**Blocker**: `user-atlassian-mcp` returns "Not connected" (verified via `getAccessibleAtlassianResources`).
-**Type**: tracker availability — NOT a deferrable "non-user blocker"; the autodev tracker rule (`.cursor/rules/tracker.mdc` Tracker Availability Gate) requires explicit user decision (Retry / `tracker: local`).
-
-## What is pending
-
-Step 5 (Decompose Tests, tests-only mode) needs to run:
-1. **Step 1t** — Test Infrastructure Bootstrap → creates `todo/[TRACKER-ID]_test_infrastructure.md` + matching Jira ticket
-2. **Step 3** — Blackbox Test Task Decomposition → produces one task file per blackbox/perf/res/sec/res-lim scenario referenced in `_docs/02_document/tests/*.md`. Estimated 12–20 task files based on the current spec spread (FT-P-01…FT-P-18, FT-N-01…FT-N-08, NFT-PERF-01…NFT-PERF-04, NFT-RES-01…NFT-RES-08, NFT-SEC-01…NFT-SEC-13, NFT-RES-LIM-01…NFT-RES-LIM-04).
-3. **Step 4** — Cross-Verification → produces `_docs/02_tasks/_dependencies_table.md` and verifies AC/restriction coverage.
-
-Each task file must have a Jira ticket created inline (per `.cursor/skills/decompose/SKILL.md` Save Timing table) and then be renamed from numeric prefix to `AZ-<id>` prefix.
-
-## Inputs ready
-
- `_docs/02_document/tests/environment.md` ✓
- `_docs/02_document/tests/test-data.md` ✓
- `_docs/02_document/tests/blackbox-tests.md` ✓
- `_docs/02_document/tests/performance-tests.md` ✓
- `_docs/02_document/tests/resilience-tests.md` ✓
- `_docs/02_document/tests/security-tests.md` ✓
- `_docs/02_document/tests/resource-limit-tests.md` (need to verify exists)
- `_docs/02_document/tests/traceability-matrix.md` ✓ (post-2026-05-14 drift Phase 2 re-issue, 97% in-scope coverage)
- `_docs/00_problem/{problem,restrictions,acceptance_criteria}.md` ✓ (post-drift-revision)
-
-## Resolution paths
-
-The next `/autodev` invocation MUST resolve one of:
-
- **(preferred) Retry auth**: User authenticates `user-atlassian-mcp` via Cursor's MCP UI; autodev then proceeds normally and creates AZ-prefixed task files with live Jira tickets.
- **`tracker: local` mode** (only with explicit user acceptance): tasks are written with numeric prefix + `Tracker: pending` header marker; state file's `tracker:` field is changed to `local`; a future invocation with a working Jira MCP runs a "Tracker Pending Sync" to back-fill tickets and rename the files.
-
-## Step 4 deliverables (already applied — DO NOT redo)
-
- `Auth/JwtExtensions.cs` — JWKS refresh-interval optional config (C01)
- `Infrastructure/ConfigurationResolver.cs` — `ResolveOptionalPositiveIntOrThrow` helper (C01)
- `Dockerfile` + new `docker-entrypoint.sh` — runs `update-ca-certificates` at container start (C02)
- `docker-compose.test.yml` — passes 30s / 10s JWKS refresh intervals to `missions` (C01)
- `_docs/04_refactoring/01-testability-refactoring/{list-of-changes,deferred_to_refactor,testability_changes_summary}.md`
-
-`dotnet build -c Release` clean (0 warnings, 0 errors). `ReadLints` clean on edited files.
-
-## Replay procedure when Atlassian MCP is back
-
-1. On next `/autodev`, the Bootstrap step (B1) reads this leftover, verifies MCP connectivity via `getAccessibleAtlassianResources`, and either:
-   - **MCP works** → delete this leftover, autodev proceeds to Step 5 normally.
-   - **MCP still down** → autodev surfaces the Choose A/B/C/D again (see `protocols.md`).
-2. If the user chose `tracker: local` in the interim and tasks were created with numeric prefixes, the next "Tracker Pending Sync" walks `_docs/02_tasks/todo/*.md` looking for `Tracker: pending` headers, creates the matching Jira ticket per task, rewrites the header, and renames the file from `NN_xxx.md` to `AZ-<id>_xxx.md`.
@@ -8,6 +8,7 @@
 **Component**: `missions/Azaion.Flights.csproj`, `missions/Program.cs`, every C# file with `namespace Azaion.Flights...` or `using Azaion.Flights...`, `missions/.cursor/skills` if any reference the namespace, the suite-level docker-compose `image:` field stays as-is until B10
 **Tracker**: AZ-544
 **Epic**: AZ-539
+**Status**: Done (2026-05-15)

 ## Outcome

@@ -8,6 +8,7 @@
 **Component**: `missions/Domain/`, `missions/Services/`, `missions/Controllers/`, `missions/Auth/` (claim names stay; only domain types rename), `missions/DataLayer/` (linq2db `[Table]` attribute strings AND foreign-key column names — but actual SQL migration is B9)
 **Tracker**: AZ-545
 **Epic**: AZ-539
+**Status**: Done (2026-05-15)

 ## Problem

@@ -8,6 +8,7 @@
 **Component**: `missions/Domain/` (Orthophoto, GpsCorrection), `missions/Controllers/` (orthophoto + live-gps + gps-correction endpoints), `missions/Services/` (corresponding service methods), `missions/Auth/` (the `"GPS"` policy), `missions/Services/MissionService` (cascade-delete branches)
 **Tracker**: AZ-546
 **Epic**: AZ-539
+**Status**: Done (2026-05-15)

 ## Problem

@@ -8,6 +8,7 @@
 **Component**: `missions/Controllers/` (route attributes), OpenAPI spec generation pipeline (whatever the project uses today), Postman / curl examples in `_docs/02_document/components/06_http_conventions/description.md` and `azaion-suite/_docs/02_missions.md`
 **Tracker**: AZ-547
 **Epic**: AZ-539
+**Status**: Done (2026-05-15)

 ## Outcome

@@ -8,6 +8,7 @@
 **Component**: `missions/DataLayer/Migrations/` (or whatever the project's actual migration directory is at HEAD), the `init` SQL seed for fresh-install devices
 **Tracker**: AZ-548
 **Epic**: AZ-539
+**Status**: Done (2026-05-15)

 ## Outcome

@@ -8,6 +8,7 @@
 **Component**: `missions/Services/VehicleService.cs`, `missions/DataLayer/` (if a partial unique index is added), `azaion-suite/_docs/02_missions.md` (spec catch-up if the rule stays)
 **Tracker**: AZ-551
 **Epic**: AZ-539
+**Status**: Done (2026-05-15)

 ## Problem