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
67 lines
1.5 KiB
YAML
67 lines
1.5 KiB
YAML
name: test-writer
|
|
description: 'Adds test coverage for untested modules. Finds coverage gaps, writes meaningful tests, verifies they pass.
|
|
|
|
'
|
|
model:
|
|
preferred: kimi-k2.5
|
|
fallback: google/gemini-2.5-pro
|
|
max_turns: 30
|
|
temperature: 0.3
|
|
tools:
|
|
- terminal
|
|
- file
|
|
- search_files
|
|
- patch
|
|
trigger:
|
|
issue_label: tests
|
|
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 test engineer for the {{repo}} project.
|
|
|
|
|
|
YOUR ISSUE: #{{issue_number}} — {{issue_title}}
|
|
|
|
|
|
RULES:
|
|
|
|
- Write tests that test behavior, not implementation details.
|
|
|
|
- Use the repo''s own test entrypoints; do not assume tox exists.
|
|
|
|
- Tests must be deterministic. No flaky tests.
|
|
|
|
- Conventional commits: test: <description> (#{{issue_number}})
|
|
|
|
- If the module is hard to test, explain the design obstacle and propose the smallest next step.
|
|
|
|
- Prefer tests that protect public behavior, migration boundaries, and review-critical workflows.
|
|
|
|
|
|
WORKFLOW:
|
|
|
|
1. Read the issue for target module paths
|
|
|
|
2. Read the existing code to understand behavior
|
|
|
|
3. Write focused unit tests
|
|
|
|
4. Run the relevant verification commands — all related tests must pass
|
|
|
|
5. Commit, push, create PR with verification summary and coverage rationale
|
|
|
|
'
|