primcli 1.15.0 → 1.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -68,11 +68,33 @@ primitive domains list
68
68
  primitive functions templates
69
69
  primitive functions init my-fn --template email-reply
70
70
  primitive functions logs --id <function-id>
71
+ primitive memories set thread:latest '{"email_id":"em_123"}'
72
+ primitive memories get thread:latest
71
73
  primitive deliveries replay --id <delivery-id>
72
74
  ```
73
75
 
74
76
  Generated API commands remain available for compatibility and full schema parity, for example `primitive emails:list-emails` and `primitive sending:reply-to-email`.
75
77
 
78
+ ## Primitive Memories
79
+
80
+ Memories are durable JSON key-value records scoped to your org by default. Use
81
+ `--function <function-id>` to read or write the same key under a function scope;
82
+ the value is the function id UUID, not the function name.
83
+
84
+ ```bash
85
+ primitive memories set thread:latest '{"email_id":"em_123"}'
86
+ primitive memories set greeting '"hello"'
87
+ primitive memories get thread:latest
88
+ primitive memories search thread: --metadata-only
89
+ primitive memories delete thread:latest
90
+
91
+ primitive memories set state '{"step":2}' --function <function-id>
92
+ primitive memories get state --function <function-id>
93
+ ```
94
+
95
+ Values must be valid JSON. Strings must be quoted as JSON strings, so use
96
+ `'"hello"'`, not `hello`.
97
+
76
98
  ## Recipient routing
77
99
 
78
100
  Bind a recipient address to a destination so inbound mail resolves to a single