App/server hardening follow-ups (loadReport currency, reconnect debounce, token->Keychain, idempotency namespacing) #6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design context:
docs/design/server-split.md+ tracking issue seltzerhq/pecun#18 (the code lives here in nic/commons).Accumulated app/server hardening follow-ups (from the P3b/P4 reviews + the P5/P6 session), none blocking:
loadReport: thread report currency + priorNetWorth through the gRPC path (currently dropped).the whole change_log per entry on a flap).
today -- a documented decision; revisit).
PR #12 (merged) landed four of the five follow-ups:
loadReport: report currency + priorNetWorth now threaded through the gRPC path (addedcurrency+prior_net_worthtoGetReportRequest).GRPCEndpoint.isLoopback).Leaving this issue open for the idempotency-namespacing item. It's a deliberate, documented semantic (first-writer-wins on a shared
content_hash), flagged inWriterExecutor.postTransaction: it only matters once clients choose their own idempotency keys -- today keys are server-generated per proposal -- so changing money-path dedup behavior shouldn't happen unilaterally. Decision needed: namespace the hash by principal now, or keep as-is until clients pick keys.Full gate was green at merge: 188 SwiftPM tests + the Xcode app oracle.