@receiz/ai-skills 104.0.0 → 105.0.0

package/README.md

@@ -1,6 +1,6 @@
 # Receiz AI Skills
 
-`receiz-app-builder-skill` is the authoritative v104 workflow for starting,
+`receiz-app-builder-skill` is the authoritative v105 workflow for starting,
 integrating, upgrading, diagnosing, and repairing repositories through the typed
 Receiz app contract, shared SDK compiler, CLI, and MCP tools.
 
@@ -12,7 +12,7 @@ Receiz is a proof-native artifact system. A Receiz object is not a database row.
 
 ## SDK, MCP, And Skills
 
-- SDK: `@receiz/sdk` is for building apps. It exposes validators, projections, proof memory, identity artifact helpers, public app-state, public store, commerce, wallet, sports, world, offline queues, webhooks, and sandbox helpers.
+- SDK: `@receiz/sdk` is the universal runtime; `@receiz/sdk/react` is React-only; `@receiz/sdk/compiler` is Node-only; `@receiz/sdk/testing` is browser-safe sandbox and conformance support.
 - MCP: `@receiz/mcp-server` is for agent tool access. It exposes SDK-backed tools for diagnostics, public reads, offline shape inspection, app-state/public-store actions, deterministic previews, and delegated writes. Artifact verification remains SDK `verification.verifyArtifact(file)` and requires continuity.
 - Skills: this package is operating doctrine. It tells an AI which Receiz primitive is active, which source of truth wins, which SDK or MCP rail to use, and what must never be assumed.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@receiz/ai-skills",
-  "version": "104.0.0",
+  "version": "105.0.0",
   "description": "Authoritative Receiz AI operating skills for proof-native SDK and MCP agents.",
   "type": "module",
   "files": [

package/receiz-app-builder-skill/SKILL.md

@@ -31,13 +31,15 @@ integration tooling beneath Receiz proof truth; inspection is not verification.
 
 ## Required Behavior
 
+Select the package boundary first: universal runtime from `@receiz/sdk`, React bindings from `@receiz/sdk/react`, Node-only app compiler APIs from `@receiz/sdk/compiler`, and sandbox/conformance support from `@receiz/sdk/testing`.
+
 1. Inspect the explicit repository root with `receiz_project_inspect` or `receiz app inspect`.
 2. Identify intended features and create or update the contract with `defineReceizApp` or `receiz_app_contract_create`.
 3. Compile a read-only plan with `compileReceizAppContract`, `receiz_app_plan`, or `receiz app plan`.
 4. Explain scopes, authority boundaries, findings, and every proposed file.
 5. Obtain explicit confirmation for the exact preview digest before mutation.
 6. Apply the smallest safe change set with `receiz_app_apply` or `receiz app apply`.
-7. Run generated conformance and repository tests.
+7. Run generated conformance, `receiz conformance`, and repository tests.
 8. Reinspect with `receiz_app_check` and report exact evidence.
 9. Use `receiz_app_upgrade` for version-aware upgrades and `receiz_app_explain` for findings.
 10. Report remaining manual work and blocked authority without claiming completion.
@@ -56,18 +58,19 @@ upgrade, diagnosis, and repair routes.
 
 ## MCP Usage Rules
 
-Use only the seven documented tools listed in
+Use the documented tools listed in
 [resources/workflow.md](resources/workflow.md). Inspection, contract proposals,
 planning, checking, upgrade planning, and explanation are read-only.
 `receiz_app_apply` returns a preview first and requires the exact digest as
 explicit confirmation. Every response must retain the MCP authority boundary.
+Use `receiz_app_repair` for confirmed deterministic repair, `receiz_scope_explain` for canonical scopes, `receiz_release_qualify` for read-only release evidence, `receiz_proof_trace` only with canonical artifact bytes for a verdict, and `receiz_webhook_replay` only after signature verification and exact confirmation.
 
 ## SDK Usage Rules
 
-Use `defineReceizApp`, `validateReceizAppContract`,
+Import `defineReceizApp`, `validateReceizAppContract`,
 `compileReceizAppContract`, `inspectReceizProject`,
 `planReceizIntegration`, `checkReceizIntegration`, `planReceizUpgrade`, and
-`explainReceizIntegrationFinding`. Artifact verification remains
+`explainReceizIntegrationFinding` from `@receiz/sdk/compiler`. Artifact verification remains
 `verification.verifyArtifact`; creation remains the SDK's authenticated native
 Record-before-Seal rail.
 
@@ -94,6 +97,7 @@ Read [resources/authority-boundaries.md](resources/authority-boundaries.md).
 Stop when a required delegated permission, identity proof, capability, or user
 decision is unavailable. Report the blocked boundary; do not fabricate it.
 Generated browser code may contain public origins but never server credentials.
+`receiz.extensions.ts` is developer-owned and create-once; regeneration must never overwrite it. Emulator evidence is `sandboxVerified`, never a production verified verdict.
 
 ## Examples
 

package/receiz-app-builder-skill/resources/workflow.md

@@ -7,10 +7,11 @@
 | Add or remove a rail | Update the contract, then plan | Apply only the changed digest |
 | Upgrade | `receiz_app_upgrade` | Apply approved package/generated changes |
 | Diagnose | `receiz_app_check`, `receiz_app_explain` | None until the finding is understood |
-| Repair | Reinspect generated-file drift | Regenerate Receiz-owned files only |
+| Repair | `receiz_app_repair` preview | Exact digest confirmation; regenerate Receiz-owned files only |
 
 After every mutation, run the returned verification commands and reinspect.
 The same repository must produce zero changes on the second run.
+Preserve the developer-owned `receiz.extensions.ts` sibling on every run. Finish with `receiz conformance` or `receiz_release_qualify`.
 
 Do not substitute inspection for verification, publication for settlement, or a
 successful write for proof admission.

package/receiz-mcp-agent-skill/resources/mcp-tool-map.md

@@ -1,6 +1,6 @@
 # MCP Tool Map
 
-## v104 Application Compiler
+## v105 Application Compiler And Semantic Operations
 
 | Need | Tool | Mutation |
 |---|---|---|
@@ -11,6 +11,11 @@
 | Check conformance | `receiz_app_check` | Read-only |
 | Plan upgrade | `receiz_app_upgrade` | Read-only |
 | Explain finding | `receiz_app_explain` | Read-only |
+| Repair application | `receiz_app_repair` | Exact digest confirmation required |
+| Trace proof | `receiz_proof_trace` | Read-only; canonical bytes required for verified verdict |
+| Replay webhook | `receiz_webhook_replay` | Signature verification and exact confirmation required |
+| Explain scope | `receiz_scope_explain` | Read-only |
+| Qualify release | `receiz_release_qualify` | Read-only |
 
 Repository inspection is not verification. These tools never supply an artifact
 verification verdict or proof authority.
@@ -20,7 +25,7 @@ Source: `packages/receiz-mcp-server/src/index.ts`.
 ## Diagnostics And Setup
 
 - `receiz_doctor`: SDK doctor for app/tenant diagnostics.
-- `receiz_capabilities`: inspect SDK capability readiness.
+- `receiz_capabilities`: use `capabilities.describe` for deterministic support and probe mode for readiness.
 - `receiz_required_scopes`: return stable scope constants by rail.
 - `receiz_runtime_blueprint`: return app runtime blueprint.
 - `receiz_authorize_url`: build Connect/OIDC authorize URL.
@@ -47,6 +52,7 @@ Source: `packages/receiz-mcp-server/src/index.ts`.
 - `receiz_proof_query`: delegated proof query projection.
 
 Use SDK `verification.verifyArtifact(file)` for verification; it requires enclosing integrity and ownership continuity.
+Emulator output is labeled `sandboxVerified`; never translate it into Receiz verification.
 
 ## Sports, Wallet, World
 

package/receiz-proof-skill/resources/sdk-reference.md

@@ -1,10 +1,12 @@
 # SDK Reference For Proof Work
 
-The v104 app compiler APIs (`defineReceizApp`, `compileReceizAppContract`, and
+The v105 app compiler APIs (`defineReceizApp`, `compileReceizAppContract`, and
 repository planning/checking functions) inspect and integrate applications.
 They do not verify proof bytes. Continue to use `verification.verifyArtifact`
 for the indivisible integrity, owner, namespace, and continuity verdict.
 
+Import runtime proof APIs from `@receiz/sdk`, React bindings from `@receiz/sdk/react`, compiler APIs from `@receiz/sdk/compiler`, and sandbox/conformance helpers from `@receiz/sdk/testing`. Emulator evidence is `sandboxVerified`, not production verification.
+
 Source: `packages/receiz-sdk/src/index.ts`, `packages/receiz-sdk/src/identity.ts`, `packages/receiz-sdk/src/react.ts`, and SDK package docs.
 
 ## Core Constants And Schemas