@openora/mcp 0.4.1-canary.142 → 0.4.1-canary.145

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +5 -4
  2. package/docs/catalog.json +2582 -248
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -34,7 +34,7 @@ order:
34
34
  1. `OSS_CATALOG` env var (absolute path), if set.
35
35
  2. `<cwd>/docs/catalog.json`, then `<cwd>/node_modules/@openora/mcp/docs/catalog.json`,
36
36
  then walking up from `cwd` for a `docs/catalog.json`.
37
- 3. The package's own bundled snapshot (shipped in `docs/catalog.json`).
37
+ 3. The package's own snapshot (`docs/catalog.json`, generated when the platform repo installs and shipped with every release).
38
38
 
39
39
  ## Registering in a consumer's `.mcp.json`
40
40
 
@@ -55,6 +55,7 @@ order:
55
55
 
56
56
  ## Keeping the catalog current
57
57
 
58
- The catalog is regenerated upstream in the platform repo via `pnpm regen`
59
- (which runs `tools/gen/gen-catalog.ts`). A new `@openora/mcp` release ships the updated
60
- snapshot; pin `OSS_CATALOG` to a freshly generated file to override it locally.
58
+ The platform repo never commits the catalog: `tools/gen/gen-catalog.ts` regenerates it on
59
+ every install (`prepare`), after every pull or branch switch (husky), and on `pnpm regen`. A
60
+ checkout and every `@openora/mcp` release therefore carry a snapshot of the current source; pin
61
+ `OSS_CATALOG` to another generated file to override it locally.