@farthershore/product 0.2.0 → 0.2.1

package/README.md

@@ -2,9 +2,11 @@
 
 Product-as-Code SDK for Farther Shore. Builder repos use this package from
 `product/product.config.ts` to declare product contracts in TypeScript. Builders
-author and export a `Business`; the Farther Shore GitHub bot compiles that
-program to backend-owned IR, validates it, and publishes through Core when repo
-changes land.
+author and export a `Business`; Farther Shore compiles that program to
+backend-owned IR, validates it, and applies it through Core. Every product is
+created with a GitHub repo that contains the editable `frontend/` starter and
+the Product SDK entrypoint; connecting GitHub is a product-creation
+precondition.
 
 ## Install
 
@@ -31,10 +33,11 @@ frontend/
   ...
 ```
 
-`product/` is authored Product SDK code. `frontend/` is the generated editable
-frontend app and is built by the frontend pipeline only. Runtime state and
-compiled IR are not checked into the builder repo; Farther Shore stores them in
-Core.
+`product/` is authored Product SDK code and may be split into any imported files
+the builder wants. `frontend/` is the generated editable starter app and is built
+by the frontend pipeline only. Runtime state, accepted specs, compilation
+records, deployment runs, and compiled IR are not checked into the builder repo;
+Farther Shore stores them in Core.
 
 ## Example
 
@@ -80,10 +83,10 @@ export const configurePlans: ProductModule = (product) => {
 };
 ```
 
-## Bot build
+## Lifecycle apply paths
 
-Normal product repos do not call platform release or IR APIs. The GitHub bot
-owns that workflow:
+Generated product repos use GitHub as the required automation and frontend
+workspace:
 
 1. Loads `product/product.config.ts`.
 2. Requires the default export to be the `Business` returned by
@@ -93,9 +96,15 @@ owns that workflow:
 4. Validates the result against the deployed platform contract.
 5. Publishes the accepted release through Core so edge artifacts propagate.
 
-The bundled `farthershore-manifest-build` binary is bot/build-runner plumbing.
-Run it locally only when debugging the automation itself; it is not part of the
-normal builder workflow.
+The same IR can also be applied to an already repo-backed product through
+trusted Core APIs, for example `farthershore build --apply <product>`. That path
+is useful for local validation/apply loops, but it is not a replacement for the
+product repo. The repo remains the required frontend customization workspace
+because `frontend/` is where the starter UI and all custom React code live.
+
+The bundled `farthershore-manifest-build` binary is shared by the bot,
+build-runner, and CLI. It emits the deterministic Manifest IR envelope that Core
+accepts; Core, not the user repo, remains the lifecycle authority.
 
 ## Public API
 

package/dist/bin.js

@@ -2360,7 +2360,7 @@ function hashIr(ir) {
 }
 
 // src/version.ts
-var SDK_VERSION = true ? "0.2.0" : "0.0.0-dev";
+var SDK_VERSION = true ? "0.2.1" : "0.0.0-dev";
 
 // src/business.ts
 var BUSINESS_BRAND = Symbol.for("farthershore.product.business");

package/dist/index.js

@@ -2355,7 +2355,7 @@ function canonicalIrJson(ir) {
 }
 
 // src/version.ts
-var SDK_VERSION = true ? "0.2.0" : "0.0.0-dev";
+var SDK_VERSION = true ? "0.2.1" : "0.0.0-dev";
 
 // src/business.ts
 var BUSINESS_BRAND = Symbol.for("farthershore.product.business");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@farthershore/product",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Farther Shore product-as-code SDK — declare your business in TypeScript",
   "type": "module",
   "main": "./dist/index.js",