Skip to content

Commit 86c7d03

Browse files
docs(plans): close out purge-gate-and-private-data
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TGqwPjt3v4eMfiHpPmCKnR
1 parent 4ef9f67 commit 86c7d03

1 file changed

Lines changed: 16 additions & 3 deletions

File tree

‎plans/purge-gate-and-private-data.md‎

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
status: in-progress
2+
status: done
33
depends: [scheduled-spam-purge]
44
specs:
55
- specs/behaviors/person-lifecycle.md
@@ -45,8 +45,8 @@ private store would write the old data back).
4545

4646
## Validation
4747

48-
- [ ] `npm run type-check && npm run lint && npm test` clean.
49-
- [ ] Tests: the gate; `deletePersonData` persisted to disk, other people
48+
- [x] `npm run type-check && npm run lint && npm test` clean.
49+
- [x] Tests: the gate; `deletePersonData` persisted to disk, other people
5050
untouched; Purge deletes the private profile; the cleanup is
5151
admin-only, counts without emails, deletes on `apply`, then counts 0.
5252

@@ -56,4 +56,17 @@ private store would write the old data back).
5656

5757
## Notes
5858

59+
- Incident: #253 merged 35 s before Release #254 was cut, so v0.10.2
60+
carried it; the sandbox's boot sweep wrote 5e11d592e ("people:
61+
scheduled spam purge (27)") to the shared `published`. Production was
62+
held on v0.10.1 and goes straight to v0.10.3.
63+
- Devbox (flag unset): the pod logged "scheduled spam purge disabled" and
64+
wrote no data commit.
65+
- Chose an in-API admin endpoint over the operator script first proposed:
66+
the API rewrites whole private-store files from memory on its next
67+
private write, so a script beside a live pod would be undone.
68+
5969
## Follow-ups
70+
71+
- **None.** Operator steps (set the flag in cfp-live-cluster, run the
72+
cleanup with Chris's OK) are in the runbook and with the release.

0 commit comments

Comments
 (0)