API Evangelist enhancements for the Flare Therapeutics Content API

# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Flare Therapeutics Content API
  version: 1.0.0
extends: openapi/flare-therapeutics-content-openapi.yml
x-generated: '2026-08-12'
x-method: generated
x-source: >-
  Generated by the API Evangelist enrichment pipeline on 2026-08-12. Records the enhancements API
  Evangelist added on top of the raw WordPress route index at https://www.flaretx.com/wp-json/.
  Flare Therapeutics publishes no OpenAPI, so there is no provider-authored original to mutate —
  this overlay documents what we contributed so the derivation stays auditable and separable from
  the provider's own contract.
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apis.io/providers/flare-therapeutics/
    x-apievangelist-harvested: '2026-08-12'
    x-apievangelist-contribution: >-
      Operation summaries, descriptions, operationIds, tag groupings, response schemas, pagination
      headers, error responses and error examples were authored by API Evangelist. The route paths,
      HTTP methods and every query parameter were taken verbatim from the provider's published route
      index, and every collection count was read from a live X-WP-Total header.
- target: $.info
  update:
    x-provider-publishes-openapi: false
    x-provider-developer-program: false
    x-surface-class: cms-content-api
- target: $.paths['/wp/v2/posts'].get
  update:
    x-apievangelist-note: >-
      The company news archive and the highest-traffic operation on the surface — 42 press releases,
      news-coverage items and scientific presentations from 2021-05-13 to 2026-06-30, classified by
      the four registered categories.
- target: $.paths['/wp/v2/media'].get
  update:
    x-apievangelist-note: >-
      The highest-value operation for a research consumer. 19 of the 419 attachments are
      application/* documents — the AACR, ASCO GU, SITC, ENA and ATS poster PDFs and an ASCO GU 2026
      Phase 1A data presentation — reachable with media_type=application. They are not otherwise
      enumerated anywhere machine-readable on the site.
- target: $.paths['/wp/v2/tags'].get
  update:
    x-apievangelist-note: Registered and reachable but empty (X-WP-Total 0) on this deployment.
- target: $.paths['/wp/v2/comments'].get
  update:
    x-apievangelist-note: Registered and reachable but empty (X-WP-Total 0) on this deployment.
- target: $.paths['/wp/v2/blocks'].get
  update:
    x-apievangelist-note: >-
      Registered and reachable but empty (X-WP-Total 0) — modelled so the surface is complete, not
      because it carries data.
- target: $.paths['/wp/v2/taxonomies'].get
  update:
    x-apievangelist-note: >-
      Worth reading for what it discloses rather than what it returns: post_tag declares
      types [post, team_member], which exposes the existence of a `team_member` post type that is
      registered in the CMS but absent from /wp/v2/types and therefore unreadable over REST.
- target: $.components.schemas.Post
  update:
    x-apievangelist-note: >-
      yoast_head, yoast_head_json, acf and class_list are deployment-specific extensions added by
      the Yoast SEO and Advanced Custom Fields plugins, not part of the upstream wp/v2 Post
      contract. They were observed on live responses on 2026-08-12 and may disappear on a plugin
      change. acf is an empty array on every object sampled.
- target: $.components.schemas.Error
  update:
    x-apievangelist-note: >-
      The WordPress REST error envelope. Deliberately not remapped to RFC 9457 problem+json — see
      errors/flare-therapeutics-problem-types.yml for why no problem-type URIs are invented here.