-
-
Notifications
You must be signed in to change notification settings - Fork 89
feat(github-app): focus-manifest policy as gate input #555
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Milestone
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Parent roadmap: #525
Parent phase: #528
Background
Repo owners can declare policy in a focus manifest, but today it only produces advisory guidance — CI doesn't enforce it.
Goal
Wire focus-manifest policy into the gate so declared blocked paths / required-linked-issue / test expectations become configurable gate blockers.
Current Behavior
FocusManifest(src/signals/focus-manifest.ts:13) feedsFocusManifestGuidance(advisory only);evaluateGateCheckignores it.Desired Behavior
manifestPolicyGateModesetting makesblockedPaths,linkedIssuePolicy:"required", andtestExpectationsenforceable gate blockers, surfaced through the existing Gate check.Implementation Requirements
GateCheckPolicy+evaluateGateCheckto consume manifest policy; new setting + migration. Reuse the existing manifest parser/guidance.Public/Private Output Boundaries
sanitizeForCheckRun; manifest content is repo-public already.Acceptance Criteria
blockedPathor missing a required test fails the gate when enabled.Testing Requirements
npm run test:ci, 97%+ coverage. Manifest-policy gate fixtures.