v0.6.407 residuals: audit forwarding, classification, Delete forever, IdP start (multi-instance and edge cases) #1174

Open
opened 2026-11-12 19:12:37 +00:00 by Cordy · 0 comments
Owner

Residuals named in the v0.6.407 reviews (details in .superpowers/sdd/backlog/findings.md and ARCHITECTURE.md residual lists).

#1044 audit forwarding:

  • Lag mail key follows Bell.Since (second mail possible if the earliest instance stops reporting); key by destination plus first failingSince.
  • Config-file destinations do not start while destinations.json is unreadable (fall back to Config).
  • Lease held after the last destination is removed; plain syslog-tcp connect failures not recorded; form test event lacks to=.
  • First-position rule can skip a late event in the ~20 s window at a destination's start; a pruned month can be over-counted after a crash or a posix retry.
  • segments/seal.go:119 still uses AddDate(0,-n,0) (29th-31st); segments.Verify cannot detect an edit of a chain's newest segment.

#1043 classification:

  • Existence oracle by guessed name for guests/link visitors (404 vs 409); OCM folder ETags change when hidden items change.
  • labels.Store.Set should require a version for any lowering; share index by root for linkHides/labelMoveWarning; owner-scoped count route for F16.
  • Start-up window: the label hook is attached before the settings (an unreadable store would refuse renames even where classification was never configured; nothing renames there today).

#1152 Delete forever:

  • Busy folders remembered within one call; admin settings GET may query directory groups each time; trash-forever-back bell can reach a reused account name; erase-request-expired double-record race; OIDC claim-admins count until next sign-in for requester-not-admin.

#1137 / #936:

  • Fingerprint does not follow a client-key renewal accepted while no instance has reached the provider; faultGot1137 duplicates oidclib's gotText; --routes runs the IdP wiring; not-found rule reads any 404 JSON with a string error as a configuration fault; add cairnd check-oidc and a tls-version failure code.
Residuals named in the v0.6.407 reviews (details in `.superpowers/sdd/backlog/findings.md` and ARCHITECTURE.md residual lists). #1044 audit forwarding: - Lag mail key follows `Bell.Since` (second mail possible if the earliest instance stops reporting); key by destination plus first `failingSince`. - Config-file destinations do not start while `destinations.json` is unreadable (fall back to `Config`). - Lease held after the last destination is removed; plain `syslog-tcp` connect failures not recorded; form test event lacks `to=`. - First-position rule can skip a late event in the ~20 s window at a destination's start; a pruned month can be over-counted after a crash or a posix retry. - `segments/seal.go:119` still uses `AddDate(0,-n,0)` (29th-31st); `segments.Verify` cannot detect an edit of a chain's newest segment. #1043 classification: - Existence oracle by guessed name for guests/link visitors (404 vs 409); OCM folder ETags change when hidden items change. - `labels.Store.Set` should require a version for any lowering; share index by root for `linkHides`/`labelMoveWarning`; owner-scoped count route for F16. - Start-up window: the label hook is attached before the settings (an unreadable store would refuse renames even where classification was never configured; nothing renames there today). #1152 Delete forever: - Busy folders remembered within one call; admin settings GET may query directory groups each time; `trash-forever-back` bell can reach a reused account name; `erase-request-expired` double-record race; OIDC claim-admins count until next sign-in for requester-not-admin. #1137 / #936: - Fingerprint does not follow a client-key renewal accepted while no instance has reached the provider; `faultGot1137` duplicates oidclib's `gotText`; `--routes` runs the IdP wiring; `not-found` rule reads any 404 JSON with a string `error` as a configuration fault; add `cairnd check-oidc` and a tls-version failure code.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1174
No description provided.