From e4119eaa6bed2b833065cc2e886afdcc110556ef Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 8 Oct 2026 23:52:34 +0200 Subject: [PATCH] NK-WP-0048-T05: close the superseded memo with return, not by leaving it open Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 330051@bnt-lap001 Assistant-Session: b98d4912-95a3-4619-b7fb-57aa1db7407b --- workplans/NK-WP-0048-security-case-types.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/workplans/NK-WP-0048-security-case-types.md b/workplans/NK-WP-0048-security-case-types.md index 89d4307..028ef75 100644 --- a/workplans/NK-WP-0048-security-case-types.md +++ b/workplans/NK-WP-0048-security-case-types.md @@ -233,8 +233,13 @@ supersedes the first memo and passes informed-decision's and the dispatcher's validation. It needs a new memo id because the dispatcher refuses new content under a delivered idempotency key (`idempotency_conflict`). Queuing it is the same attended step as above. Both memos serve hub decision `e418263e`; the -first answer resolves it, so the founder answers r2 and leaves the first memo -unanswered. key-cape and railiance-apps were told about Forgejo's new custody +first answer resolves it, so the first memo must not stay open: an accept on it +would acknowledge the superseded shape, and a decline would resolve the +decision against r2. Close it with `return` (a reviewer verb that requests a +new revision and does not resolve the hub decision; only accept and decline +do), commenting that r2 supersedes it, then answer r2. `withdraw` exists in +the vocabulary but is not offered to reviewers, and lifecycle `revise` only +applies to lifecycle-registered memos, not intake-delivered ones. key-cape and railiance-apps were told about Forgejo's new custody path. ```task