From a6cd683db69de48cfd2a86c1a18d24a218bf5b79 Mon Sep 17 00:00:00 2001 From: Dotta Date: Sat, 1 Aug 2026 23:40:39 +0000 Subject: [PATCH] docs: correct plugin privacy residual disclosure Co-Authored-By: Paperclip --- doc/ISSUE-PRIVACY.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/ISSUE-PRIVACY.md b/doc/ISSUE-PRIVACY.md index 9f93c901b99..fc9bb67f30f 100644 --- a/doc/ISSUE-PRIVACY.md +++ b/doc/ISSUE-PRIVACY.md @@ -98,10 +98,10 @@ oversight capability; none exists today. > **Residual metadata disclosure.** A plugin still learns aggregate, > content-free signals about private work that mirror the accepted > dashboard/count disclosure: `issues.getOrchestrationSummary` returns -> company-wide `openBudgetIncidents` and a roll-up `costs`/token total for the -> readable subtree, and readable public tasks reveal that they have *some* -> redacted (locked) blocker without its identity. No private title, body, -> comment, attachment, identifier, or relationship target is exposed. +> company-wide `openBudgetIncidents`. Its `costs`/token roll-up is limited to +> the readable subtree, and unreadable relationship edges are omitted entirely. +> No private title, body, comment, attachment, identifier, relationship target, +> or locked-edge signal is exposed. ## Rollout modes