@open-tomato/rafa 0.44.0 → 0.46.0

package/dist/learning/index.js

@@ -1,17 +1,16 @@
 // @bun
-import {
-  bless,
-  merge,
-  promotable
-} from "../index-nv34ptht.js";
 import {
   CONFIDENCE_MAX,
   CONFIDENCE_MIN,
   GAP,
   SOURCE_STEP,
   actionHash,
+  bless,
+  merge,
+  promotable,
   triggerKey
-} from "../index-hf2k497d.js";
+} from "../index-77ajfffn.js";
+import"../index-z1w83f81.js";
 export {
   triggerKey,
   promotable,

package/dist/plan/index.js

@@ -1,29 +1,30 @@
 // @bun
 import {
+  FINDING_KINDS,
+  FINDING_SIGNALS,
   PLAN_BLOCK_KINDS,
   PLAN_HEADER_FIELDS,
   PROBE_TIMEOUT_MS,
+  RAFA_BLOCK_KINDS,
+  REPORT_STATUSES,
+  isRafaBlockKind,
   loadPlanPrerequisites,
   mergePlanPrerequisites,
   parsePlan,
   parsePrerequisites,
+  parseReport,
   planPrerequisites,
   prerequisitesPathForPlan,
+  readRafaBlocks,
   renderInjection,
   runPreflight,
   runShellProbe
-} from "../index-57mmzkcn.js";
+} from "../index-39kbcw68.js";
+import"../index-2a7nb3an.js";
 import {
-  FINDING_KINDS,
-  FINDING_SIGNALS,
-  INJECT_MODES,
-  RAFA_BLOCK_KINDS,
-  REPORT_STATUSES,
-  isRafaBlockKind,
-  parseReport,
-  readRafaBlocks
-} from "../index-cknayrpc.js";
-import"../index-hf2k497d.js";
+  INJECT_MODES
+} from "../index-ykggr043.js";
+import"../index-z1w83f81.js";
 export {
   runShellProbe,
   runPreflight,

package/dist/plan-prompt.md

@@ -34,7 +34,10 @@ on the `open-tomato/rafa` board.
   test that imports none of its files: test preloads, `bunfig.toml`,
   `tsconfig*.json`, `package.json` or the lockfile, global state or
   environment every test inherits, and a stage's closing cross-module
-  test task.
+  test task. Keep the whole suite and any command outliving one Bash call
+  out of a task's text: `tests=full` is how the runner runs the suite, and
+  a task that needs a long run's output reads the `.output.txt` a `[start]`
+  prerequisite or the runner wrote beside its JUnit file.
 
 * Before planning, review the spec as written, and report that review at the
   END of your final message as a `rafa:spec-review` block carrying
@@ -42,7 +45,9 @@ on the `open-tomato/rafa` board.
   list of gaps for not-ready. Every gap carries `heading`, `what` and
   `blocking: true` or `blocking: false`, and a gap that is NOT blocking also
   carries the `assumption:` you would plan under — one sentence naming the
-  guess, not a restatement of the gap. A gap is blocking when guessing wrong
+  guess, not a restatement of the gap. Write every one of the three values,
+  `heading`, `what` and `assumption`, in double quotes, so that a `: ` or a
+  ` #` inside one stays part of its text. A gap is blocking when guessing wrong
   changes what ships or what is safe; write no plan while one gap is blocking,
   and plan under your stated assumptions when every gap is non-blocking.
   The block is the LAST thing you write: end the final message with it, after
@@ -87,6 +92,10 @@ criteria — **do not execute the plan**.
   it from the plan. An `[auto]` item holds exactly one backticked span, and
   that span is its command, ending the item after `: ` and run as written:
   prove a tool with `<tool> --version`, `<tool> --help` or `which <tool>`.
+  An `[auto]` item only the tasks need carries `[tasks]` after its box and
+  tag, and one only the wrap-up needs carries `[wrap-up]`
+  (`- [ ] [auto] [tasks] ...`); an unmarked item is needed by both. The
+  marker is written bare, never in backticks and never after the command.
 * Do not create or touch any tracker file — the loop derives it from the plan.
 
 ## The effort-store rule for plans that carry migrations