fix: rev fallback asks for multi-line markdown reply bodies
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
+3
-2
@@ -30,8 +30,9 @@
|
||||
`https://rev.n62.casa/review?dir=<url-encoded worktree>&base=<base>`, while
|
||||
the API to call is `http://localhost:7373`;
|
||||
long-poll `GET /api/comments?dir=&since=&wait=1`, reply in-thread via
|
||||
`POST /api/comments` with author `"agent"` + `parentId`, never mark
|
||||
threads resolved.
|
||||
`POST /api/comments` with author `"agent"` + `parentId` and a real
|
||||
multi-line markdown body (pipe a heredoc through `jq -Rs`, never a
|
||||
body inlined on one line), never mark threads resolved.
|
||||
|
||||
## Crit reviews (plans, live pages, HTML files — code diffs go to rev)
|
||||
- **`crit live` / `crit preview` write comments to a local review FILE, not an API** — there is NO notification and `crit fetch` does NOT apply (it needs a prior `crit share`). `/api/comments` on the daemon is the WRONG place (stays `[]`). If I launched the crit server myself, I must poll the review file myself.
|
||||
|
||||
Reference in New Issue
Block a user