@open-tomato/rafa 0.14.0 → 0.16.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/README.md +31 -1
- package/dist/cli.js +16158 -12213
- package/dist/describe-wbn759vf.js +13 -0
- package/dist/effort/store/index.js +4 -2
- package/dist/index-1vtd5fr7.js +13296 -0
- package/dist/{index-96pz9023.js → index-6cw1n0qy.js} +56 -394
- package/dist/index-kph6p7rp.js +19506 -0
- package/dist/{index-p96zrptw.js → index-krjzghpz.js} +6 -4
- package/dist/index-n3rw8rhr.js +397 -0
- package/dist/index-p901zs2p.js +124 -0
- package/dist/{index-g9kvby04.js → index-q491ekzm.js} +10 -26
- package/dist/index-qzhpqmfy.js +234 -0
- package/dist/index.js +40 -11643
- package/dist/plan/index.js +5 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -202,6 +202,33 @@ Every command has help at three levels (`rafa --help`,
|
|
|
202
202
|
`rafa loop --help`, `rafa loop start --help`), and
|
|
203
203
|
`rafa describe --output=json` is the same roster for a tool or an agent.
|
|
204
204
|
|
|
205
|
+
## Configuration
|
|
206
|
+
|
|
207
|
+
Settings live in `.rafa/config.yaml` in the project, and in
|
|
208
|
+
`~/.rafa/config.yaml` for every project on the machine; a setting in the
|
|
209
|
+
project's file outranks the same one in yours. `rafa init` writes both
|
|
210
|
+
with every setting commented out at its default, so uncomment a line,
|
|
211
|
+
with its section line, to change it.
|
|
212
|
+
|
|
213
|
+
### `cleanup`
|
|
214
|
+
|
|
215
|
+
Three settings shape what `rafa cleanup` lists.
|
|
216
|
+
|
|
217
|
+
| Key | Default | What it sets |
|
|
218
|
+
|---|---|---|
|
|
219
|
+
| `cleanup.staleDays` | `30` | the age in days past which a branch is listed as Stale |
|
|
220
|
+
| `cleanup.worktreeIdleDays` | `7` | the idle days past which a worktree is listed |
|
|
221
|
+
| `cleanup.keep` | `[]` | glob patterns naming branches that are never listed |
|
|
222
|
+
|
|
223
|
+
Both day counts take a whole number above zero.
|
|
224
|
+
|
|
225
|
+
```yaml
|
|
226
|
+
cleanup:
|
|
227
|
+
staleDays: 30
|
|
228
|
+
worktreeIdleDays: 7
|
|
229
|
+
keep: ["release/*"]
|
|
230
|
+
```
|
|
231
|
+
|
|
205
232
|
## Specs, issues and the roadmap
|
|
206
233
|
|
|
207
234
|
You can plan from a local file and never touch a board. When you want
|
|
@@ -348,7 +375,10 @@ and a line here is ticked by the change that finishes the feature.
|
|
|
348
375
|
already has a plan, a branch or a pull request
|
|
349
376
|
- ✅ `rafa doctor --deep`: what a loop session and its subagents can
|
|
350
377
|
actually reach — settings, `PATH`, providers and the tools its stack needs
|
|
351
|
-
-
|
|
378
|
+
- ✅ Verified and stamped references in specs: each reference the spec
|
|
379
|
+
names is extracted by pattern, verified against its target, and
|
|
380
|
+
fingerprinted so changes are caught when the spec is refreshed
|
|
381
|
+
- ✅ Clean up merged, stale and unpushed branches and idle worktrees
|
|
352
382
|
- ⬜ `rafa status`: everything in one snapshot, and one line about what
|
|
353
383
|
changed since you last looked
|
|
354
384
|
- ⬜ The right skills reach the right task, chosen when the plan is
|