fix(docs): make the reference schema actually valid

Validated the schema block with prisma@7.9.0 instead of trusting it by
inspection. It reported 182 errors; the causes were three:

- Prisma enums require one value per line. Writing them compactly produced
  146 cascading errors, including bogus "attribute not known" reports on
  perfectly good @@index lines.
- Organization declared assets, alerts, risks, incidents and documents, but
  those models had no inverse relation field. Prisma needs both sides, so
  the FK that guarantees a record cannot outlive its tenant was missing.
- Prisma 7 removed url from the datasource block: the connection string now
  belongs to prisma.config.ts and to a driver adapter passed to
  PrismaClient. Documented, with the consequence for our env variables.

The schema now validates. Also corrected two internal inconsistencies:
ScoreBreakdown is generic over its band, because a vessel is READY while an
organization is NORMAL and neither vocabulary should be assignable to the
other; and the Phase 6 acceptance criterion no longer promises a band
transition that the formula does not produce (100 to 85 is still Ready) —
it asserts the arithmetic instead. A test that demanded a band change would
push someone to inflate the asset weight to make it pass.

Documenting a schema that does not compile is the same failure this project
criticises elsewhere, so DATABASE.md now records that it was verified.

Author: TheAlphaOffshoreCode

README.md

@@ -123,7 +123,7 @@ real commands, verified, and not before.
 
 From Phase 1 onward, no phase is considered done until all of these pass in CI:
 
-```
+```text
 lint  ·  typecheck  ·  unit + integration tests  ·  build  ·  secret scan
 ```
 

docs/API.md

@@ -38,7 +38,7 @@ Rules:
   depend on the schema's shape, and a Prisma type leaking into a component takes fields with it
   that were never meant to be rendered.
 * Reads are never cached across tenants. Cache tags always include the organization id:
-  `revalidateTag(\`org:${ctx.organizationId}:vessels\`)`.
+  ``revalidateTag(`org:${ctx.organizationId}:vessels`)``.
 * Pagination is mandatory on list queries.
 
 ```ts

docs/ARCHITECTURE.md

@@ -106,7 +106,7 @@ flowchart TB
 
 ### 3.2 The dependency rule
 
-```
+```text
 presentation → application → domain
                     ↓
              infrastructure
@@ -231,7 +231,7 @@ Two scores, one formula family, always returned **with a breakdown**.
 
 **Vessel Readiness Score (VRS), 0–100** — weighted mean of four sub-scores:
 
-```
+```text
 VRS = round(0.30·W + 0.30·A + 0.20·R + 0.20·O)
 ```
 
@@ -256,10 +256,19 @@ status panel: `≥85 Normal`, `70–84 Attention`, `50–69 Warning`, `<50 Criti
 
 Every score returns:
 
+The two scores share the formula machinery but **not** their band vocabulary: a vessel is
+`READY / ATTENTION / RESTRICTED / CRITICAL`, while the organization-level panel reads
+`NORMAL / ATTENTION / WARNING / CRITICAL`. Same numeric cut-offs, different words, because "this
+vessel is restricted" and "the operation is in warning" are different statements. The type is
+generic over the band so neither set can be assigned where the other belongs:
+
 ```ts
-type ScoreBreakdown = {
+type VesselBand = 'READY' | 'ATTENTION' | 'RESTRICTED' | 'CRITICAL'
+type OperationalStatus = 'NORMAL' | 'ATTENTION' | 'WARNING' | 'CRITICAL'
+
+type ScoreBreakdown<Band extends string> = {
   total: number
-  band: 'READY' | 'ATTENTION' | 'RESTRICTED' | 'CRITICAL'
+  band: Band
   degraded: boolean            // some input was missing
   factors: Array<{
     key: 'weather' | 'assets' | 'risks' | 'alerts'
@@ -287,7 +296,7 @@ server-side. Illegal transitions return a typed error; every accepted transition
 
 **Read (Server Component):**
 
-```
+```text
 page.tsx (RSC) → features/x/queries/getX(ctx, params)
                → tenant-scoped Prisma query (+ provider call if external)
                → domain projection (scores, verdicts)
@@ -296,7 +305,7 @@ page.tsx (RSC) → features/x/queries/getX(ctx, params)
 
 **Write (Server Action):**
 
-```
+```text
 client form → server action
   1. getSessionContext()        → { userId, organizationId, role }  — never trust client input
   2. Zod parse of the payload   → typed input or field errors
@@ -420,7 +429,7 @@ written against a concrete implementation.
 
 ## 9. Directory structure
 
-```
+```text
 ocean-command/
 ├── prisma/
 │   ├── schema.prisma
@@ -528,7 +537,7 @@ non-optional** — they are the tests that stop a security regression from shipp
 
 GitHub Actions on every push and PR:
 
-```
+```text
 lint  →  typecheck  →  unit + integration tests (Postgres service container)  →  build
                           ↓
                     secret scan