@fml-inc/fml 0.8.6-rc.3 → 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.
- package/.claude-plugin/plugin.json +1 -1
- package/README.md +16 -5
- package/dist/{chunk-5TOOBX7I.js → chunk-4YLSKFDU.js} +1140 -111
- package/dist/{chunk-V2XC7JTB.js → chunk-5JJQWV4G.js} +381 -95
- package/dist/{chunk-YFHZJPTC.js → chunk-6BTC3S7C.js} +4 -2
- package/dist/chunk-F57IFY3K.js +21 -0
- package/dist/{chunk-2DQQXBWM.js → chunk-LPSZCTTJ.js} +37 -1
- package/dist/chunk-ZC2ZXSKC.js +277 -0
- package/dist/cli.js +168 -126
- package/dist/hook-handler.js +214 -22
- package/dist/observer-server.js +108 -22
- package/dist/sync-cycle.js +3 -2
- package/package.json +3 -3
- package/dist/chunk-ORYHJUC7.js +0 -1225
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
|
|
217
|
-
whichever is reached first
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
the
|
|
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`,
|