Make pr-reviewer binding provider/model-agnostic #22
No reviewers
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/creatidy-console!22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "maintenance/pr-reviewer-binding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Owner-authorized maintenance (direct instruction, 2026-10-05): make the
pr-reviewercontract provider/model-binding agnostic.Change
Only
.kilo/agents/pr-reviewer.md:model: openai/gpt-6.1-solandvariant: high(no replacement pin);## Reviewer bindingpolicy: reviewer inherits the implementation session's provider family/model/reasoning configuration by default, with OpenAI→OpenAI and z.ai→z.ai provider-family affinity, explicit owner override support, no silent substitution, and precise reporting when a binding cannot be executed.Preserved
Console-specific permission allowlists (
npm_config_offline=truetypecheck/test/make commands, canonical Creatidy/creatidy-console ls-remote URLs including the folded YAML? key : allowforms), the.kilo/rules/30-implementation-discipline.mdreference, the NOTICE provenance comment, checkout/read-only constraints, verdict semantics, and the stable JSON result schema (no new fields).Validation
description,mode,permission(folded multilinedescription:untouched)openai/gpt-6.1-sol,variant: high,GPT-6.1orKilo 7.8.3references remaingit diff --name-only origin/develop...HEAD→ only.kilo/agents/pr-reviewer.mdwithout exceeding this allowlist, Docker/evidence requirements)⚠ Why this PR is not merged
tests/workflow-contract.test.mjs(«independent review retains frozen permissions/model and JSON schema») asserts the SHA-256 of the reviewer frontmatter equals2fe21aebef14cab6dfc709822b9d3a356fb01eceb3923758ef7d892bae919a3b— the hash of the current pinned frontmatter (verified: origin/develop frontmatter hashes to exactly that value; this branch's hashes to99c2a06cbdcd476a3dcc6e6b424d548a0af4185da6d9559714dd3cb5044b27e7). The frozen hash encodes the verymodel:/variant:pins this maintenance removes, so the expected single CI failure is that assertion.Merging requires a one-line follow-up updating the frozen hash (or replacing the frontmatter freeze with a no-
model:/no-variant:assertion). That test file is outside this task's authorized scope, so the owner must authorize it. Everything else in the change is complete and validated.