@fullwell/fullwell 1.1.5 → 1.1.6
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/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,10 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
## 1.1.6 - 2026-07-22
|
|
6
|
+
|
|
7
|
+
- Commit confirmed guided onboarding drafts with up to 10,000 evidence records and 10,000 items in one request of at most 16 MiB; never split a within-limit draft into intermediate Fullwell writes.
|
|
8
|
+
|
|
5
9
|
## 1.1.5 - 2026-07-21
|
|
6
10
|
|
|
7
11
|
- Require the authorized browser audit to open every qualifying grocery order detail, expand complete item lists, and report hidden-item limitations instead of trusting order-history summaries.
|
package/install-metadata.json
CHANGED
package/package.json
CHANGED
|
@@ -33,7 +33,7 @@ The only canonical household read and mutation boundary is the remote `household
|
|
|
33
33
|
| `hfj_get_item` | Read a complete item, evidence summaries, blob revision, and HEAD. | Read only. |
|
|
34
34
|
| `hfj_append_evidence` | Append one to 100 immutable evidence records. | `expected_head`, `idempotency_key`; migration ID when applicable. |
|
|
35
35
|
| `hfj_commit_change_set` | Commit up to 50 agent-authored item, correction, report, or index changes. | `expected_head`, per-item blob revisions, evidence IDs, `idempotency_key`. |
|
|
36
|
-
| `hfj_commit_onboarding` | Atomically save a confirmed snack-and-recipe draft,
|
|
36
|
+
| `hfj_commit_onboarding` | Atomically save a confirmed snack-and-recipe draft with up to 10,000 evidence records and 10,000 items in a complete MCP request of at most 16 MiB. | Explicit final confirmation, snapshot `expected_head`, section and item revisions, `idempotency_key`. |
|
|
37
37
|
| `hfj_create_collection` | Create a reviewed private collection and resolved snapshot. | Explicit items/fields, `expected_head`, `idempotency_key`. |
|
|
38
38
|
| `hfj_create_collection_share` | Publish an immutable snapshot for 1, 7, 30, or 90 days. | `idempotency_key`; default 30 days. |
|
|
39
39
|
| `hfj_revoke_collection_share` | Immediately revoke a share. | Explicit confirmation, `idempotency_key`. |
|
|
@@ -31,7 +31,7 @@ The helper protocol is strict. `load` takes `operation`, `user_id`, `household_i
|
|
|
31
31
|
5. After every user answer, completed order detail, collected recipe occurrence, section skip, or other meaningful progress, send the helper a `save` request containing the exact snapshot binding, the last returned local draft revision, and the complete bounded working draft. Retain source scope, completed-source cursors, typed evidence, semantic decisions, profile edits, reports, expected item revisions, section outcomes, and the stable final idempotency key. Keep only the information needed to resume; never store credentials, cookies, tokens, browser state, screenshots, raw HTML, or raw page captures. If `DRAFT_CONFLICT` occurs, reload and do not overwrite another conversation's progress.
|
|
32
32
|
6. If the user naturally declines the current section, record a draft `skip` outcome with its snapshot revision and exactly one reason: `no_sources` when there are no applicable sources, `not_now` when they defer or say never mind, or `user_declined` for another refusal. Save the checkpoint, advance to the next section without asking permission, and do not revisit a section skipped in this guided run.
|
|
33
33
|
7. Interpret meaning conversationally; never imitate keyword matching. If the user explicitly stops, cancels, or quits the whole setup, delete the exact current local draft revision and end without a Fullwell write.
|
|
34
|
-
8. Before any write, validate that the draft
|
|
34
|
+
8. Before any write, validate that the draft contains at most 10,000 evidence records and 10,000 items, that the complete MCP request is at most 16 MiB, and that it does not depend on an omitted item when `items_truncated` is true. If exact current items are required, explain why and use the narrow legacy read tools before presenting the confirmation. A draft within both count limits and the byte limit must use the one final onboarding write; never split it or make intermediate writes. If it exceeds either bound, keep the checkpoint and name the exact blocking count or byte limit instead of claiming completion.
|
|
35
35
|
9. Present one concise final summary covering source/profile changes, evidence and item counts, reports, and skipped sections. Ask for explicit confirmation to save it. If the user declines or edits the summary, keep drafting and checkpoint the change without a Fullwell write.
|
|
36
36
|
10. After confirmation, call `hfj_commit_onboarding` exactly once with the snapshot HEAD, the checkpointed stable idempotency key, unique section outcomes, changed profiles, evidence, items, canonical reports, and expected item revisions. Omit unchanged profiles and already-complete sections. A `complete` outcome is valid only when the matching canonical report is included or already exists. Delete the exact local draft revision only after the tool reports success.
|
|
37
37
|
11. On an uncertain result, retain the checkpoint and retry the exact final request with the same idempotency key. On `REVISION_CONFLICT`, reread context, reconstruct the draft against current state, show the changed summary, and confirm again. Never delete the checkpoint or report completion from local state alone after a failed, uncertain, or conflicted write.
|