@farthershore/product 0.5.0 → 0.6.1

package/README.md

@@ -25,11 +25,8 @@ product/
   package.json
   product.config.ts
   meters.ts
-  plans/
-    free.ts
-    pro.ts
-  routes/
-    api.ts
+  features.ts
+  plans.ts
 frontend/
   ...
 ```
@@ -45,8 +42,8 @@ Farther Shore stores them in Core.
 ```ts
 import { fs } from "@farthershore/product";
 import { configureMeters } from "./meters.js";
-import { configureCronRoutes } from "./routes/cron.js";
-import { configurePlans } from "./plans/index.js";
+import { configureCronRoutes } from "./features.js";
+import { configurePlans } from "./plans.js";
 
 const product = fs.product("croncloud", {
   origin: "https://app.example.com",
@@ -122,7 +119,7 @@ Route metering is explicit:
 
 - omitted route metering inherits product defaults such as `requests = 1`
 - `reports` declares dynamic meters the upstream may report with
-  `@farthershore/metering`
+  `@farthershore/backend`
 - `costs` declares gateway-known fixed usage values for a route
 - `estimates` overrides reusable meter estimates for admission checks
 - `unmetered: true` clears all inherited and explicit route metering
@@ -173,12 +170,10 @@ accepts; Core, not the user repo, remains the lifecycle authority.
 - `product.use(...modules)` — compose Product SDK modules from any files under
   `product/`.
 - `product.surface(...)` — declare the product surfaces customers interact with
-  (`frontend`, `api`, `docs`, `widget`, `webhook`, `worker`, or `agent`).
+  (`frontend`, `api`, `docs`, `widget`, `webhook`, `worker`, `agent`, or
+  `dashboard`).
 - `product.entitlement(...)` — group capabilities, feature gates, limits, and
   meters into reusable access metadata.
-- `product.offering.plan(...)` — declare a subscription plan through the
-  generalized offering namespace. `product.plan(...)` remains the direct plan
-  helper.
 - `product.meter(...)` — declare billable or enforceable dimensions.
 - `product.requests()` — declare and inherit the platform-managed successful
   request meter.
@@ -188,7 +183,7 @@ accepts; Core, not the user repo, remains the lifecycle authority.
 - `product.capability(...)` — declare capability bundles and plan grants.
 - `product.feature(...)` / `product.api.route(...)` — declare gateway routes,
   static costs, dynamic reports, estimates, and action metadata.
-- `product.policy(...)` — declare policy files in code.
+- `product.policy(...)` — declare policy layers in code.
 - `product.plan(...)` — declare plan pricing, limits, grants, and lifecycle
   behavior.
 - `product.lifecycle.*` — declare migrations.