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
corrections: salted actor hash for distinct-people counts #7563
Understood: this is a parked, deferred item. Distinct-people counts in corrections would use a salted actor hash. It reopens only once the team-sources policy exists, which is the condition for reading teammates' sessions. No open issue tracks that policy, so I listed no blocker. The done-when items are to cite the policy and file slices, so the work can't start until the policy lands. I found no clear duplicates among the open issues.
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.
Not admitted to the issue lane: a Feature needs an open parent issue a listed human filed that awaits no decision. A recorded decision does not change these rules (.github/actions/resolve-config/admission-rules.json); a person who wants it worked adds agent-ready.
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.
The work-resolve-issue lane did not start this issue: it needs a person to make it clearer first.
Why, in the run's own words:
#7563 is parked: its Depends on line says it opens only on its reopen trigger, "The team-sources policy exists (C7: teammates' sessions are read only under a known policy)". No such policy exists in the repository: a search for team-sources, teammates' sessions, salted actor and actor hash across the checkout, including plugins/corrections, found nothing. The issue records no decision. Both of its Done-when items depend on that policy ("The policy exists and is cited in a comment", "Slices are filed under this item"), and its Out of scope forbids reading teammates' sessions before the policy exists. Writing the policy is an intent and vision call about whose sessions the corrections plugin may read, so this run must not write it. Question for a person: (1) Should this issue go back to parked (needs-human or status: needs-decision) until the C7 team-sources policy is written? Or should someone write that policy now and cite it here, so this item can be sliced into implementation issues under it?
What the run says it did not do:
No review, build, test or lint step ran, because no file was changed (pushback before any edit).
git-read status lists untracked dotfiles and editor directories at the checkout root (.bash_profile, .bashrc, .gitconfig, .idea, .mcp.json, .profile, .ripgreprc, .vscode, .zprofile, .zshrc). This run wrote none of them and left them alone; they look like runner environment artifacts and should not b
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: none
Size: Small
Complexity: Low
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is a parked, deferred item. Distinct-people counts in corrections would use a salted actor hash. It reopens only once the team-sources policy exists, which is the condition for reading teammates' sessions. No open issue tracks that policy, so I listed no blocker. The done-when items are to cite the policy and file slices, so the work can't start until the policy lands. I found no clear duplicates among the open issues.
Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane: a Feature needs an open parent issue a listed human filed that awaits no decision. A recorded decision does not change these rules (
.github/actions/resolve-config/admission-rules.json); a person who wants it worked addsagent-ready.kyle-sexton commentedon Oct 26, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 26, 2026
The work-resolve-issue lane did not start this issue: it needs a person to make it clearer first.
Why, in the run's own words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40261944111
To retry, answer the question here, remove
needs-humanand addagent-readyagain.