Artifact 6dfffd6e2115652b27f7f9c81f1acf936cc78e241fb831b5e2dddd411a2b6afa:
- File
cmd/quarry/main.go
-
2026-08-16 05:04:31
— part of check-in
[37f62c9a82]
on branch trunk
— notify: fire mention and activity triggers to the notify companion (0001 §5)
internal/notify: a Novu-compatible POST /v1/events/trigger client (quarry triggers, notify owns delivery). chat.post parses @mentions and fires quarry-mention per handle; wiki/ticket write ops fire quarry-activity to a repo:<name> topic. All best-effort — a notify outage never fails the user action — with idempotency keys so replays dedup. --notify enables it (disabled by default). Verified live: mention and activity triggers POSTed with the right Novu shape. (user: dmestas, size: 14960) [annotate] [blame] [check-ins using]
-
2026-08-16 09:57:16
— part of check-in
[3d68e9b401]
on branch trunk
— chat: drop DAG archival — keep chat ephemeral like Fossil
Reversed 0001 §5's 'durability is the DAG': minting chat into synced, content-addressed forum artifacts writes casual chatter permanently into the DAG, the opposite of Fossil's deliberate chat ephemerality (server-local, auto-purged, never synced). Chat stays live + the 7-day JetStream window; durable archival becomes a future quarry-specific/S3 concern, not near-term. Removes internal/chatarchive, its wiring and flags, events.KV, and the zitcli forum/technote wrappers it used (they return with v2 web-authored forum). Chat itself is unchanged. (user: dmestas, size: 14960) [annotate] [blame] [check-ins using]
-
2026-08-16 05:04:31
— part of check-in
[37f62c9a82]
on branch trunk
— notify: fire mention and activity triggers to the notify companion (0001 §5)