added basic envelope data model and message handling

pm/tasks.org

@@ -1,9 +1,7 @@
 #+title: Task Log
 #+updated: [2026-04-14 Tue 13:26]
 
-Use the template below, which should be a top-level org-mode header.
-
-* [x] 0.1.0: Define v0 bridge contract (estimate 1 commit)
+* [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.
 keep scope painfully small so transport bugs are obvious.
 my preference is for python-based systems.
@@ -22,7 +20,7 @@ my preference is for python-based systems.
    - trusted private deployment
 
 ** evidence
-- commit:
+- commit: 5ad2b6b
 - tests: n/a (design note only)
 - datetime: [2026-04-14 Tue 14:28]
 - artifact: pm/0.1.0-v0-bridge-contract.org
@@ -30,7 +28,7 @@ my preference is for python-based systems.
 ** notes
 - This is the boundary-setting task; everything else depends on it.
 
-* [ ] 0.1.1: Define canonical relay envelope + anti-loop rules (estimate 1 commit)
+* [X] 0.1.1: Define canonical relay envelope + anti-loop rules (estimate 1 commit)
 Specify the minimal message metadata the bridge must preserve and the exact loop-prevention mechanism.
 
 ** Acceptance Criteria
@@ -52,8 +50,9 @@ Specify the minimal message metadata the bridge must preserve and the exact loop
 
 ** evidence
 - commit:
-- tests:
-- datetime:
+- tests: n/a (design note only)
+- datetime: [2026-04-14 Tue 14:40]
+- artifact: pm/0.1.1-relay-envelope-and-loop-rules.org
 
 ** notes
 - Prefer boring explicit metadata over clever heuristics.