@odla-ai/chapter 0.28.1 → 0.28.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@odla-ai/chapter",
3
- "version": "0.28.1",
3
+ "version": "0.28.2",
4
4
  "description": "A leader/follower foundation for branded membership sites: shared CRM, admin, auth, payments, booking, and explicit record delivery from one defineChapter config.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://odla.ai/docs/packages/chapter",
@@ -50,10 +50,12 @@ runtime and data rollback remain proven.
50
50
  ## Phase 0 — Freeze the operating baseline
51
51
 
52
52
  Use odla PM as the migration's durable coordination state; do not create a
53
- parallel migration diary. If the odla app already exists, begin by listing
54
- doing tasks, open bugs, open goals, and recent decisions for the `appId` from
55
- `odla.config.mjs`. Read the active task, its linked goal, and their comments
56
- before inspecting code.
53
+ parallel migration diary. If the odla app already exists, begin with `pm next`
54
+ plus open bugs and recent decisions for the `appId` from `odla.config.mjs`.
55
+ Read the active task, its linked goal, and their comments before inspecting
56
+ code. If the requested work is not aligned to an open goal, discuss that with
57
+ the human before implementation. Refine and mark the task Ready, then claim its
58
+ reviewed revision atomically before creating the execution worktree.
57
59
 
58
60
  If the app is not registered yet, choose the intended stable `appId`, keep
59
61
  Phase 0/early provisioning evidence in focused commits and checkpoint
@@ -77,9 +77,9 @@ focused branch/commit and checkpoint handoff for the approved brief and rerun
77
77
  the Phase 0 checks when a fresh agent resumes. Immediately after provision
78
78
  registers the app, create PM conformance goals and track tasks, record these
79
79
  product/brand/identity decisions, and backfill the earlier evidence. PM is
80
- authoritative from then on; start every later session by listing doing tasks,
81
- open bugs/goals, and recent decisions for the `appId` in
82
- `odla.config.mjs`. Never put secrets in PM.
80
+ authoritative from then on; start every later session with `pm next`, then read
81
+ open bugs and recent decisions for the `appId` in `odla.config.mjs`. Never put
82
+ secrets in PM.
83
83
 
84
84
  | Decision | Required answer |
85
85
  | --- | --- |