External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: reflow hard-wrapped prose to one line per paragraph

Browse Source 
Markdown and editors soft-wrap on their own, so the manual ~75-char line
breaks across the docs added nothing but noise. Join wrapped prose, list
items, and paragraphs into single lines across 67 docs — README, CLAUDE.md,
deployment, usage, the RAG knowledge base, and the agent role prompts.
Whitespace-only: code fences, tables, and blockquote alerts are byte-identical
and the change is token-verified (no content altered). Applied with a
deterministic reflow tool (committed separately).

Also lands two doc edits that were awaiting commit: the measured under-load
resource numbers in usage.md and the pr_reviewer additions to the
org-structure RAG doc.
This commit is contained in:
Renn F
2026-06-16 23:18:55 +02:00
parent 640a964b88
commit f48106cbb6
67 changed files with 504 additions and 1593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rag/tools/journal-tools.md
+4 -10
View File
@@ -1,8 +1,6 @@
# Journal Tools
There is **no** `roboco_journal_*` tool. Journaling is a single content
tool on the `roboco-do` MCP server: `note`. The `scope` argument selects
the entry kind; structured fields are filled per scope.
There is **no** `roboco_journal_*` tool. Journaling is a single content tool on the `roboco-do` MCP server: `note`. The `scope` argument selects the entry kind; structured fields are filled per scope.
```python
note(
@@ -24,8 +22,7 @@ note(
)
```
`text` is always required. Missing narrative fields default to a visible
placeholder rather than being rejected — the note is always recorded.
`text` is always required. Missing narrative fields default to a visible placeholder rather than being rejected — the note is always recorded.
## Scopes
@@ -91,8 +88,7 @@ note(
## Reflection
Use a `reflect`-scope note before submitting to QA — it gives QA the
"why" behind the diff.
Use a `reflect`-scope note before submitting to QA — it gives QA the "why" behind the diff.
```python
note(
@@ -108,9 +104,7 @@ note(
## Reading Journals
Journals are written by `note` and surface through the knowledge base —
there is no separate journal-read tool. Search past notes (yours and
your team's, where permitted) via the `roboco-optimal` MCP server:
Journals are written by `note` and surface through the knowledge base — there is no separate journal-read tool. Search past notes (yours and your team's, where permitted) via the `roboco-optimal` MCP server:
```python
# Semantic search over indexed notes/decisions/learnings