From 19e617df78b5ff269d19f14b2d684bed265a3015 Mon Sep 17 00:00:00 2001 From: diffwireauto <330573775+diffwireauto@users.noreply.github.com> Date: Mon, 19 Oct 2026 04:28:33 -0400 Subject: [PATCH] docs(#917): grant-terms block in the schema the tool actually parses The first version was invented YAML in an untagged fence. grant.py requires a single fence tagged grant-terms containing JSON with keys epic_chain, chain, verification, merge, and optionally flash/expires_after_hours. epic_chain is a list of distinct ISSUE NUMBERS, so the Epics had to exist first: 919 (A, isolate offload), 920 (B, normalise to rows), 921 (C, integration testing). Verified with grant.parse_terms against the file: zero errors. Refs #334 Agent: TealGlen (session c61ce804) Co-Authored-By: Claude Opus 5 --- .../standalone/917-storage-save-path/PLAN.md | 29 +++++++++---------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/docs/initiatives/standalone/917-storage-save-path/PLAN.md b/docs/initiatives/standalone/917-storage-save-path/PLAN.md index 0bc69e20..824c724c 100644 --- a/docs/initiatives/standalone/917-storage-save-path/PLAN.md +++ b/docs/initiatives/standalone/917-storage-save-path/PLAN.md @@ -99,20 +99,19 @@ One, at the end of Epic A, and one at the end of Epic C: run the build on hardwa ## grant-terms +The Epic chain is [#919](https://github.com/OffbandMesh/meshcore-client/issues/919) (A, isolate offload), [#920](https://github.com/OffbandMesh/meshcore-client/issues/920) (B, normalise to rows), [#921](https://github.com/OffbandMesh/meshcore-client/issues/921) (C, integration testing), merged in that order. + +```grant-terms +{ "epic_chain": [919, 920, 921], + "chain": true, + "verification": {"mode": "owner"}, + "merge": {"budget": 3, + "basis": "one merge per Epic in the chain (919, 920, 921); Tasks are commits on the Epic branch, so there is no per-task PR"}, + "expires_after_hours": 72 } ``` -feature: Storage - remove O(history) work from the message save path -epic_chain: - - A: blob read-modify-write off the UI isolate - - B: normalise messages into rows (migration) - - C: Integration Testing (A + B on hardware, both platforms) -verification: - A: benchmark harness shows main-isolate block at or near zero on the real 5.39 MB payload; owner device check on burst - B: per-key message counts identical before and after on a copy of the real 41 MB database; per-message cost flat across history length - C: owner hardware test, Android and Windows -merges: 3 -flash: 0 -reset: null -duration: 72h -``` -**Basis for each budget.** Merges is 3: the chain is three Epics and each merges once, with no per-task PR. Flash is 0: nothing here touches a radio. Reset is null: not applicable. Duration is 72h because Epic B carries a migration test against a 41 MB database, and a grant that outlasts a careful run beats one expiring mid-chain and needing a re-mint. +**Basis for the expiry.** 72 hours because Epic B carries a migration test against a copy of the real 41 MB database, and a grant that outlasts a careful run beats one expiring mid-chain and needing a re-mint. + +**No flash or reset budget.** Nothing in this Feature touches a radio, so both keys are omitted and default to null. + +**Verification is `owner` rather than a command** because two of the three Epics end in a judgement only the owner can make: that the UI no longer freezes under a burst on his device, and that nothing is missing after the migration. A command here would be a check that cannot fail, which the tool flags and which would verify nothing.