pipeline(labels): author-based eligibility — gittensor:priority only on maintainer-authored issues, auto-strip elsewhere

[JSONbored]

Problem

gittensor:priority carries the highest scoring multiplier, which makes it the one label whose application must be constrained by rule. The clean, mechanical rule: priority marks work the maintainer has originated and triaged as most valuable — so the label is only valid on issues authored by a repo maintainer.

Scope

• Pipeline rule evaluated on every label-add event (and on a periodic sweep for drift): if gittensor:priority is present on an issue whose author is not a maintainer of record, the pipeline removes the label and posts a single neutral comment linking the policy doc
• Maintainer-of-record derived from repo permissions, not a hardcoded name, so the rule generalizes to any repo ORB manages
• Enforcement events written to the decision ledger like any other pipeline action (event type, issue, actor, rule id), so the rule's history is independently checkable
• Idempotent: re-labeling triggers re-strip; no comment spam (edit/update the existing comment)
• Policy doc page: which labels carry scoring weight, the eligibility rule for each, and where enforcement lives in code
• Tests: contributor-authored issue labeled priority (by anyone, including a maintainer) → stripped + logged; maintainer-authored issue labeled priority → untouched

Acceptance

No open issue on any managed repo carries gittensor:priority unless its author is a maintainer of record; every strip is ledger-logged; the policy doc is linked from the strip comment.

Out of scope

Changes to the multiplier values themselves (registry-side, separate venue).

[linear-code]

JSO-6800