Merge pull request #245 from CodeForPhilly/chore/close-slug-refs-2.9

chore(plans): close out slug-references and gitsheets-2.9

Author: themightychris

plans/gitsheets-2.9.md

@@ -1,9 +1,10 @@
 ---
-status: in-progress
+status: done
 depends: [slug-references]
 specs:
   - specs/behaviors/storage.md
   - specs/behaviors/slug-handles.md
+pr: 243
 ---
 
 # Plan: adopt gitsheets 2.9
@@ -48,7 +49,7 @@ follow-up; #307 import-merge runbook.
       (person, project, event, cascade) still show attachments moved;
       buzz regenerateSlug keeps its image (test)
 - [x] `type-check` + `lint` + full suite green
-- [ ] Sandbox and production boot on the release
+- [x] Sandbox and production boot on the release
 
 ## Notes
 
@@ -62,4 +63,6 @@ follow-up; #307 import-merge runbook.
 - The musl core-napi build is in the lockfile. Loading it in the Alpine
   image is verified when the release image runs on sandbox.
 
+- Shipped in v0.9.0; the Alpine image loads core-napi 0.7.0 (sandbox and production booted, 0 restarts).
+
 ## Follow-ups

plans/slug-references.md

@@ -1,5 +1,5 @@
 ---
-status: in-progress
+status: done
 depends: [sheet-contracts]
 specs:
   - specs/principles.md
@@ -92,7 +92,7 @@ Out:
 - [x] Migration: idempotent; refuses to write if any reference doesn't
       resolve; `contracts verify` passes after it on every branch
 - [x] `type-check` + `lint` + full suite green
-- [ ] `published` migrated and adopted in lockstep with the release;
+- [x] `published` migrated and adopted in lockstep with the release;
       sandbox and production boot
 
 ## Risks / unknowns
@@ -117,8 +117,8 @@ Out:
   that no longer exist (it protected no one); it also deletes the pruned
   person's RSVPs. Account-claim merge re-points the requester's RSVPs.
   scrub-data pseudonymizes every person-slug reference consistently.
-- Remaining before `done`: migrate and adopt on `published` in lockstep
-  with the release, then boot sandbox and production.
+
+- `published` migrated (1,450 records) and adopted v2 in lockstep with v0.9.0 (`13ac63b`); sandbox and production booted, and memberships resolve both ways.
 
 ## Follow-ups
 

plans/slug-rename-attachments.md

@@ -1,5 +1,5 @@
 ---
-status: in-progress
+status: done
 depends: [slug-history-config]
 specs:
   - specs/behaviors/slug-handles.md
@@ -51,7 +51,7 @@ later commit once the move API ships.
 - [x] Test: rename a person with an avatar; the avatar is served at the new
       key and `avatarKey` matches
 - [x] Test: rename a project; no attachments are orphaned
-- [ ] (after upstream) no delete-then-upsert left in the rename paths
+- [x] (after upstream) no delete-then-upsert left in the rename paths
 - [x] `type-check` + `lint` + full api suite green
 
 ## Risks / unknowns
@@ -65,4 +65,8 @@ later commit once the move API ships.
   `featuredImageKey` are rewritten. What's left is swapping this for a native
   gitsheets move once one exists (see `awaits`).
 
+- Finished by [`gitsheets-2.9`](gitsheets-2.9.md) (PR #243): gitsheets#302
+  shipped native rename-on-upsert that moves attachments, and every rename
+  path now uses it via `upsertMoved`. The take/restore interim is removed.
+
 ## Follow-ups