@odla-ai/chapter 0.25.4 → 0.25.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/chapter",
-  "version": "0.25.4",
+  "version": "0.25.5",
   "description": "A leader/follower foundation for branded membership sites: shared CRM, admin, auth, payments, booking, and explicit record delivery from one defineChapter config.",
   "license": "MIT",
   "homepage": "https://odla.ai/docs/packages/chapter",

package/runbooks/adopt-existing.md

@@ -489,6 +489,9 @@ At 390, 768, 1280, and 1440 pixels in every theme, compare:
 - at 1280 and 1440, every unselected collection table uses the full content
   width: no empty detail pane and no wide table squeezed into a narrow rail;
   after selection, both master and detail remain usable;
+- record the CSS-pixel bounding boxes for the accepted outer workspace, master,
+  and detail at desktop widths. Compare those measurements with the frozen
+  baseline; static markup and component identity cannot prove geometry;
 - no clipped labels, card text escape, accidental document scroll, or
   horizontal overflow;
 - loading, empty, error, unauthorized, 404, and reduced-motion states.
@@ -602,6 +605,26 @@ Run the real journey:
 `doctor`, unit tests, build, CLI smoke, a login page, and a human-looking admin
 screen are necessary but not sufficient.
 
+### Close the source-to-deployment loop
+
+A commit, pushed branch, or merged pull request does not change a running
+website. After every change that affects a route, workspace, asset, provider
+binding, or acceptance result:
+
+1. identify the exact reviewed commit and intended deployment target;
+2. build and deploy that commit with the repository's reviewed dev command;
+3. capture the deploy command, direct origin, immutable Worker/deployment
+   version, and source commit in PM;
+4. reload the direct deployed origin and assert distinctive behavior from the
+   acceptance matrix—not merely a shared label or route;
+5. measure the deployed viewport geometry and exercise the affected journey;
+6. leave the bug/task open if the intended commit was not deployed or the live
+   assertion was not observed.
+
+Do not report “fixed”, “ready for handoff”, or a passing phase from source-only
+tests. If CI is expected to deploy a branch or merge automatically, verify the
+actual completed deployment and version rather than assuming the trigger ran.
+
 Before filing a route bug from deployed evidence, prove that the probed
 deployment runs the intended commit/version. Repeat the request against the
 direct candidate origin and the public domain with a unique non-secret query