@openengio/cli 0.33.0 → 0.36.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openengio/cli",
-  "version": "0.33.0",
+  "version": "0.36.0",
   "license": "Apache-2.0",
   "type": "module",
   "engines": {

package/skill/conventions/SKILL.md

@@ -186,8 +186,12 @@ An enum's `members` is a list of strings or finite numbers. A published member c
 
 ### number
 
+A number or integer may declare a unit under schema language version `4`. The value is still
+a number, displayed with that unit. Publication refuses unknown symbols (`unknown-unit`), and
+a later version may add a unit but cannot change or remove it (`changed-unit`).
+
 ```json
-{"kind": "number"}
+{"kind": "number", "unit": "kg"}
 ```
 
 ### integer
@@ -251,6 +255,21 @@ one property's bytes.
 }
 ```
 
+### bound
+
+A quantitative constraint on a top-level object property, or an entry in a top-level array of
+bounds, under schema language version `4`. A value such as
+`{"over":"each","quantity":"mass","comparison":"<=","value":100,"unit":"kg"}` compares
+each linked object's mass against 100 kg. `sum`, `min`, `max` and `count` aggregate the linked
+values. A limit may instead be `{ "property": "allocation" }`, read from this object's own
+numeric property. `within` requires a non-negative `tolerance`; other comparisons take none.
+Compatible units are converted for comparison; incompatible units answer `unit-mismatch`.
+Bounds answer independently of review: clearing a suspect link does not make an `out` bound `in`.
+
+```json
+{"kind": "bound"}
+```
+
 ## 9. Examples
 
 These are small type documents to adapt and validate in a change set before accepting it.

package/skill/openeng/SKILL.md

@@ -54,6 +54,44 @@ attachment properties, and `openeng attachment get <object> <property> [--out <p
 project and ref flags to download it. The `get` command uses the descriptor's file name when `--out`
 is omitted. The accepted classes and file-size limit are in `openeng skill conventions`.
 
+## Link review and impact
+
+Read `openeng links status <object> --project <id> --ref <ref>` before reviewing a tracked
+link. Review states are `cleared` (reviewed against the current upstream), `suspect` (significant
+upstream content changed), `unreviewed` (never cleared), `not-visible` (the upstream cannot be
+read) and `too-many-links` (the chain exceeds its bound). Bounds have their own states: `in`,
+`out`, `none`, `no-value`, `unit-mismatch` and `not-visible`; clearing does not change them.
+Aggregates also show coverage and hidden or missing counts. Numeric output shows its unit.
+
+After reviewing the upstream, run `openeng links clear <link> --version <upstreamVersion>
+--project <id> --ref <ref>`. Take the opaque version from the status answer. For an atomic batch,
+list up to 100 link ids and repeat `--version` once per link in the same order. On
+`upstream-changed`, read status and review before sending its new version; do not replace the
+precondition blindly. `upstream-not-readable` requires upstream read access. There is no
+organisation clearing setting: the edge's write rule decides who may clear. User, run-apply,
+client and service tokens are admitted; run-explore and run-types are refused at admission.
+The object agent has no clearing tool; clear through this CLI or the SDK. Recover an unknown
+outcome by correlation before retrying.
+
+Use `openeng branches impact <ref> --base <base> --project <id>` to review changes against
+the merge base: review, bounds and aggregate changes, downstream reach to depth three and
+hidden counts. Added and removed links are marked. `head-moved` requires reading again;
+`over-bound` refuses the entire read. Add `--json` for each complete answer.
+
+## Hosted apps
+
+A hosted app is a React bundle that runs inside a project, in a sandbox, with the viewer's authority.
+Export a component that takes `{ client }` and start it by calling the runtime's
+`globalThis.__oe2HostedApp.mount(App)` as the bundle's last statement (the `@openengio/hosted-app`
+package that wraps this call is not published yet). Publish the built bundle with
+`openeng hosted-app publish <bundle> --project <id> --key <app key>`; it creates the app when the
+project has none under that key, and prints the version and its SHA-256. If the app holds the
+one-wall permission, the output also carries a warning: read it to the person and do not hide it.
+`openeng hosted-app list --project <id>` lists the apps, `openeng hosted-app versions <app key>
+--project <id>` lists an app's versions, and `openeng hosted-app revoke <app key | app id | version id>
+--project <id>` revokes a version (an id starting `hav_`) or the whole app by its key or `app_` id. Revoke only when the
+person asks. Hosted apps run only in Google Chrome.
+
 ## Rules that hold for every command
 
 - Add `--json` when you read the answer yourself. It prints one JSON value on standard output.
@@ -160,7 +198,10 @@ to understand each part, then design the model with the person before you draft
    `openeng types list`.
 
 Property kinds are `null`, `boolean`, `string`, `number`, `integer`, `person`, `enum`, `array`,
-`object`, `datetime` and `attachment`. Use `datetime` for an instant. A value is an RFC 3339 date-time
+`object`, `datetime`, `attachment` and `bound`. Under language version `4`, numeric properties may
+declare a `unit`, such as `kg`; publication refuses an unknown symbol (`unknown-unit`) or a later
+change or removal (`changed-unit`). A `bound` is a top-level object property, or a top-level array
+of bounds, under version `4`. See `openeng skill conventions` for its shape. Use `datetime` for an instant. A value is an RFC 3339 date-time
 with an explicit offset and zero to three fraction digits, such as `2026-10-19T22:30:00+01:00` or
 `2026-10-19T21:30:00Z`; a value with no offset, an impossible date or time, or four or more fraction
 digits is refused. The platform stores it as `YYYY-MM-DDTHH:MM:SS.sssZ`, the same instant in UTC.
@@ -365,6 +406,7 @@ using the type key from the object read. Explore also reads its selected object
 2. Query the objects you need with `openeng objects-sdk queryObjects --json`. Keep each object's
    project with its identifier; one set may contain objects of several projects in your organisation.
    To combine two selections on the same ref, send `{ "kind": "set", "op": "difference", "left": { "kind": "objects", "typeKey": "..." }, "right": { "kind": "objects", "typeKey": "..." }, "limit": 100, "continuation": null }`. `op` may be `union`, `intersection` or `difference`. Each operand may have its own `projects`, `filters` and `steps`; operands cannot be nested set operations.
+   To select several object types in one paged query, use `typeKey: null` with a top-level `{ "kind": "type", "op": "in", "values": ["part", "system"] }` filter. The list holds 1 to 100 published type keys; combine it with a text filter to search those types. Follow the returned continuation without changing the selection.
    `aggregateObjects` also accepts `operation: "average"` with one numeric `property`; the result includes its mean and the count averaged, and omits the mean when that count is zero.
 3. Call `openeng objects-sdk createObjectSet` with a name and the selected addresses, following its
    help. Keep the returned set identifier and revision. Retrying with the same idempotency key