6d713aeeb9
Some checks failed
PR Checklist / pr-checklist (pull_request) Failing after 1m18s
Golden state: Kimi K2.5 primary → Gemini via OpenRouter → local Ollama. Anthropic is gone from every active config, fallback chain, and loop script. Wizard configs (3): - allegro, bezalel, ezra: removed anthropic from fallback_providers, replaced with gemini + ollama. Removed anthropic provider section. Playbooks (7): - All playbooks now use kimi-k2.5 as preferred, google/gemini-2.5-pro as fallback. No claude model references remain. Fleet scripts (8): - claude-loop.sh: deprecated (exit 0, original preserved as reference) - claudemax-watchdog.sh: deprecated (exit 0) - agent-loop.sh: removed claude dispatch case - start-loops.sh: removed claude-locks, claude-loop from proc list - timmy-orchestrator.sh: removed claude worker monitoring - fleet-status.sh: zeroed claude loop counter - model-health-check.sh: replaced check_anthropic_model with check_kimi_model - ops-gitea.sh, ops-helpers.sh, ops-panel.sh: removed claude from agent lists Infrastructure (5): - wizard_bootstrap.py: removed anthropic pip package and API key checks - WIZARD_ENVIRONMENT_CONTRACT.md: replaced ANTHROPIC keys with KIMI - DEPLOY.md: replaced ANTHROPIC_API_KEY with KIMI_API_KEY - fallback-portfolios.yaml: replaced anthropic provider with kimi-coding - fleet-vocabulary.md: updated Ezra and Claude entries to Kimi K2.5 Docs (2): - sonnet-workforce.md: deprecated with notice - GoldenRockachopa-checkin.md: updated model references Preserved (not touched): - training/ data (changing would corrupt training set) - evaluations/ (historical benchmarks) - RELEASE_*.md (changelogs) - metrics_helpers.py (historical cost calculation) - hermes-sovereign/githooks/pre-commit.py (secret detection - still useful) - security/secret-scan.yml (key detection - still useful) - architecture_linter.py (warns about anthropic usage - desired behavior) - test_sovereignty_enforcement.py (tests anthropic is blocked - correct) - son-of-timmy.md philosophical references (Claude as one of many backends) Refs: Sovereignty directive, zero-cloud vision
75 lines
1.8 KiB
YAML
75 lines
1.8 KiB
YAML
name: bug-fixer
|
|
description: 'Fixes bugs with test-first approach. Writes a failing test that reproduces the bug, then fixes the code, then
|
|
verifies.
|
|
|
|
'
|
|
model:
|
|
preferred: kimi-k2.5
|
|
fallback: google/gemini-2.5-pro
|
|
max_turns: 30
|
|
temperature: 0.2
|
|
tools:
|
|
- terminal
|
|
- file
|
|
- search_files
|
|
- patch
|
|
trigger:
|
|
issue_label: bug
|
|
manual: true
|
|
repos:
|
|
- Timmy_Foundation/the-nexus
|
|
- Timmy_Foundation/timmy-home
|
|
- Timmy_Foundation/timmy-config
|
|
- Timmy_Foundation/hermes-agent
|
|
steps:
|
|
- read_issue
|
|
- clone_repo
|
|
- create_branch
|
|
- dispatch_agent
|
|
- run_tests
|
|
- create_pr
|
|
- comment_on_issue
|
|
output: pull_request
|
|
timeout_minutes: 15
|
|
system_prompt: 'You are a bug fixer for the {{repo}} project.
|
|
|
|
|
|
YOUR ISSUE: #{{issue_number}} — {{issue_title}}
|
|
|
|
|
|
APPROACH (prove-first):
|
|
|
|
1. Read the bug report. Understand the expected vs actual behavior.
|
|
|
|
2. Reproduce the failure with the repo''s existing test or verification tooling whenever possible.
|
|
|
|
3. Add a focused regression test if the repo has a meaningful test surface for the bug.
|
|
|
|
4. Fix the code so the reproduced failure disappears.
|
|
|
|
5. Run the strongest repo-native verification you can justify — all relevant tests, not just the new one.
|
|
|
|
6. Commit: fix: <description> Fixes #{{issue_number}}
|
|
|
|
7. Push, create PR, and summarize verification plus any residual risk.
|
|
|
|
|
|
RULES:
|
|
|
|
- Never claim a fix without proving the broken behavior and the repaired behavior.
|
|
|
|
- Prefer repo-native commands over assuming tox exists.
|
|
|
|
- If the issue touches config, deploy, routing, memories, playbooks, or other control surfaces, flag it for Timmy review
|
|
in the PR.
|
|
|
|
- Never use --no-verify.
|
|
|
|
- If you can''t reproduce the bug, comment on the issue with what you tried and what evidence is still missing.
|
|
|
|
- If the fix requires >50 lines changed, decompose into sub-issues.
|
|
|
|
- Do not widen the issue into a refactor.
|
|
|
|
'
|