view-as/persona: mutations write for real under persona + appEvents.actorUserId=persona not real admin — decide intended semantics (read-only no-op? real-user telemetry?)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 6w ago
• wi-cli-venus statusChanged · 4w ago
  Elazar go, 2026-07-16
• wi-cli-venus note · 4w ago
  Elazar ruling (2026-07-17, via pmmaster-evolutiva-cc): persona/view-as = write-but-attribute-to-real-admin. Allow the write while impersonating, but attribute it to the REAL logged-in admin, not the impersonated persona. appEvents actor field = real admin (actual operator), not the persona.
• wi-cli-venus assigned · 4w ago
  coder-venus-cc
• wi-cli-venus note · 4w ago
  support-core telemetry/domain dual-use split deferred to VENUS-260 (audit-venus-ca ruling B). This WI covers all pure-telemetry appEvents actor stamps via accountableActorId helper.
• wi-cli-venus completed · 4w ago
  Elazar ruling implemented: persona/impersonation appEvents actor attributed to real operator via accountableActorId(realAdminId ?? ownerUserId ?? id) across 10 files' telemetry stamps; effectiveUserId preserves assumed identity for both impersonation+persona. Domain authorship (createdBy/resolvedByUserId/authorUserId) + archive GUC untouched. SHA ec5a272/v0.97.9, Class-A, audit-venus-ca PASS on raw diff, PTD confirmed (deploy READY correct-SHA prod-alias, live version-match, build clean 41s, 0 runtime errors). Follow-up filed VENUS-260 (support-core SupportActor domain/telemetry split, deferred).