docs(agents): update session close — sync endpoint + trailing slash fix

Replace manual make fix-consistency instruction with direct curl call to
POST /repos/repo-registry/sync. Fix trailing slash on tasks/{id}/ example.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-04-26 15:13:18 +02:00
parent 9051fe644a
commit 35274baac1

View File

@@ -68,7 +68,7 @@ curl -s -X PATCH "http://127.0.0.1:8000/messages/<message_id>/read" \
### Update task status (after workstreams are synced)
```bash
curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>/" \
curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
-H "Content-Type: application/json" \
-d '{"status": "in_progress"}'
```
@@ -89,8 +89,15 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>/" \
**Close:**
1. Update task statuses in workplan files to match progress
2. Call `POST /progress/` with a summary of what was done
3. If workplan files changed, note that `fix-consistency` should be run from
the custodian machine: `cd ~/the-custodian/state-hub && make fix-consistency REPO=repo-registry`
3. If workplan files changed, sync them to the hub DB:
```bash
curl -s -X POST "http://127.0.0.1:8000/repos/repo-registry/sync" | python3 -m json.tool
```
This runs the ADR-001 consistency check with `--fix` and returns a JSON report.
A `"result": "warn"` with only C-17 is normal (unpushed commits); no action needed.
A `"result": "fail"` means file/DB drift that could not be auto-fixed — read the issues list.
---