feat(management): server-side secured-write TTL — stale pending writes expire, never execute (arch-review S2)

Claude-Session: https://claude.ai/code/session_01MtdgwpEeCUn6cUA5f1LMPj
This commit is contained in:
Joseph Doherty
2026-07-10 05:38:19 -04:00
parent b3e2294e1d
commit 064a7d9415
7 changed files with 129 additions and 2 deletions
@@ -24,6 +24,14 @@ public enum AuditKind
SecuredWriteReject,
SecuredWriteExecute,
/// <summary>
/// A Pending secured write aged past its server-side TTL and was transitioned to
/// <c>Expired</c> without ever executing — the stale setpoint is never relayed to
/// the site. Emitted best-effort by the system (no verifier) when the approve/reject
/// path or the opportunistic list sweep observes an overdue Pending row. (arch-review S2)
/// </summary>
SecuredWriteExpire,
/// <summary>
/// A reconciliation pull row that failed to insert on every retry up to the
/// permanent-abandon threshold, so central advanced its cursor past it and