feat: coord API — no-auth, DB softfail 503, agent tracking protocol
- coord routers: removed JWT auth requirement (internal-only endpoints) - error_handler: SQLAlchemy OperationalError/DisconnectionError → 503 with Retry-After: 30 header instead of 500 - /health: live DB probe (SELECT 1) instead of static response - CLAUDE.md: "Live State Tracking" section with full agent protocol for all projects — session start, lock claim/release, component state updates, softfail + local queue catch-up - COORDINATION_PROTOCOL.md: softfail/catch-up section + server-side 503 behavior documented Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -252,19 +252,7 @@ Full protocol reference: `.claude/COORDINATION_PROTOCOL.md`
|
||||
|
||||
### Cross-Session Messages (MANDATORY)
|
||||
|
||||
At session start and after every `/sync`, check for unread messages:
|
||||
```
|
||||
GET http://172.16.3.30:8001/api/coord/messages?to_session=<this-session>&unread_only=true
|
||||
```
|
||||
If unread messages exist, display each one prominently before any other work:
|
||||
```
|
||||
============================================================
|
||||
MESSAGE FROM <from_session> — <subject>
|
||||
============================================================
|
||||
<body>
|
||||
============================================================
|
||||
```
|
||||
Mark as read via `PUT /api/coord/messages/{id}/read` after displaying.
|
||||
See the **Session Start Protocol** in "Live State Tracking" above. Messages must be displayed and marked read before any other work.
|
||||
|
||||
Also scan session logs pulled during `/sync` for legacy `## Note for <user>` sections (transitional — older sessions still use markdown).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user