Update docs per recent changes

Author: camdecoster

src/types/ARCHITECTURE.md

@@ -8,8 +8,9 @@ How TypeScript types are organized in plotly.js.
 ┌──────────────────────────────────────────────────────────────┐
 │  Consumer surface (what `npm install plotly.js` exposes)     │
 │  lib/index.d.ts — wired via package.json#types               │
-│  Curated re-exports of public types + 'export as namespace   │
-│  Plotly' for namespace and global usage.                     │
+│  `export type *` for generated schema types + explicit       │
+│  re-exports of hand-written types + `export as namespace     │
+│  Plotly` for global/namespace usage.                         │
 └──────────────────────────────────────────────────────────────┘
                           │
                           ▼
@@ -23,8 +24,9 @@ How TypeScript types are organized in plotly.js.
 │  Hand-written types      │  │  Generated types               │
 │  src/types/core/*.d.ts   │  │  src/types/generated/...       │
 │  src/types/lib/*.d.ts    │  │                                │
-│                          │  │  schema.d.ts — from schema     │
-│                          │  │  (traces + layout + shared)    │
+│                          │  │  schema.d.ts — common enums,   │
+│                          │  │  traces, layout, animation,    │
+│                          │  │  config, _internal namespace   │
 └──────────────────────────┘  └────────────────────────────────┘
 ```
 

src/types/CONVERTING_ATTRIBUTES.md

@@ -116,13 +116,14 @@ the attribute object's runtime shape changed (most often a missed
 
 ```bash
 git add src/<path>/attributes.ts \
-        src/<path>/index.js src/<path>/defaults.js  # (whichever consumers you updated) \
-        src/types/core/<file>.d.ts \
-        src/types/generated/
+        src/<path>/index.js src/<path>/defaults.js  # (whichever consumers you updated)
 git commit -m "Convert <component> attributes to TypeScript"
 ```
 
-The conversion is a single self-contained commit per file.
+The conversion is a single self-contained commit per file. There's
+nothing to commit under `src/types/` for a correct conversion — the
+generated types are byte-identical (which is exactly what
+`schema-typegen-diff-check` confirmed in step 6).
 
 ## Worked example: modebar
 
@@ -149,8 +150,8 @@ The schema does not describe these — they remain in `src/types/`:
 - **Events** (`PlotMouseEvent`, `LegendClickEvent`, etc.)
 - **Public API function signatures** (`Plotly.newPlot`, `relayout`, ...)
 - **Internal types** (`FullLayout._modules`, `GraphDiv._fullData`, ...)
-- **Utility types** the mapped type bottoms out on (`Color`, `Datum`,
-  `TypedArray`, `MarkerSymbol`, ...)
+- **Utility types** (`Color`, `Datum`, `TypedArray`, `MarkerSymbol`, etc.) —
+  these are the primitives the generator's emitted types reference.
 
 If you find yourself converting one of these, stop and ask.
 
@@ -211,5 +212,5 @@ Pick from this priority list. Lower-numbered items are smaller / simpler.
 ## Working in parallel
 
 Multiple converters can work on different attribute files in parallel.
-Merge conflicts are rare and limited to the hand-written type files when
-removing types — manual conflict if two converters touch the same file.
+Each conversion is self-contained within one component's directory plus
+its direct `require()`-callers, so merge conflicts are rare.

src/types/GENERATOR.md

@@ -21,8 +21,10 @@ Run via `npm run schema`.
 `tasks/generate_schema_types.mjs` is called by `tasks/schema.mjs` after
 writing `plot-schema.json`. The generator walks `schema.traces`,
 `schema.layout.layoutAttributes`, `schema.animation`, `schema.frames`, and
-`schema.config.edits`, mapping each attribute's `valType` metadata to a
-TypeScript type.
+`schema.config` (including `schema.config.edits`), mapping each attribute's
+`valType` metadata to a TypeScript type. The set of meta keys to strip
+during emission is read from `schema.defs.metaKeys` so any addition to the
+schema's metadata format is picked up automatically.
 
 ### Phase 0: Common enum discovery
 
@@ -109,7 +111,7 @@ The Layout interface includes subplot index signatures:
 // etc.
 ```
 
-### Phase 5: Animation, frame, and edits interfaces
+### Phase 5: Animation, frame, edits, and config interfaces
 
 `AnimationOpts` is emitted from `schema.animation` (references the
 injected `Transition` and `AnimationFrameOpts` shared types). `Frame` is
@@ -128,6 +130,15 @@ The override mechanism is the `fieldOverrides` param on `attrsToProperties`
 schema can't self-reference. `Edits` is emitted from `schema.config.edits`
 without overrides (all fields are concrete booleans).
 
+`ConfigBase` is emitted from `schema.config` after registering Edits'
+fingerprint in `sharedTypes`, so `edits?: Edits` references the named
+interface rather than re-inlining the subtree. Seven config fields whose
+schema `valType` is `any` (`locales`, `modeBarButtons`,
+`modeBarButtonsToAdd`, `modeBarButtonsToRemove`, `setBackground`,
+`showSources`, `toImageButtonOptions`) come through as `any`; the
+hand-written `Config` in `core/config.d.ts` overrides them via
+`Omit<ConfigBase, keyof ConfigOverrides> & ConfigOverrides`.
+
 ### Phase 6: Internal namespace
 
 Names in `INTERNAL_INTERFACES` are wrapped in `export namespace _internal {
@@ -182,7 +193,7 @@ src/types/generated/schema.d.ts
 ├── Trace interfaces (ScatterData, BarData, ... — 49 traces)
 ├── Layout component interfaces (LayoutAxis, Legend, Scene, Annotation, etc.)
 ├── Layout interface
-└── Animation / frames / config (AnimationOpts, Frame, Edits)
+└── Animation / frames / config (AnimationOpts, Frame, Edits, ConfigBase)
 ```
 
 Regenerate with `npm run schema`.
@@ -213,9 +224,10 @@ Attribute name overrides via `ATTR_NAME_OVERRIDES` map specific attribute
 paths to a type alias regardless of valType (e.g. `marker.symbol` →
 `MarkerSymbol`).
 
-Reserved keys stripped from the output: `editType`, `role`, `description`,
-`impliedEdits`, `_isSubplotObj`, `_isLinkedToArray`, `_arrayAttrRegexps`,
-`_deprecated`.
+Reserved keys stripped from the output come from `schema.defs.metaKeys` —
+currently `editType`, `role`, `description`, `impliedEdits`,
+`_isSubplotObj`, `_isLinkedToArray`, `_arrayAttrRegexps`, `_deprecated`.
+New additions to that list are picked up automatically on regen.
 
 ## Extending the schema generator
 
@@ -302,18 +314,19 @@ console.log(s.layout.layoutAttributes.xaxis);  // inspect layout attrs
 console.log(s.traces.scatter.attributes);       // inspect trace attrs
 ```
 
-## Public API re-export check
+## Public API re-export
 
 `lib/index.d.ts` uses `export type * from '../src/types/generated/schema'`,
 so every top-level exported type from `schema.d.ts` is automatically
 re-exported to consumers. Types inside the `_internal` namespace are still
 reachable via `_internal.X` (the namespace itself is exported by the
 wildcard) but their bare names are not.
 
-`tasks/schema.mjs` short-circuits its per-name re-export verification
-when the wildcard is detected. If you ever replace the wildcard with an
-explicit allowlist, the per-name check runs and warns about any
-exported-but-not-re-exported types.
+The wildcard is load-bearing: it removes the maintenance burden of keeping
+`lib/index.d.ts` in sync with new schema additions. If anyone ever swaps
+it for an explicit allowlist, restore the per-name re-export verifier
+that previously lived in `tasks/schema.mjs` (see git history) — otherwise
+new generated types will silently fail to surface in the public API.
 
 ## CI integration
 

src/types/SETUP.md

@@ -23,7 +23,7 @@ Quick reference for the TypeScript toolchain in plotly.js.
 - [tsconfig.json](../../tsconfig.json) — type checker config
 - [esbuild-config.js](../../esbuild-config.js) — bundler config
 
-Both target ES2016. Strict mode is currently **off** (`strict: false`) for incremental adoption — types tighten over time as files convert.
+Both target ES2016. `strict: true` is on in `tsconfig.json` — the type system is fully strict for the `.d.ts` declarations and converted TypeScript sources. The remaining JS files coexist via `allowJs: true` and are type-checked loosely (no strict null checks etc. on the JS side).
 
 ## npm scripts