@open-tomato/rafa 0.24.0 → 0.26.0

package/README.md

@@ -279,6 +279,23 @@ project's file outranks the same one in yours. `rafa init` writes both
 with every setting commented out at its default, so uncomment a line,
 with its section line, to change it.
 
+### `effort`
+
+One setting says how long a command waits for another rafa process that
+is writing the effort store before it gives up with `SQLITE_BUSY`.
+
+| Key | Default | What it sets |
+|---|---|---|
+| `effort.busyTimeoutMs` | `5000` | the wait in milliseconds, a whole number from 1 to 60000 |
+
+There is no unlimited wait, since a lock wait with no end can hang a
+loop; `0`, a fraction and a quoted `"5000"` are refused.
+
+```yaml
+effort:
+  busyTimeoutMs: 10000
+```
+
 ### `cleanup`
 
 Three settings shape what `rafa cleanup` lists.

package/dist/bundled/skills/dev-planner/SKILL.md

@@ -503,6 +503,17 @@ The report rules in this skill restate `src/report/parse.ts`, which is the autho
 
 ---
 
+## Plans that change the effort store
+
+When the spec adds or changes anything in `.rafa/effort/`:
+
+- Give each migration its own task, naming its id and whether it is additive or which side it breaks. Never write a schema version number or an array position.
+- A task that runs the branch's store code over real data first runs `bun src/rafa.ts effort copy --to=.rafa/scratch/<stub>-effort`, and runs each command with `RAFA_EFFORT_DIR=<absolute path of that dir>` on the same line. The close-out task removes the copy.
+- Work that must land in the live store goes under "Operator steps after the plan merges [human]": `rafa self-update`, then the command.
+- PREREQUISITES carries `- [ ] The installed rafa can read and write the live store: \`rafa effort schema --check\`` under an `[auto]` heading.
+
+---
+
 ## Command-development rule: Claude session declaration
 
 When planning work on rafa commands: every command that can start a Claude