@fml-inc/fml 0.8.6 → 0.8.7-rc.1

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "fml",
3
- "version": "0.8.6",
3
+ "version": "0.8.7-rc.1",
4
4
  "description": "FML agent tools for Claude Code",
5
5
  "mcpServers": {
6
6
  "fml": {
package/README.md CHANGED
@@ -213,11 +213,22 @@ backlog.
213
213
 
214
214
  The handler-side inbox is a short-lived durability bridge for times when the
215
215
  observer is stopped or unavailable. It is bounded independently from the
216
- SQLite spool: by default it accepts at most 512 MiB or 10,000 delivery files,
217
- whichever is reached first. At a limit it preserves older committed files,
218
- refuses the newest inbox write, and still fails open for the invoking agent; a
219
- running observer can still accept that event directly. `fml status` reports
220
- the active limits and cumulative capacity refusals.
216
+ SQLite spool: by default it accepts at most 512 MiB or 262,144 delivery files,
217
+ whichever is reached first; the entry cap is derived from the byte budget at
218
+ 2 KiB per event, so bytes are the effective bound for any realistic event.
219
+ Raising `FML_HOOK_INBOX_MAX_BYTES` alone re-derives the entry cap. At a limit
220
+ it preserves older committed files, refuses the newest inbox write, and still
221
+ fails open for the invoking agent; a running observer can still accept that
222
+ event directly. `fml status` reports the active limits, cumulative capacity
223
+ refusals, and the subset of refusals that no observer took either, which is
224
+ real loss; `fml start` warns about any such loss recorded since the last
225
+ start.
226
+
227
+ To keep the bridge short, a hook that finds the observer's recorded endpoint
228
+ no longer answering relaunches the observer in the background, at most once
229
+ every ten minutes. An explicit `fml stop` pauses capture entirely and is never
230
+ undone by a hook; a crash, reboot, or upgrade is. A machine where `fml start`
231
+ never ran has no recorded endpoint and gets no daemon.
221
232
 
222
233
  Set `FML_HOOK_INBOX_MAX_BYTES` and `FML_HOOK_INBOX_MAX_ENTRIES` in the coding
223
234
  agent's environment to change these limits. Bytes accept the same `B`, `KiB`,