You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ADR 0040 step 3 — Use the session visibility projection across daemon surfaces #4967
Delete remaining response-specific name filters after the callers move. Preserve the local device-recovery exception.
When a caller lacks session proof, use detached evidence or a public contention reason as permitted by policy.
Verification
Exercise a shared-token caller without tenant isolation, a tenant-scoped caller, and a local device-recovery caller. Verify the same visibility outcome across listing, progress, and contention.
Related work
Depends on the shared predicate in #4960. Keep its existing listing and reply coverage.
The issue requests implementation work: applying a shared session visibility projection to daemon surfaces, removing old filters, and verifying callers, rather than reporting broken behavior or asking for help.
When this step lands, amend the ADR that ADR 0040 (#4964) lists for it in its Amendments table, in the same PR. ADR 0040 does not edit those ADRs up front, because an ADR states the current truth and the code has not changed yet.
Activity
apex-sentinel-staging commentedon Nov 22, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue requests implementation work: applying a shared session visibility projection to daemon surfaces, removing old filters, and verifying callers, rather than reporting broken behavior or asking for help.
thymikee commentedon Nov 22, 2026
When this step lands, amend the ADR that ADR 0040 (#4964) lists for it in its Amendments table, in the same PR. ADR 0040 does not edit those ADRs up front, because an ADR states the current truth and the code has not changed yet.