recess-cli 2.3.0 → 2.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "recess-cli",
-  "version": "2.3.0",
+  "version": "2.5.0",
   "description": "Safe Recess administration and family AI tools from the command line.",
   "license": "UNLICENSED",
   "repository": {

package/skill/recess-cli/SKILL.md

@@ -33,7 +33,7 @@ recess --json skills admin get recess-admin --all-references --reason "Load staf
 
 Use `skills guardian list` or `skills admin list` when the needed skill is not obvious. Never substitute one audience for the other. A guardian session cannot fetch the admin catalog; an admin may fetch either catalog.
 
-For machine-readable discovery, use `recess --json agent-context`; for a smaller syntax surface, use `recess --json help <noun> [verb]`. Unknown commands, flags, duplicate non-repeatable flags, missing flag values, and extra positional arguments fail explicitly.
+For machine-readable discovery filtered to the current session's locally decoded CLI scope, use `recess --json agent-context`; for a smaller syntax surface, use `recess --json help <noun> [verb]`. These discovery commands make no API request; `auth status` and `doctor` are the live session checks. Human help uses `◇` for shared commands and `◆` for exact-admin commands. Unknown commands, flags, duplicate non-repeatable flags, missing flag values, and extra positional arguments fail explicitly.
 
 ## Authentication
 
@@ -41,8 +41,9 @@ For machine-readable discovery, use `recess --json agent-context`; for a smaller
 - Headless (no browser): `auth request`, then a human approves the printed URL while signed in to
   Recess, then `auth poll`. The session takes on the **approver's** scope — a guardian approving
   grants family-only access, not staff access. Kids cannot approve.
-- Sessions last 12 hours and are rechecked against the live user role and permissions.
-- `auth status` inspects the current session; `auth logout` clears the stored session.
+- Sessions last 12 hours. `auth status` and `doctor` recheck the live user role and permissions;
+  discovery stays local and may reflect the minted scope until the next login.
+- `auth logout` clears the stored session.
 - The default API is production. If `RECESS_CLI_API_ORIGIN` is set, state the non-default origin before acting.
 
 Never print or paste session cookies, device codes, or config-file contents.
@@ -69,6 +70,42 @@ Every write is two-step:
 
 Any changed target, payload, local file, server revision, amount, recipient, or consequence requires a new preview and new approval. Never infer approval from the original request. If a confirmed invocation is interrupted, retry the unchanged command with the same operation key; never mint a new one for an uncertain write. Inspect recovery state with `recess --json jobs get <operation-key>`.
 
+## Building Studio apps (`recess apps`)
+
+Guides build Recess Studio apps in their own editor and publish them with the CLI; Studio never
+prompts a model for them.
+
+- `recess --json apps init <dir> --reason "..."` writes the locked scaffold plus `AGENTS.md` (the
+  runtime + template contract, pedagogy, and design rules). Read `AGENTS.md` before editing.
+- Edit only `skill.js`, `model.js`, `model.css`, `params.schema.json`, `params.json`. Locked files
+  fail validation if changed.
+- Write `contract.json` (the BuildContract from `AGENTS.md`) and `manifest.json`
+  (`{title, description, template?}`) before validating.
+- `recess --json apps validate [dir] --reason "..."` runs Studio's deterministic validation on the
+  uploaded files and returns `report.failReasons`; fix every reason and rerun. Nothing is published.
+- `recess --json apps publish [dir] --reason "..."` validates, then the independent reviewer judges
+  the app; on pass it becomes the current version at `appUrl`. `REJECTED` carries the reviewer's
+  findings — fix them and publish again. Both commands wait for the result (`--no-wait` to return the
+  build id and poll with `apps status`).
+- `recess --json apps pull <project-id> [dir]` downloads a project you own to keep editing it.
+- `recess --json apps standards "<words or notation>"` finds the CCSS standard for `manifest.json`
+  (`"grade 4 adding fractions"` → `4.NF.B.3a`…); guides rarely know the codes, look them up.
+
+Two ways in. If the guide names a kid or a todo, pull the analysis first and build against it;
+otherwise build from their description:
+
+- `recess --json students todos --student <kid-id> [--analyzed]` lists the kid's recent todos with
+  CCSS tags and `analyzed` (a forensic analysis exists); `recess --json students analysis --todo <id>`
+  returns it pruned for building — patterns with `instanceKey`, root cause, prescriptions, the
+  standard, grade band, interests. No name, no frames.
+- `recess --json apps init <dir> --for-todo <todo-id>` writes the scaffold plus `brief.md` (that
+  analysis as an assignment) and remembers the kid. Build to the brief: remediate mode, items the
+  kid would miss the observed way, `template.misconceptions` = the pattern keys.
+- `recess --json apps publish --assign <kid-id> [--due YYYY-MM-DD]` publishes and, on `COMPLETE`,
+  creates the kid's todo (linked to the source todo when init used `--for-todo`). A rejected build
+  assigns nothing. `recess --json apps assign [dir] --student <kid-id>` assigns an already-published
+  app.
+
 ## Shared constraints
 
 - Use high-level CLI commands. The raw escape hatch is GET-only:

package/skill/recess-cli/agents/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "2.4.0",
-  "minCliVersion": "2.1.0"
+  "version": "2.5.0",
+  "minCliVersion": "2.4.0"
 }