From 244b59728ef00634f6c32f41f565b908fb1ebcb6 Mon Sep 17 00:00:00 2001 From: Chris Alfano Date: Sat, 16 May 2026 14:27:19 -0400 Subject: [PATCH] chore(plans): clear storage-foundation awaits after gitsheets v1.0.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit gitsheets v1.0 shipped to NPM as 1.0.3 (latest). PR #144 merged upstream 2026-05-16, GitHub tag v1.0.0 cut shortly after, then v1.0.3 published on NPM with the final patch fixes. Per the awaits: convention, resolution is just deleting the entry when the awaited thing happens. The "Assumes gitsheets v1.0 has shipped" Scope prose stays — it has more context than the YAML did. storage-foundation's depends: [test-harness] is the only remaining blocker. Once test-harness lands, storage-foundation is the next plan ready to execute. Co-Authored-By: Claude Opus 4.7 (1M context) --- plans/storage-foundation.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/plans/storage-foundation.md b/plans/storage-foundation.md index 22c6e51..fe7f62e 100644 --- a/plans/storage-foundation.md +++ b/plans/storage-foundation.md @@ -13,8 +13,6 @@ upstream-specs: - gitsheets:specs/behaviors/transactions.md - gitsheets:specs/behaviors/validation.md - gitsheets:specs/behaviors/normalization.md -awaits: - - "JarvusInnovations/gitsheets@v1.0 — consumed via Repository / Sheet / openStore TypeScript API (https://github.com/JarvusInnovations/gitsheets/milestone/1)" issues: [] ---