@oprt/cli 0.3.0 → 0.4.0

package/README.md

@@ -31,11 +31,12 @@ into the file an agent reads on every turn: `AGENTS.md` by default, `CLAUDE.md`
 Running it again replaces only the block. `search` ranks components and recipes by need
 (`--limit` is a whole number from 1 to 50). `component` prints one component's props, what each
 option value is for, its nesting rules and its example. `check` reads `.tsx` and `.jsx` files with
-the project's own TypeScript (5 or 6; TypeScript 7 has no JavaScript syntax API to read with) and
-reports invalid option values, unknown exports, forbidden nesting, missing required props and breaks
-of the house rules. `doctor` says whether lookups and code checking can run here, one at a time,
-and why checking is blocked when it is. `mcp` serves the lookups and the check over the Model
-Context Protocol on stdin and stdout, with no dependencies.
+a parser that ships inside this package (Babel's, in TypeScript and JSX mode), so it works in any
+project: no TypeScript, or any version of it, is needed. It reports invalid option values, unknown
+exports, forbidden nesting, missing required props and breaks of the house rules. `doctor` says
+whether lookups and code checking can run here, one at a time, which parser checking reads with, and
+why checking is blocked if the parser file is ever missing. `mcp` serves the lookups and the check
+over the Model Context Protocol on stdin and stdout, with no dependencies to install.
 
 `check` says how much it read. `evaluation_status` is `evaluated_clean` only when every file was
 read in full and nothing was found; otherwise it is `evaluated_with_findings`,
@@ -44,15 +45,15 @@ with its place; or some files did not parse), `not_evaluated` (no file parsed) o
 `no_files_evaluated` (nothing was read, for example a Markdown file). A file that does not parse
 is reported as `SYNTAX_ERROR` findings and is never clean. Types and rendering are not checked.
 Exit codes: `0` when what was read has no errors (warnings fail only with `--strict`; limits do not
-fail the run), `1` for an error, a file that did not parse, no file read, or no usable TypeScript,
+fail the run), `1` for an error, a file that did not parse, no file read, or a parser that cannot be loaded,
 `2` for a usage error or a path that does not exist.
 
 Every command takes `--json`, `list` and `add` included, and answers
-`{ "apiVersion": 1, "type": "…", "identity": {…}, "data": … }`. `identity` keeps four things
+`{ "apiVersion": 2, "type": "…", "identity": {…}, "data": … }`. `identity` keeps four things
 apart: `cli_version` (this package), `contract_version` (the `@oprt/react` version the contract
 describes), `contract_digest` (`sha256:` of `dist/contract.json`) and `schema_version` (this
 result format, the same number as `apiVersion`). A failure is
-`{ "apiVersion": 1, "error": "…", "code": "ERR_…", "suggestions": […], "identity": {…} }`; codes
+`{ "apiVersion": 2, "error": "…", "code": "ERR_…", "suggestions": […], "identity": {…} }`; codes
 are stable and only ever added to. `component --dense --json` is a compact form of the same data.
 `oprt mcp` returns the same envelope as each tool's structured result, with an `outputSchema` on
 every tool (a summary of the full schema, so the tool list is about 5.4 KB); a check that finds problems is a successful call, and a call that could not run is an