Skip to content

[PR governance] Enroll html4tree in central OpenCode review dispatch #1003

Description

@seonghobae

Problem

ContextualWisdomLab/html4tree is governed by the central required-review workflows, but it is absent from the exact repository allowlist exposed through OPENCODE_REPOSITORY_DISPATCH_TARGETS.

The current html4tree pull requests have completed same-head Strix evidence, and the repository-local scheduler then stops with this fail-closed decision:

Required OpenCode Review dispatch waits for central required workflow materialization; required workflow source is ContextualWisdomLab/.github, but this scheduler run has no cross-repository repository-dispatch credential.

The central scheduler's runtime allowlist currently omits ContextualWisdomLab/html4tree, so the privileged central path cannot target the repository either. A green placeholder check must not be treated as an actual Reviews API verdict.

Affected current pull requests

  • ContextualWisdomLab/html4tree#435
  • ContextualWisdomLab/html4tree#436
  • ContextualWisdomLab/html4tree#442
  • ContextualWisdomLab/html4tree#444

All four have auto-merge enabled and remain blocked on a real independent current-head review verdict.

Acceptance criteria

  • Add ContextualWisdomLab/html4tree to the organization variable OPENCODE_REPOSITORY_DISPATCH_TARGETS without weakening the exact-allowlist or actor validation.
  • Run the central targeted scheduler for each affected current head after same-head Strix evidence completes.
  • Verify that opencode-agent or opencode-agent[bot] submits APPROVED or CHANGES_REQUESTED for the exact current head through the Reviews API.
  • Do not accept a COMMENTED review, old-head review, status-only check, human-originated repository_dispatch, or self-approval as satisfying the gate.
  • Confirm that an approved PR with successful exact-head required checks merges through the existing auto-merge policy.
  • Close this issue only after at least one html4tree PR receives a real current-head OpenCode review and the remaining affected PRs are queued through the same path.

Security boundary

This is a configuration enrollment request, not a request to remove fail-closed behavior or bypass independent approval.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions