@open-tomato/rafa 0.37.0 → 0.39.0

package/dist/{index-3mzw3kzh.js → index-sr3kc4mf.js}

@@ -1,7 +1,7 @@
 // @bun
 import {
   describeValue
-} from "./index-fzhd3d4y.js";
+} from "./index-m2ahxjw8.js";
 
 // src/cli/spends.ts
 var SPENDS_GLYPH = "\uD83E\uDE99";

package/dist/index.js

@@ -9,7 +9,7 @@ import {
   report,
   start,
   validateManifest
-} from "./index-35ze56rz.js";
+} from "./index-nwgwxfkt.js";
 import {
   PLAN_BLOCK_KINDS,
   PLAN_HEADER_FIELDS,
@@ -23,7 +23,7 @@ import {
   renderInjection,
   runPreflight,
   runShellProbe
-} from "./index-7bb0fdb7.js";
+} from "./index-g4116t9m.js";
 import {
   CORE_ADAPTER_REGISTRY,
   DISK_FILE_SYSTEM,
@@ -52,7 +52,7 @@ import {
   scopeAt,
   selectEffortStore,
   selfAndAncestors
-} from "./index-1mxv55ec.js";
+} from "./index-1r2b1052.js";
 import {
   CONFIG_DEFAULTS,
   CONFIG_FILE,
@@ -69,11 +69,12 @@ import {
   parseReport,
   readRafaBlocks,
   resolveConfig
-} from "./index-jfas157k.js";
+} from "./index-m0wt4nr1.js";
 import"./index-d6d0942q.js";
-import"./index-k6sd4ym5.js";
-import"./index-3mzw3kzh.js";
+import"./index-eyjq63mx.js";
+import"./index-sr3kc4mf.js";
 import {
+  BOARD_PROJECT_TEMPLATE_DEFAULT,
   BOARD_RELATIONSHIP_MODES,
   CLAUDE_SETTING_SOURCES,
   CONFIG_VERSIONS,
@@ -83,7 +84,7 @@ import {
   RELEASE_AUTO,
   STORE_BACKENDS,
   SYNC_STRATEGIES
-} from "./index-fzhd3d4y.js";
+} from "./index-m2ahxjw8.js";
 import"./index-wp8c28fd.js";
 export {
   validateManifest,
@@ -157,5 +158,6 @@ export {
   CONFIG_FILE,
   CONFIG_DEFAULTS,
   CLAUDE_SETTING_SOURCES,
-  BOARD_RELATIONSHIP_MODES
+  BOARD_RELATIONSHIP_MODES,
+  BOARD_PROJECT_TEMPLATE_DEFAULT
 };

package/dist/plan/index.js

@@ -12,7 +12,7 @@ import {
   renderInjection,
   runPreflight,
   runShellProbe
-} from "../index-7bb0fdb7.js";
+} from "../index-g4116t9m.js";
 import {
   FINDING_KINDS,
   FINDING_SIGNALS,
@@ -21,10 +21,10 @@ import {
   isRafaBlockKind,
   parseReport,
   readRafaBlocks
-} from "../index-jfas157k.js";
+} from "../index-m0wt4nr1.js";
 import {
   INJECT_MODES
-} from "../index-fzhd3d4y.js";
+} from "../index-m2ahxjw8.js";
 import"../index-wp8c28fd.js";
 export {
   runShellProbe,

package/dist/plan-prompt.md

@@ -89,6 +89,33 @@ criteria — **do not execute the plan**.
   prove a tool with `<tool> --version`, `<tool> --help` or `which <tool>`.
 * Do not create or touch any tracker file — the loop derives it from the plan.
 
+## The effort-store rule for plans that carry migrations
+
+A plan task that names a migration by its id (``migration `<id>` `` in the task line)
+is one the loop's installed runtime must be able to read before the task runs. If the
+task changes the store's schema, the loop's own open would fail once the branch code
+runs.
+
+**In a plan that carries an effort-store migration:**
+
+* Every `bun src/rafa.ts` command on a still-to-run task line must carry
+  `RAFA_EFFORT_DIR=<absolute path of the scratch copy>` as the first assignment on
+  the same line. That names the copy made by the command the plan should declare
+  under Prerequisites, `bun src/rafa.ts effort copy --to=.rafa/scratch/<stub>-effort`
+  (spelled unprefixed, as that step makes the copy). Once made, every branch
+  subcommand runs over the copy, and the loop's own store stays unaffected until the
+  installed runtime has brought it forward.
+
+* The PREREQUISITES file (`PREREQUISITES-<stub>.md`) must carry an `[auto]` item
+  probing exactly `rafa effort schema --check`, the probe that holds the plan back
+  until the installed rafa can read the store that branch code will migrate. Write
+  it as: `- [ ] The installed rafa can read and write the live store: \`rafa effort
+  schema --check\`` under an `[auto]` section.
+
+`rafa plan create` checks both rules when a plan carries a migration and refuses the
+plan if either breaks, moving it into `rejected/` so the loop does not pick it up.
+The same checks run in the loop's preflight before any task starts.
+
 {PLAN_FORMAT}
 
 {ROUTING}

package/dist/plans/resolve-conflict-lockfile.md

@@ -19,8 +19,8 @@ This plan resolves a pull request with a `bun.lock` conflict by taking the base'
 
 # Stage: Resolve
 
-- [ ] Merge the base branch into the current branch using `git merge origin/main` {agent=loop-implementer}
-- [ ] Take the base's `bun.lock` with `git checkout origin/main -- bun.lock` {agent=loop-implementer}
+- [ ] Merge the base branch into the current branch using `git merge origin/{BASE}` {agent=loop-implementer}
+- [ ] Take the base's `bun.lock` with `git checkout origin/{BASE} -- bun.lock` {agent=loop-implementer}
 - [ ] Run `bun install` (plain, not `--frozen-lockfile`) to re-anchor dependencies to the merged state {agent=loop-implementer}
 - [ ] Run `bun install --frozen-lockfile` to verify the lockfile is now consistent with the merged manifests {agent=loop-implementer}
 - [ ] Run the gates (`env -u CLAUDECODE bun test`, `bunx tsc --noEmit`, `bunx eslint .`) to verify no other conflicts arose {agent=loop-implementer}

package/dist/plans/resolve-conflict-manifest.md

@@ -19,7 +19,7 @@ This plan resolves a pull request with a `package.json` conflict by merging the
 
 # Stage: Resolve
 
-- [ ] Merge the base branch into the current branch using `git merge origin/main` {agent=loop-implementer}
+- [ ] Merge the base branch into the current branch using `git merge origin/{BASE}` {agent=loop-implementer}
 - [ ] Resolve the `package.json` conflict by keeping both sides' entries and taking the higher version where both sides bumped a dependency {agent=loop-implementer}
 - [ ] Run `bun install` (plain, not `--frozen-lockfile`) to ensure both sides' dependencies are installed and the lockfile is updated {agent=loop-implementer}
 - [ ] Run `bun install --frozen-lockfile` to verify the lockfile is now consistent with the merged manifests {agent=loop-implementer}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-tomato/rafa",
-  "version": "0.37.0",
+  "version": "0.39.0",
   "description": "Alpha. Runs a plan through the ralph loop: one Claude Code session per task, one commit per task, then a pull request and a CI wait.",
   "private": false,
   "publishConfig": {