Skip to content

feat(github-app): focus-manifest policy as gate input #555

Description

@JSONbored

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) feeds FocusManifestGuidance (advisory only); evaluateGateCheck ignores it.

Desired Behavior

  • A manifestPolicyGateMode setting makes blockedPaths, linkedIssuePolicy:"required", and testExpectations enforceable gate blockers, surfaced through the existing Gate check.

Implementation Requirements

  • Extend GateCheckPolicy + evaluateGateCheck to consume manifest policy; new setting + migration. Reuse the existing manifest parser/guidance.

Public/Private Output Boundaries

  • Gate text through sanitizeForCheckRun; manifest content is repo-public already.

Acceptance Criteria

  • A PR touching a manifest blockedPath or missing a required test fails the gate when enabled.

Testing Requirements

  • npm run test:ci, 97%+ coverage. Manifest-policy gate fixtures.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions