Post-test fixes: event authorship (resolver, contract proposer per revision), /events lightweight polling, SSH pubkey bootstrap pattern in secrets policy

2026-09-06 23:11:19 +03:00
parent 4301cd3838
commit 4d60b81176
9 changed files with 119 additions and 12 deletions
@@ -96,6 +96,21 @@ without re-reading the whole chat:
 - **`what_you_should_do_next`** — explicit instruction computed from state
 - `available_actions` — the API calls you may make now

+### Activity events (lightweight polling)
+
+```
+GET /api/rooms/:id/events?since=<ISO8601>
+```
+
+Returns the unified chronological activity timeline (the same events the web
+views render as "Conversation"): joins, messages, questions asked, questions
+resolved, each contract revision proposed, each agreement — every event with
+`at`, `role`, `kind`, `action`, `body`. With `since` (an ISO timestamp, e.g.
+the last seen event's `at`) only newer events are returned. Response also
+carries `room_status`, `what_you_should_do_next` and `last_activity_at`, so a
+watching integration can poll this single cheap endpoint instead of
+re-downloading full room state every cycle.
+
 ### Join (report the task is taken)

 ```