@ouro.bot/cli 0.1.0-alpha.1 → 0.1.0-alpha.10

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.
Files changed (46) hide show
  1. package/AdoptionSpecialist.ouro/psyche/SOUL.md +3 -1
  2. package/dist/heart/config.js +34 -0
  3. package/dist/heart/core.js +41 -2
  4. package/dist/heart/daemon/daemon-cli.js +280 -22
  5. package/dist/heart/daemon/daemon.js +3 -0
  6. package/dist/heart/daemon/hatch-animation.js +28 -0
  7. package/dist/heart/daemon/hatch-flow.js +3 -1
  8. package/dist/heart/daemon/hatch-specialist.js +6 -1
  9. package/dist/heart/daemon/log-tailer.js +146 -0
  10. package/dist/heart/daemon/os-cron.js +260 -0
  11. package/dist/heart/daemon/ouro-bot-entry.js +0 -0
  12. package/dist/heart/daemon/ouro-bot-wrapper.js +4 -3
  13. package/dist/heart/daemon/ouro-entry.js +0 -0
  14. package/dist/heart/daemon/process-manager.js +18 -1
  15. package/dist/heart/daemon/runtime-logging.js +9 -5
  16. package/dist/heart/daemon/specialist-orchestrator.js +161 -0
  17. package/dist/heart/daemon/specialist-prompt.js +56 -0
  18. package/dist/heart/daemon/specialist-session.js +150 -0
  19. package/dist/heart/daemon/specialist-tools.js +132 -0
  20. package/dist/heart/daemon/task-scheduler.js +4 -1
  21. package/dist/heart/identity.js +28 -3
  22. package/dist/heart/providers/anthropic.js +3 -0
  23. package/dist/heart/streaming.js +3 -0
  24. package/dist/mind/associative-recall.js +23 -2
  25. package/dist/mind/context.js +85 -1
  26. package/dist/mind/friends/channel.js +8 -0
  27. package/dist/mind/friends/types.js +1 -1
  28. package/dist/mind/memory.js +62 -0
  29. package/dist/mind/pending.js +93 -0
  30. package/dist/mind/prompt-refresh.js +20 -0
  31. package/dist/mind/prompt.js +101 -0
  32. package/dist/nerves/coverage/file-completeness.js +14 -4
  33. package/dist/repertoire/tools-base.js +92 -0
  34. package/dist/repertoire/tools.js +3 -3
  35. package/dist/senses/bluebubbles-client.js +279 -0
  36. package/dist/senses/bluebubbles-entry.js +11 -0
  37. package/dist/senses/bluebubbles-model.js +253 -0
  38. package/dist/senses/bluebubbles-mutation-log.js +76 -0
  39. package/dist/senses/bluebubbles.js +332 -0
  40. package/dist/senses/cli.js +89 -8
  41. package/dist/senses/inner-dialog.js +15 -0
  42. package/dist/senses/session-lock.js +119 -0
  43. package/dist/senses/teams.js +1 -0
  44. package/package.json +4 -3
  45. package/subagents/README.md +3 -1
  46. package/subagents/work-merger.md +33 -2
package/subagents/README.md CHANGED
@@ -22,12 +22,14 @@ For tools that support skills but not Claude sub-agents, install these as skills
22
22
  ```bash
23
23
  mkdir -p ~/.codex/skills/work-planner ~/.codex/skills/work-doer ~/.codex/skills/work-merger
24
24
 
25
- # Recommended: hard-link to keep one source of truth and avoid stale copies
25
+ # Hard-link to keep one source of truth
26
26
  ln -f "$(pwd)/subagents/work-planner.md" ~/.codex/skills/work-planner/SKILL.md
27
27
  ln -f "$(pwd)/subagents/work-doer.md" ~/.codex/skills/work-doer/SKILL.md
28
28
  ln -f "$(pwd)/subagents/work-merger.md" ~/.codex/skills/work-merger/SKILL.md
29
29
  ```
30
30
 
31
+ **Important:** Hard-links break when editors save by replacing the file (new inode). After editing any `subagents/*.md` file, re-run the `ln -f` command for that file to restore the link. You can verify with `stat -f '%i'` — both files should share the same inode.
32
+
31
33
  Optional UI metadata:
32
34
 
33
35
  ```bash
package/subagents/work-merger.md CHANGED
@@ -327,12 +327,43 @@ done
327
327
  ### Step 4: Handle CI result
328
328
 
329
329
  **CI passes:**
330
- - Proceed to Step 5 (merge).
330
+ - Proceed to Step 5 (pre-merge sanity check).
331
331
 
332
332
  **CI fails:**
333
333
  - Proceed to **CI Failure Self-Repair**.
334
334
 
335
- ### Step 5: Merge the PR
335
+ ### Step 5: Pre-merge sanity check
336
+
337
+ Before merging, verify the PR delivers what the planning/doing doc intended. This is a lightweight review, not a full audit.
338
+
339
+ 1. Re-read the doing doc (already available from On Startup)
340
+ 2. Review the PR diff: `gh pr diff "${BRANCH}"`
341
+ 3. Check that:
342
+ - All completion criteria from the doing doc are addressed
343
+ - No unrelated changes slipped in
344
+ - The PR title and body accurately describe what shipped
345
+ 4. Post findings as a PR comment:
346
+
347
+ ```bash
348
+ gh pr comment "${BRANCH}" --body "$(cat <<'REVIEW'
349
+ ## Pre-merge sanity check
350
+
351
+ Checked PR against doing doc: `<doing-doc-path>`
352
+
353
+ - [ ] All completion criteria addressed
354
+ - [ ] No unrelated changes
355
+ - [ ] PR description accurate
356
+
357
+ <any notes or concerns>
358
+
359
+ Proceeding to merge.
360
+ REVIEW
361
+ )"
362
+ ```
363
+
364
+ If the check reveals a genuine gap (missing criteria, wrong files included), fix it before merging. If everything looks good, proceed to Step 6.
365
+
366
+ ### Step 6: Merge the PR
336
367
 
337
368
  ```bash
338
369
  gh pr merge "${BRANCH}" --merge --delete-branch