chore: migrate development commands to the Model Intelligence loop workflow (#64) #65
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/creatidy-kernel!65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-64-model-intelligence-workflow"
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?
Scope
Refs #64. Replaces the complete development command system with the CURRENT LOCAL Model Intelligence workflow, without redesigning Kernel product behavior.
Repository: Creatidy/creatidy-kernel
Base:
c1ad28a517Final HEAD:
1f9172b7ccBranch: issue-64-model-intelligence-workflow
Commits:
c1c3ce6(migration),1f9172b(preserve exact source wording).Command Inventory
Before: /create-follow-up-issue, /deliver-issue, /implement-issue, /review-pr.
After: /implement-issue, /review-pr, /finish-pr, /loop.
Delivery is represented once by implement/finish. Follow-up issue quality (durable, distinct, actionable, deduplicated, verifiable criteria and triggering links) remains in task rules under explicit registration authorization, not an obsolete command or speculative queue.
Source And Exact Deviations
All requested live reference files were read at /home/adrian/workspace/model-intelligence. Current local reference HEAD: 013cbb43e11d7f698d359db5a456d26d8075e34e. Git confirms the inspected files match that HEAD; actual local contents were used, not remembered text or an older revision. Source repository was not mutated. Apache-2.0 license/attribution and adaptations are recorded in NOTICE and the existing reuse record.
Deviations are limited to Kernel repository identity/URLs/product names and external exclusion list; accepted Kernel architecture paths/boundaries and issue-quality safeguards; existing make check AND make package-check gates plus conditional make audit; exact pytest/import-linter/offline package-check reviewer commands; M0 -> A0 proof wording; required modification notices; adapted frozen test hashes with non-security SHA-1 and scanner annotations; one added inventory/gate/permission test. The source's Adrian-selected description and missing-native-review wording are retained. Reviewer model/variant, all existing denial patterns and isolation instructions are preserved. No runtime product code, dependencies or lockfile changes.
Acceptance Evidence
Files
Replaced: .kilo/command/implement-issue.md and review-pr.md; AGENTS.md and task/Forgejo/implementation/search/validation rules.
Added: finish-pr.md, loop.md, .kilo/agents/pr-reviewer.md, tests/test_workflow_contract.py.
Deleted: deliver-issue.md and create-follow-up-issue.md.
Adapted supporting files: .gitignore agent allowlisting, README, CONTRIBUTING, narrow development references in target/successor/ADR 0007, NOTICE and reuse provenance.
Final Validation
Review And Delivery Limitations
Terminal status: REVIEW_INFRASTRUCTURE_BLOCKED under the PRE-MIGRATION /deliver-issue contract. Independent delivery review: NOT_RUN, not APPROVE. Valid completed reviews: 0; remediation_used: 0/10. The old contract requires a fresh Scarcity Router repository_review selection and Router-eligible Agent Manager dispatch with verified resolution. No Router selection tool is exposed here. That requirement was not bypassed using the newly copied native-review rules or parent self-review.
The migration's new /loop was not invoked and cannot authorize its own integration. No merge authority is granted by this request: PR remains unmerged and #64 remains open. Local excluded ledger is .task_progress.md; canonical issue update records delivery evidence.
CLI discovery check failed because kilo is not installed on PATH. Native reviewer discovery/execution and end-to-end loop operation are unverified; workspace reload may be required after integration. Contract tests are offline textual consistency guards, not runtime/merge proof. Final canonical CI status is reported separately when observed.