@receiz/ai-skills 103.0.0 → 104.0.0

package/README.md

@@ -1,8 +1,12 @@
 # Receiz AI Skills
 
+`receiz-app-builder-skill` is the authoritative v104 workflow for starting,
+integrating, upgrading, diagnosing, and repairing repositories through the typed
+Receiz app contract, shared SDK compiler, CLI, and MCP tools.
+
 This package teaches AI agents how to understand, verify, build with, and operate Receiz from the existing repository surfaces.
 
-It is published as `@receiz/ai-skills` and is an exact-version dependency of both `@receiz/sdk` and `@receiz/mcp-server`. Installing either package places these eight skill directories under `node_modules/@receiz/ai-skills` for explicit loading by an agent host.
+It is published as `@receiz/ai-skills` and is an exact-version dependency of both `@receiz/sdk` and `@receiz/mcp-server`. Installing either package places these nine skill directories under `node_modules/@receiz/ai-skills` for explicit loading by an agent host.
 
 Receiz is a proof-native artifact system. A Receiz object is not a database row. It is a proof-carrying artifact. The artifact's witnessed history is the truth boundary. Server state, database state, UI state, marketplace state, and model memory are projections only. Old witnessed truth is not stale. If a projection is wrong, rebuild it from object history. If truth is missing, append new truth. Never mutate witnessed truth.
 

package/package.json

@@ -1,10 +1,11 @@
 {
   "name": "@receiz/ai-skills",
-  "version": "103.0.0",
+  "version": "104.0.0",
   "description": "Authoritative Receiz AI operating skills for proof-native SDK and MCP agents.",
   "type": "module",
   "files": [
     "README.md",
+    "receiz-app-builder-skill",
     "receiz-builder-skill",
     "receiz-commerce-skill",
     "receiz-distribution-skill",
@@ -28,4 +29,4 @@
   "publishConfig": {
     "access": "public"
   }
-}
+}

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

@@ -0,0 +1,114 @@
+---
+name: receiz-app-builder-skill
+description: Use when starting, integrating, upgrading, diagnosing, or repairing a TypeScript or Next.js repository that uses Receiz application contracts, SDK compiler commands, generated files, or MCP app tools.
+---
+
+# receiz-app-builder-skill
+
+Build and upgrade Receiz applications from one typed contract. The compiler is
+integration tooling beneath Receiz proof truth; inspection is not verification.
+
+## When To Use This Skill
+
+- Use for `defineReceizApp`, `receiz.app.contract.v1`, or `receiz app` commands.
+- Use when adding Receiz to an existing repository or changing feature rails.
+- Use for deterministic integration plans, generated-file repair, and upgrades.
+- Use before calling Receiz MCP application compiler tools.
+
+## When Not To Use This Skill
+
+- Do not use repository inspection to verify an artifact.
+- Do not use it to invent proof objects, owners, continuity, or settlement.
+- Do not bypass `receiz-proof-skill` for byte-bearing artifact verification.
+
+## Core Receiz Laws
+
+- Never treat a database, server, marketplace, UI, model response, or cache as final authority.
+- The sealed proof object remains stronger than SDK, compiler, MCP, AI, and repository state.
+- Proof-object creation uses authenticated native Record before Seal.
+- Existing witnessed history is never rewritten; append missing truth and rebuild incorrect projections.
+- MCP inspection is not verification and MCP never becomes proof authority.
+
+## Required Behavior
+
+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.
+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.
+
+Read [resources/workflow.md](resources/workflow.md) for new, existing, feature-change,
+upgrade, diagnosis, and repair routes.
+
+## Forbidden Behavior
+
+- Never invent APIs, tools, scopes, proof IDs, owners, settlement, verification results, authorization, or completed file changes.
+- Never write outside the explicit repository root or follow a symlink outside it.
+- Never overwrite unmarked application code.
+- Never put tokens, keys, identity artifacts, webhook secrets, or recovery material in code, plans, fixtures, logs, or MCP output.
+- Never add a traditional database as proof authority.
+- Never claim a plan, inspection, hash, MCP lookup, or successful compile verified a proof object.
+
+## MCP Usage Rules
+
+Use only the seven 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.
+
+## SDK Usage Rules
+
+Use `defineReceizApp`, `validateReceizAppContract`,
+`compileReceizAppContract`, `inspectReceizProject`,
+`planReceizIntegration`, `checkReceizIntegration`, `planReceizUpgrade`, and
+`explainReceizIntegrationFinding`. Artifact verification remains
+`verification.verifyArtifact`; creation remains the SDK's authenticated native
+Record-before-Seal rail.
+
+## Output Format
+
+```md
+Contract:
+Repository evidence:
+Features and scopes:
+Authority boundary:
+Read-only findings:
+Proposed files:
+Preview digest:
+Confirmation status:
+Checks run:
+Remaining manual work:
+What is proven:
+What is not proven:
+```
+
+## Safety And Security Boundaries
+
+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.
+
+## Examples
+
+- [Commerce](examples/commerce.md)
+- [Marketplace](examples/marketplace.md)
+- [Persistent world](examples/persistent-world.md)
+- [AI-operated application](examples/ai-operated.md)
+- [Profile or portfolio](examples/profile-portfolio.md)
+- [Content publishing](examples/content-publishing.md)
+- [Proof verifier](examples/proof-verifier.md)
+- [Minimal proof object](examples/minimal-proof-object.md)
+
+Resources:
+
+- [Workflow](resources/workflow.md)
+- [Authority boundaries](resources/authority-boundaries.md)
+- [Generated-file repair](resources/generated-file-repair.md)
+- [Upgrade rules](resources/upgrade-rules.md)

package/receiz-app-builder-skill/examples/ai-operated.md

@@ -0,0 +1,5 @@
+# AI-Operated Application Starter Contract
+
+Select only the feature rails the agent needs. Keep planning and inspection
+read-only, require explicit confirmation for mutations, and use delegated scopes
+as permission rather than proof authority.

package/receiz-app-builder-skill/examples/commerce.md

@@ -0,0 +1,6 @@
+# Commerce Starter Contract
+
+Use `defineReceizApp` with features `identity`, `proof`, `proofMemory`,
+`publicStore`, `commerce`, `media`, and `webhooks`. Compile the plan before
+adding checkout or publication. Ownership and settlement remain distinct proof
+boundaries.

package/receiz-app-builder-skill/examples/content-publishing.md

@@ -0,0 +1,5 @@
+# Content And Publishing Starter Contract
+
+Select `identity`, `proof`, `proofMemory`, `publicStore`, `media`, and
+`webhooks`. Publication is an authenticated append and does not replace the
+sealed source proof.

package/receiz-app-builder-skill/examples/marketplace.md

@@ -0,0 +1,5 @@
+# Marketplace Starter Contract
+
+Select `identity`, `proof`, `proofMemory`, `publicStore`, `commerce`, `media`,
+and `webhooks`. Require continuity-bound verification before listing projections
+and settlement authority before value transfer.

package/receiz-app-builder-skill/examples/minimal-proof-object.md

@@ -0,0 +1,5 @@
+# Minimal Proof-Object Starter Contract
+
+Select `identity` and `proof`. Use a real authenticated Receiz ID and the native
+Record-before-Seal sequence. Do not expose a path that seals before continuity
+exists.

package/receiz-app-builder-skill/examples/persistent-world.md

@@ -0,0 +1,5 @@
+# Persistent World Starter Contract
+
+Select `identity`, `proof`, `proofMemory`, `media`, `webhooks`, and `world`.
+First-paint durable verified world truth and append verified additions without
+replacing witnessed state.

package/receiz-app-builder-skill/examples/profile-portfolio.md

@@ -0,0 +1,4 @@
+# Profile Or Portfolio Starter Contract
+
+Select `identity`, `proof`, `proofMemory`, `publicStore`, and `media`. Preserve
+owner Receiz ID continuity and project public originals only after verification.

package/receiz-app-builder-skill/examples/proof-verifier.md

@@ -0,0 +1,5 @@
+# Proof Verifier Starter Contract
+
+Select `proof` and optionally `proofMemory`. Route byte-bearing files to SDK
+`verification.verifyArtifact`. MCP inspection and repository checks never supply
+the verification verdict.

package/receiz-app-builder-skill/resources/authority-boundaries.md

@@ -0,0 +1,15 @@
+# Authority Boundaries
+
+- Inspection reports repository evidence. It proves no artifact bytes.
+- Verification validates the sealed proof object's integrity, owner, namespace,
+  and continuity through the SDK verifier.
+- Publication appends an authenticated projection; it does not create ownership
+  or settlement by implication.
+- Settlement requires the implemented settlement primitive and appropriate
+  delegated or identity-proof authority.
+- Proof creation requires a real authenticated Receiz ID and native Record
+  before Seal continuity.
+
+When authority is unavailable, return
+`blocked_missing_capability_or_authority`. Never synthesize a Receiz ID, owner,
+namespace, prior head, scope, token, proof ID, verification, or settlement.

package/receiz-app-builder-skill/resources/generated-file-repair.md

@@ -0,0 +1,10 @@
+# Generated-File Repair
+
+Receiz-owned generated files carry `@receiz-generated` or the
+`receiz.generated-files.v1` manifest. Preview regeneration, compare the digest,
+and request confirmation before writing.
+
+Automatic edits are limited to generated files, approved `package.json` fields,
+and explicit generated blocks. Unmarked source becomes a manual action. Preserve
+all unrelated code. Reject traversal, symlink escape, stale previews, and content
+whose digest changed after review.

package/receiz-app-builder-skill/resources/upgrade-rules.md

@@ -0,0 +1,11 @@
+# Upgrade Rules
+
+Compare the repository, contract, installed SDK/MCP/AI-skills versions, and
+target SDK version. Keep findings deterministic and version-aware.
+
+- Preserve valid historical proof objects.
+- Never rewrite witnessed history.
+- Append missing truth.
+- Rebuild incorrect projections from stronger verified truth.
+- Align package versions and reject published `workspace:` dependency ranges.
+- Re-run tarball installation and conformance after upgrades.

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

@@ -0,0 +1,16 @@
+# App Contract Workflow
+
+| Need | Read-only action | Confirmed mutation |
+|---|---|---|
+| New app | `receiz_app_contract_create`, `receiz_app_plan` | `receiz_app_apply` |
+| Existing repository | `receiz_project_inspect`, `receiz_app_plan` | Apply the confirmed preview |
+| 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 |
+
+After every mutation, run the returned verification commands and reinspect.
+The same repository must produce zero changes on the second run.
+
+Do not substitute inspection for verification, publication for settlement, or a
+successful write for proof admission.

package/receiz-builder-skill/SKILL.md

@@ -12,6 +12,7 @@ Build Receiz apps from proof objects, durable public projections, proof memory,
 - Use for no-db storefronts, product pages, marketplaces, pack opening apps, profile vaults, proof pages, claim flows, QR entry flows, custom domains, subdomains, and template apps.
 - Use when generating app code that imports `@receiz/sdk` or `@receiz/sdk/react`.
 - Use when an AI must choose SDK rails for public store, app state, checkout, media, identity, wallet, sports, or offline queues.
+- For contract-driven repository integration or upgrades, use `receiz-app-builder-skill` first and use this skill for the resulting application surfaces.
 
 ## When Not To Use This Skill
 

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

@@ -1,5 +1,20 @@
 # MCP Tool Map
 
+## v104 Application Compiler
+
+| Need | Tool | Mutation |
+|---|---|---|
+| Inspect repository | `receiz_project_inspect` | Read-only |
+| Propose contract | `receiz_app_contract_create` | Read-only |
+| Compile plan | `receiz_app_plan` | Read-only |
+| Preview/apply | `receiz_app_apply` | Exact digest confirmation required |
+| Check conformance | `receiz_app_check` | Read-only |
+| Plan upgrade | `receiz_app_upgrade` | Read-only |
+| Explain finding | `receiz_app_explain` | Read-only |
+
+Repository inspection is not verification. These tools never supply an artifact
+verification verdict or proof authority.
+
 Source: `packages/receiz-mcp-server/src/index.ts`.
 
 ## Diagnostics And Setup

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

@@ -1,5 +1,10 @@
 # SDK Reference For Proof Work
 
+The v104 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.
+
 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

package/receiz-skill-bundle/resources/skill-routing.md

@@ -2,13 +2,14 @@
 
 ## Route Order
 
-1. If an object must be verified, start with `receiz-proof-skill`.
-2. If local files or airplane-mode proof are involved, use `receiz-offline-verifier-skill`.
-3. If MCP tools or delegated access are involved, use `receiz-mcp-agent-skill`.
-4. If code or app surfaces are being generated, use `receiz-builder-skill`.
-5. If product, storefront, order, receipt, certificate, note, or checkout boundaries appear, use `receiz-commerce-skill`.
-6. If sports cards, card memory, Pack Derby, rarity, MLB proof language, or live events appear, use `receiz-sports-card-skill`.
-7. If QR, venue, affiliate, staff script, or physical activation appears, use `receiz-distribution-skill`.
+1. If a repository is being started, integrated, upgraded, diagnosed, or repaired, use `receiz-app-builder-skill`.
+2. If an object must be verified, start with `receiz-proof-skill`.
+3. If local files or airplane-mode proof are involved, use `receiz-offline-verifier-skill`.
+4. If MCP tools or delegated access are involved, use `receiz-mcp-agent-skill`.
+5. If code or app surfaces are being generated, use `receiz-builder-skill`.
+6. If product, storefront, order, receipt, certificate, note, or checkout boundaries appear, use `receiz-commerce-skill`.
+7. If sports cards, card memory, Pack Derby, rarity, MLB proof language, or live events appear, use `receiz-sports-card-skill`.
+8. If QR, venue, affiliate, staff script, or physical activation appears, use `receiz-distribution-skill`.
 
 ## Multi-Skill Order