Skip to content

feat(feedback): accept explicitly trusted private publisher identities - #425

Merged
rldyourmnd merged 1 commit into
mainfrom
feat/trusted-user-feedback-20260907
Sep 7, 2026
Merged

feat(feedback): accept explicitly trusted private publisher identities#425
rldyourmnd merged 1 commit into
mainfrom
feat/trusted-user-feedback-20260907

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

A trusted private executor using a User token could not deduplicate its own feedback because the publisher only recognized Bot accounts. Add an explicit publisher type with Bot unchanged as the default; User requires its exact configured numeric identity. Unknown types fail before API access, and unrelated or mismatched accounts cannot suppress a failure.

Evidence now includes observation/run creation times and a bounded reason derived only from authoritative conclusions. Product versus infrastructure classification remains unknown. Issues stay unassigned, and ambiguous POST replies still recover via the exact durable marker without a second write.

Validation: 23 production-publisher fixture tests, actionlint and full make verify (vet, race tests, release manifest and build) passed. No live private executor is claimed by this source change.

Closes #424.

Signed-off-by: rldyourmnd <danil@nddev.it.com>
@rldyourmnd
rldyourmnd merged commit 24dc426 into main Sep 7, 2026
10 checks passed
@rldyourmnd
rldyourmnd deleted the feat/trusted-user-feedback-20260907 branch September 7, 2026 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support explicitly trusted private feedback executors without broadening marker trust

1 participant