Core API Rewrite

OBJECTIVE

The main objective is to retire the legacy REST endpoints behind a single GraphQL schema, so clients ask for exactly the fields they need. Deleted: Reads and writes both ship in v1. Inserted: Reads only in v1; mutations follow once the schema settles.

APPROACH

The schema is derived from the existing resource models rather than written from scratch. Each query runs alongside its REST twin for two weeks before the old route is switched off.

type Project {
  id: ID!
  callsign: String!
  status: Status!
}

type Query {
  project(id: ID!): Project
  projects(status: Status): [Project!]!
}

> RX: Ship reads first. Hold the mutations until the schema has survived one full release.

Inline code reads like this: GET /projects?status=active