Add owner-authorized repository-local autonomous /loop workflow #21

Closed
opened 2026-10-05 07:59:57 +00:00 by kilo · 4 comments
Member

Owner mandate: Adrian's explicit 2026-10-05 task authorizes exactly one deduplicated workflow issue and its normal implementation/PR delivery. Existing #5 covers bounded review/remediation only, not autonomous selection/merge/next-issue delivery. This issue changes development workflow, not MI product architecture.

Implement .kilo/command/loop.md with the primary invocation context as sole orchestrator. Reuse implement-issue and native finish-pr/review-pr semantics; preserve the reviewer unchanged unless narrowly necessary. One normal checkout, one mutator, no worktree/alternate checkout/stash/reset of owner work, no second controller/service/scheduler/database, no Scarcity Router use, no other-repository mutation, main/release/deploy or direct develop push.

Selection: refresh all canonical open MI issues each cycle; exclude labels exactly invalid/wontfix/duplicate case-insensitively before any historical PR interpretation. Do not extend exclusions. Exclude unmet explicit prerequisites/gates and unresolved owner decisions; never invent dependencies. Order eligible issues by explicit priority, explicit required gate/implementation ordering, then oldest created_at. Resolve material conflicts with owner. Issue is planning authority; unrelated/historical/abandoned PRs cannot select/reorder/restart work. After selection continue one current authorized issue PR or create one through existing implementation workflow.

Review/remediation: fresh isolated read-only pr-reviewer whole-PR task every invocation, frozen exact HEAD/base and complete delta, stable structured contract. Loop-capable finish is bounded to 10 whole-PR invocations per issue delivery including initial and COMMENT, persisted in excluded .task_progress.md across reentry/phases/model/session changes within one loop invocation. No reset/history rewrite; genuine decisions stop early. APPROVE needs empty findings, exact current HEAD/base, clean checkout, successful final gate, current open/unmerged develop-target PR.

Loop alone authorizes supported canonical Forgejo PR merge to develop after refreshed exact approval/currentness checks. Verify actual merge and develop advance, acceptance, then close completed issue appropriately, return safely to clean current develop, refresh queue. Standalone review stays read-only, standalone finish READY_TO_MERGE without merge, standalone implementation owner-selected. Terminal QUEUE_EMPTY, STOP_AND_ASK, STOP_REVISE, BLOCKED. Owner decisions stop entire loop, not skip selected issue; provide exact issue/PR/HEAD, evidence, unresolved rationale, concrete options/tradeoffs/recommendation.

Validation: repository-owned deterministic workflow-text consistency tests covering discovery, authority boundaries, exact label exclusions, ordering, PR non-authority, reviewer independence, durable 10-review limit, exact approval, PR-only develop merge, verified acceptance/closure and hard constraints. Run make check and fresh independent review.

This workflow-change PR itself uses CURRENT pre-merge authorization: maximum three remediation rounds after initial review, independent exact-HEAD APPROVE; no merge authority granted by this task. Keep this issue open at READY_TO_MERGE handoff; use Refs, not automatic closing keywords. No functional issue is selected by this mandate.

Owner mandate: Adrian's explicit 2026-10-05 task authorizes exactly one deduplicated workflow issue and its normal implementation/PR delivery. Existing #5 covers bounded review/remediation only, not autonomous selection/merge/next-issue delivery. This issue changes development workflow, not MI product architecture. Implement `.kilo/command/loop.md` with the primary invocation context as sole orchestrator. Reuse implement-issue and native finish-pr/review-pr semantics; preserve the reviewer unchanged unless narrowly necessary. One normal checkout, one mutator, no worktree/alternate checkout/stash/reset of owner work, no second controller/service/scheduler/database, no Scarcity Router use, no other-repository mutation, main/release/deploy or direct develop push. Selection: refresh all canonical open MI issues each cycle; exclude labels exactly invalid/wontfix/duplicate case-insensitively before any historical PR interpretation. Do not extend exclusions. Exclude unmet explicit prerequisites/gates and unresolved owner decisions; never invent dependencies. Order eligible issues by explicit priority, explicit required gate/implementation ordering, then oldest created_at. Resolve material conflicts with owner. Issue is planning authority; unrelated/historical/abandoned PRs cannot select/reorder/restart work. After selection continue one current authorized issue PR or create one through existing implementation workflow. Review/remediation: fresh isolated read-only pr-reviewer whole-PR task every invocation, frozen exact HEAD/base and complete delta, stable structured contract. Loop-capable finish is bounded to 10 whole-PR invocations per issue delivery including initial and COMMENT, persisted in excluded .task_progress.md across reentry/phases/model/session changes within one loop invocation. No reset/history rewrite; genuine decisions stop early. APPROVE needs empty findings, exact current HEAD/base, clean checkout, successful final gate, current open/unmerged develop-target PR. Loop alone authorizes supported canonical Forgejo PR merge to develop after refreshed exact approval/currentness checks. Verify actual merge and develop advance, acceptance, then close completed issue appropriately, return safely to clean current develop, refresh queue. Standalone review stays read-only, standalone finish READY_TO_MERGE without merge, standalone implementation owner-selected. Terminal QUEUE_EMPTY, STOP_AND_ASK, STOP_REVISE, BLOCKED. Owner decisions stop entire loop, not skip selected issue; provide exact issue/PR/HEAD, evidence, unresolved rationale, concrete options/tradeoffs/recommendation. Validation: repository-owned deterministic workflow-text consistency tests covering discovery, authority boundaries, exact label exclusions, ordering, PR non-authority, reviewer independence, durable 10-review limit, exact approval, PR-only develop merge, verified acceptance/closure and hard constraints. Run make check and fresh independent review. This workflow-change PR itself uses CURRENT pre-merge authorization: maximum three remediation rounds after initial review, independent exact-HEAD APPROVE; no merge authority granted by this task. Keep this issue open at READY_TO_MERGE handoff; use Refs, not automatic closing keywords. No functional issue is selected by this mandate.
Author
Member

Implemented the authorized workflow scope in PR #22: #22 . Base 8f503107b8, HEAD abb4e2e96d. Focused workflow checks PASS9; repository make check PASS46, Ruff/type/locked-sync/whitespace clean. Reviewer and review-pr unchanged; no product/source/dependency changes. Fresh native independent review next under the CURRENT maximum-three-remediation-round bound; this delivery does not invoke /loop or authorize merging/closing #21. Runtime command loading not claimed; Kilo workspace reload may be needed.

Implemented the authorized workflow scope in PR #22: https://forgejo.creatidy.com/Creatidy/model-intelligence/pulls/22 . Base 8f503107b8800b0ff007fa81a8137f2e5834ea80, HEAD abb4e2e96d50d52338e83da3d6150c5ea786da40. Focused workflow checks PASS9; repository make check PASS46, Ruff/type/locked-sync/whitespace clean. Reviewer and review-pr unchanged; no product/source/dependency changes. Fresh native independent review next under the CURRENT maximum-three-remediation-round bound; this delivery does not invoke /loop or authorize merging/closing #21. Runtime command loading not claimed; Kilo workspace reload may be needed.
Author
Member

READY_TO_MERGE for PR #22, still open/unmerged: #22 . Fresh native whole-PR reviewer ses_ef4e2c97effelZAGK8jp8erZ0X returned APPROVE with empty findings at exact HEAD abb4e2e96d / base 8f503107b8. Independent UV_OFFLINE=1 make check PASS46; parent make check PASS46 and focused workflow PASS9. Final canonical MCP/Git SHAs, open/unmerged develop target, owner commit identity and clean status verified. One review, zero remediation rounds under CURRENT pre-merge policy. No workflow-change PR merge/issue closure or autonomous queue execution authorized/performed. Runtime command discovery remains unverified; workspace reload may be needed, and local kilo debug CLI is absent. Tests establish workflow-text consistency, not live loop-operation proof.

READY_TO_MERGE for PR #22, still open/unmerged: https://forgejo.creatidy.com/Creatidy/model-intelligence/pulls/22 . Fresh native whole-PR reviewer ses_ef4e2c97effelZAGK8jp8erZ0X returned APPROVE with empty findings at exact HEAD abb4e2e96d50d52338e83da3d6150c5ea786da40 / base 8f503107b8800b0ff007fa81a8137f2e5834ea80. Independent UV_OFFLINE=1 make check PASS46; parent make check PASS46 and focused workflow PASS9. Final canonical MCP/Git SHAs, open/unmerged develop target, owner commit identity and clean status verified. One review, zero remediation rounds under CURRENT pre-merge policy. No workflow-change PR merge/issue closure or autonomous queue execution authorized/performed. Runtime command discovery remains unverified; workspace reload may be needed, and local kilo debug CLI is absent. Tests establish workflow-text consistency, not live loop-operation proof.
Author
Member

Owner requested narrow pre-merge semantic remediation: if canonical selected issue gains exactly invalid/wontfix/duplicate (case-insensitive), skip merge/completion, record exclusion, preserve history, safely return same checkout to clean current develop, rebuild SELECT from fresh Forgejo state without terminal status; do not broaden to other labels. Implemented in normal same-PR commit e3d04be2b3, base 8f503107b8. Only loop.md and test_workflow_contract.py changed in remediation. Regression reproduced prior failure; focused10/full makecheck47 PASS. Previous abb4e2e APPROVE no longer current; fresh whole-PR review pending, remediation1/3 under pre-merge policy. No merge/closure/loop execution.

Owner requested narrow pre-merge semantic remediation: if canonical selected issue gains exactly invalid/wontfix/duplicate (case-insensitive), skip merge/completion, record exclusion, preserve history, safely return same checkout to clean current develop, rebuild SELECT from fresh Forgejo state without terminal status; do not broaden to other labels. Implemented in normal same-PR commit e3d04be2b35e7467e83e18ad29cbce7a3acfea97, base 8f503107b8800b0ff007fa81a8137f2e5834ea80. Only loop.md and test_workflow_contract.py changed in remediation. Regression reproduced prior failure; focused10/full makecheck47 PASS. Previous abb4e2e APPROVE no longer current; fresh whole-PR review pending, remediation1/3 under pre-merge policy. No merge/closure/loop execution.
Author
Member

READY_TO_MERGE restored for PR #22 after narrow pre-merge exclusion remediation. Fresh independent whole-PR reviewer ses_ef4d37d12ffev8wsLT072aSfGS: APPROVE, empty findings, exact HEAD e3d04be2b3 / base 8f503107b8. Parent focused10 and makecheck47 PASS; independent UV_OFFLINE=1 makecheck47 and full-range whitespace PASS. Final canonical Git/MCP currentness, open/unmerged develop-target PR, owner authorship and clean checkout verified. Two reviews across delivery, remediation1/3 under pre-merge policy. No merge/issue closure or autonomous loop execution. Remaining limits: workflow-text validation, command discovery/reload unverified and local kilo debug CLI absent; no blocking review findings.

READY_TO_MERGE restored for PR #22 after narrow pre-merge exclusion remediation. Fresh independent whole-PR reviewer ses_ef4d37d12ffev8wsLT072aSfGS: APPROVE, empty findings, exact HEAD e3d04be2b35e7467e83e18ad29cbce7a3acfea97 / base 8f503107b8800b0ff007fa81a8137f2e5834ea80. Parent focused10 and makecheck47 PASS; independent UV_OFFLINE=1 makecheck47 and full-range whitespace PASS. Final canonical Git/MCP currentness, open/unmerged develop-target PR, owner authorship and clean checkout verified. Two reviews across delivery, remediation1/3 under pre-merge policy. No merge/issue closure or autonomous loop execution. Remaining limits: workflow-text validation, command discovery/reload unverified and local kilo debug CLI absent; no blocking review findings.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Creatidy/model-intelligence#21
No description provided.