0.1.2 zulip api constraints

This commit is contained in:
ben
2026-04-14 16:04:16 -04:00
parent e706294cc5
commit cbe891c973
2 changed files with 46 additions and 4 deletions

View File

@@ -58,7 +58,7 @@ Specify the minimal message metadata the bridge must preserve and the exact loop
** notes
- Prefer boring explicit metadata over clever heuristics.
* [ ] 0.1.2: Survey Zulip bot constraints + auth model (estimate 1 commit)
* [X] 0.1.2: Survey Zulip bot constraints + auth model (estimate 1 commit)
Confirm what kind of bot/client should be used on the Zulip side and document any constraints that change architecture.
** Acceptance Criteria
@@ -78,8 +78,9 @@ Confirm what kind of bot/client should be used on the Zulip side and document an
** evidence
- commit:
- tests:
- datetime:
- tests: n/a (design note only)
- datetime: [2026-04-14 Tue 15:25]
- artifact: pm/zulip-bot-constraints.org
** notes
- Keep this empirical; document only constraints that affect v0.
@@ -102,7 +103,7 @@ Pick the first XMPP client library/runtime and document the exact events needed
- pm note: avoid solving the Emacs client here; this is just relay transport.
** evidence
- commit:
- commit: e706294
- tests: n/a (design note only)
- datetime: [2026-04-14 Tue 15:05]
- artifact: pm/0.1.3-xmpp-event-model-and-library-choice.org