xmpp stack decision

pm/tasks.org

@@ -1,5 +1,6 @@
 #+title: Task Log
 #+updated: [2026-04-14 Tue 13:26]
+#+startup: overview
 
 * [X] 0.1.0: Define v0 bridge contract (estimate 1 commit)
 Write a one-page spec for the first bridge: one XMPP MUC room <-> one Zulip stream/topic, append-only relay, no edits/reactions/history sync.
@@ -49,7 +50,7 @@ Specify the minimal message metadata the bridge must preserve and the exact loop
 - pm note: this is the real core of v0; if this is fuzzy the bridge will thrash.
 
 ** evidence
-- commit:
+- commit: c72b1d8
 - tests: n/a (design note only)
 - datetime: [2026-04-14 Tue 14:40]
 - artifact: pm/0.1.1-relay-envelope-and-loop-rules.org
@@ -83,7 +84,7 @@ Confirm what kind of bot/client should be used on the Zulip side and document an
 ** notes
 - Keep this empirical; document only constraints that affect v0.
 
-* [ ] 0.1.3: Survey XMPP MUC event model + library options (estimate 1 commit)
+* [X] 0.1.3: Survey XMPP MUC event model + library options (estimate 1 commit)
 Pick the first XMPP client library/runtime and document the exact events needed for room relay.
 
 ** Acceptance Criteria
@@ -102,8 +103,9 @@ Pick the first XMPP client library/runtime and document the exact events needed
 
 ** evidence
 - commit:
-- tests:
-- datetime:
+- 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
 
 ** notes
 - Goal is “good enough to prototype,” not perfect XMPP abstraction.