@open-tomato/rafa 0.53.0 → 0.54.0

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/dist/PROMPT.md CHANGED
@@ -15,6 +15,13 @@ An `out_of_scope_bugs` entry's `kind` is one of six, a different list from a fin
15
15
  - `docs` applies when the leftover is a documentation fault larger than one stale line, since a single stale doc line goes into `stale_docs` instead.
16
16
  - `machine` applies when the fault lies in this machine or its setup, such as a missing tool or an unreachable service, rather than in the code.
17
17
 
18
+ An out-of-scope entry that is a failing test carries its evidence in `artifact`: bun's `(fail) <describe> > <case>` line as printed, with the test file's header line (`<path>.test.ts:`) above it, and every path in full from the checkout root with its real extension. The file never goes inside the `(fail)` line. For example:
19
+
20
+ ```text
21
+ packages/rafa-pr/src/triage/own-check.test.ts:
22
+ (fail) checkKind > reads a red case as fallout [3.00ms]
23
+ ```
24
+
18
25
  ```rafa:report
19
26
  status: done
20
27
  feedback: |
@@ -46,7 +46,13 @@ with no `packages/` directory and no workspace boundaries to navigate.
46
46
  - **Reproduce of each out-of-scope entry.** Give `reproduce` as one command
47
47
  run from the checkout root whose output or exit code shows the bug, such
48
48
  as `bun test src/x.test.ts` or `grep -n pattern src/y.ts`. Prose only when
49
- no command can show it, and then it names the condition.
49
+ no command can show it, and then it names the condition. A failing test's
50
+ `artifact` quotes bun's `(fail) <describe> > <case>` line as printed, with
51
+ the test file's header line (`<path>.test.ts:`) above it, and every path in
52
+ full from the checkout root with its real extension:
53
+
54
+ packages/rafa-pr/src/triage/own-check.test.ts:
55
+ (fail) checkKind > reads a red case as fallout [3.00ms]
50
56
 
51
57
  ## Verification
52
58
 
@@ -57,6 +57,22 @@ When one matches, add the stretch's case to it:
57
57
  rafa issue comment <n> --body="Seen again in stretch <n>: <the raw line>."
58
58
  ```
59
59
 
60
+ When the config sets `collaborate.rafa` (a project that reports to rafa's
61
+ own board), the gap is filed on that board, not this one. Search and file
62
+ with `--upstream=rafa`, and comment the same way:
63
+
64
+ ```bash
65
+ rafa issue list --upstream=rafa --module=cli-gap --search="<the step in a few words>"
66
+ rafa issue create --upstream=rafa --type=bug --module=cli-gap --action="<the rafa action that came closest, or unknown>" --summary="<the step rafa cannot do yet>" --cause=cli:new-context --reproduce="<the raw line>" --body="<the rafa line that came closest, what it lacks>"
67
+ rafa issue comment <n> --upstream=rafa --body="Seen again in stretch <n>: <the raw line>."
68
+ ```
69
+
70
+ Only a bug is filed upstream: `--type=bug` is the only type it takes. The
71
+ upstream check refuses a run when the config does not set
72
+ `collaborate.rafa`, or when this board's owner differs from the upstream's,
73
+ and a refused line files nothing. A private sibling is named "a private
74
+ sibling repository" in the title and the body, never by its name.
75
+
60
76
  The board is public: no local path, host name, user name or secret in the
61
77
  title or the body.
62
78