v0.2.0

Minor Changes

• #5 78a084a Thanks @bryantgillespie! - Add the directus-self-hosting skill, plus references for indexes, schema changes on live data, new projects from starters, multi-tenancy, query performance, member sign-up, import and export, audit and restore, and AI settings. Add a weekly check that opens an issue when Directus ships a newer release.

• #2 2612309 Thanks @bryantgillespie! - Add Codex metadata (agents/openai.yaml) to every skill and document installing the plugin in Codex.

• #5 1aa0c7a Thanks @bryantgillespie! - Verify every skill against Directus 12.6.0: the 12.6.0 upgrade hop (Node 26, no Corepack in node:26 images, telemetry endpoint, AI model defaults, /mcp 405, export folder setting), the 12.6 SDK and extensions version map, richtext extensions, and source links pinned to v12.6.0. Read core-tier limits from GET /license instead of hardcoding them, trim the extensions references, and fix third-round review findings (core-tier delete rows, flows request errors, auth refresh mode, Insights variables and editing, Kubernetes notes). Behavior evals take --image and default to 12.6.0.

• #5 0c96dea Thanks @bryantgillespie! - New directus-content skill for editing content as an editor would, over MCP or the API: writes go live (no version writes over MCP or REST items), arrays replace relations, M2M bare ids are junction ids, edit blocks in place, publishing, text formats, and files. directus now hands content edits to it.
  directus: page-builder (M2A) edits in a content version need each junction row's collection in the delta, and versioned reads must select it.

• #3 723c77f Thanks @bryantgillespie! - Add public asset guidance: public API vs server-side-only content (both documented), serve assets directly from a public folder (two levels at most, short field list), point public file fields at that folder, and spell out that on the core tier public file read means every file.

• #5 cf64e17 Thanks @bryantgillespie! - Cut directus-sdk and directus-environment-sync to their traps and commands, since models pass every eval case without them. Trim index, flow recipe, and loop references that only covered tasks models already get right. Document that Run Script can't follow a condition's reject path, and that UUID keys need special: ["uuid"].

• #5 a6cdcd8 Thanks @bryantgillespie! - Add version notes for older majors to the base directus skill (references/versions-v9.md to versions-v12.md): what the skills would get wrong on each major and what to do instead, with minor-version gates. Every router now checks the instance version first and points there. Also: one junction naming scheme across skills (post_tags.tag), copyable examples on 12.6.0, and fourth-round review fixes.

Patch Changes

• #5 f9f364c Thanks @bryantgillespie! - directus-upgrade: health checks probe 127.0.0.1, not localhost (the image's wget fails on ::1).
  directus-upgrade: the caller grep step names the SDK breaking-changes table.
  directus-extensions: auto reload misses an extension's first build (touch package.json or restart), and Docker Desktop bind mounts need CHOKIDAR_USEPOLLING.
  directus: JSON field filtering (_json flat paths, numbers as JSON, json() response keys and aliases, Postgres text sort).

• #5 39c2b50 Thanks @bryantgillespie! - Compact every markdown table (no alignment padding) and turn router reference tables into lists: 13% fewer characters across skills, 8% in routers. The validator rejects padded tables.
  directus-content-modeling: new existing-database reference (configure with PATCH, enums as choices plus field validation, what Directus can't use).
  directus-content-modeling: both junction relations need meta (one_field, junction_field) for the Studio's M2M and translations interfaces.

• #5 c2a6360 Thanks @bryantgillespie! - Every description opens with "Load first, before exploring code, when": Haiku loaded the right skill in 22 of 37 trigger cases before and 33 to 34 after. Sonnet stays at 37 of 37.

• #5 6805737 Thanks @bryantgillespie! - Mark Directus's preferred conventions as Recommended: instead of House rule:.

• #5 1503f31 Thanks @bryantgillespie! - Fix second-round review findings: the publish-email recipe (query reads always return arrays), the flow mail rate limit shared by utility loops, deleting linked operations, realtime uid and default limits, own-profile permissions, flow license counting, upload filename fields, Insights limits and overlaps, self-hosting compose (Redis host, secure cookies), custom index migrations on fresh environments, and several copyable snippets. Make licensing findable from the access-control description.

• #5 0cbe64b Thanks @bryantgillespie! - Fix fifth-round review findings: remove a wrong many-to-any note for 10.x, handle newer-than-12.6 instances and single-skill installs in every router's version check, drop duplicate version checks, route slow queries and AI settings to directus, and correct _some/_none, failed condition errors, the upgrade version map, backlink, re-registration, and Insights panel notes.

• #5 2aab5a7 Thanks @bryantgillespie! - Fix errors found in review: proxy trust advice (IP_TRUST_PROXY=true), many-to-many array writes (junction ids, duplicate links), field-rename PATCHes that leave a stray field record, M2A cascade rules, bulk-write flow events (keys), key plus query on item reads, trigger-flow arguments, schedule synchronization across instances, export download access, tenant slug uniqueness and file moves, the CI URL check order, and the post-upgrade cache clear. Add exact Insights panel options, the SQLite default trap, a reverse proxy example, and version gates. Shorten every skill description.