Repository navigation
Description
Is there an existing issue for this?
- I have searched the existing issues.
What area does this task affect?
CI/CD
Task description
Define and test the trusted-ref policy for credential-health workflow dispatch. Deliver one independently reviewable result at the operator trust review, parallel stage.
Scope and acceptance criteria
- Document the actual authorized actors, refs, runner-group/environment controls and credential scopes. Separate accidental branch selection, a fork actor and an actor who can edit the workflow; mark unavailable organization-policy evidence explicitly.
- Choose and document the maintainer-approved trusted-ref policy before claiming hardened dispatch. A mutable if-condition in the attacker-editable workflow is not independent protection; do not advertise it as one.
- At least eight deterministic contracts cover authorized/denied actors, allowed/disallowed refs, altered workflow identity, fork exclusion, missing credentials and provider failure, using fake endpoints and no real secrets.
- Preserve the mandatory vypdev self-hosted policy and existing hosted exceptions only for event admission/npm OIDC. Do not change consumer installation templates or deploy/activate Bugbot.
Current issues or inefficiencies
The final review raised branch-controlled credential-health dispatch on persistent self-hosted runners. Manual dispatch requires repository write access, so no unauthorized event path was demonstrated; that is not proof that arbitrary workflow-editing collaborators or branch revisions are safe.
Observed baseline: unreleased develop ccefb27627cd627ccdb7d5666fd174c2ac1da07b from merged PR #951.
- .github/workflows/copilot_credential_health.yml
- docs/security-operations/security/trust-boundaries.mdx
- docs/security-operations/security/self-hosted-runners.mdx
Expected impact
Make this one pending result independently inspectable and reproducible, with its actual passed, failed or unavailable evidence.
Completion does not authorize release, producer trust, profile qualification from partial measurements, or production activation.
Additional context or comments
Priority and dependencies
- Priority: medium. Stage: Operator trust review, parallel.
- Blocked by: None; may be prepared independently.
- Follow-up to ✨🧑💻 - Verify Bugbot findings against repository evidence before publication #950 and merged PR feat: Verify Bugbot findings against repository evidence before publication (#950) #951, not a request to reopen or extend that delivery.
- Final closure and observed limitations. Review thread.
Documentation and implementation boundary
Documentation: docs/security-operations/security/trust-boundaries.mdx, docs/security-operations/security/self-hosted-runners.mdx.
Keep Clean Architecture and current coverage/contract gates. When a later implementation changes a public contract, update its catalogued SDD, tests and docs together and validate specifications; update Graphify after code changes.
Read the effective #950 contract in the owning SDD and its current reconciliation amendments; historical pilot deadlines are not current investigation limits.
Fixed invariants and planning state
Backlog only: no in-progress, branch creation, model execution, deployment or activation requested by this planning step.
Keep BUGBOT_VERIFICATION_MODE=disabled. Evaluated PRs must have zero write attempts; retain frozen pilots and independent evaluator/oracle evidence.
Token usage is optional telemetry and cannot stop investigation or reject a supported verdict. Elapsed time and turn count do not impose research cutoffs; explicit cancellation and evidence/SHA integrity remain mandatory. Post-run latency qualification criteria remain distinct from session deadlines.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsIn Progress
Activity
[-]Define and test the trusted-ref policy for credential-health workflow dispatch[/-][+]🔧 - Define and test the trusted ref policy for credential health workflow dispatch[/+]vypbot commentedon Nov 19, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.[-]🔧 - Define and test the trusted ref policy for credential health workflow dispatch[/-][+]🔧🧑💻 - Define and test the trusted ref policy for credential health workflow dispatch[/+]vypbot commentedon Nov 19, 2026
Implementation plan
Acceptance: The operator trust review contains the approved trusted-ref policy, documented actor/ref/runner/environment/credential boundaries and explicit unavailable organization evidence; at least eight deterministic fake-endpoint contracts cover the required cases with no real secrets, and all applicable project gates pass without release or activation.
Need something else? Mention the bot with a question or use
/copilot help.chore-979-define-and-test-the-trusted-ref-policy-for-credential-healt…
vypbot commentedon Nov 19, 2026
Progress · 65% estimated
Assessed head
f0655e7f· 2/7 supported1 need implementation · 4 need verification or clarification
Implementation still needed
Verification or clarification needed
Issue · Linked pull request · Full assessment