- watchdog.py: tier0 auto-recovery (3 retries, 1h cooldown, audit trail) — pending Ganymede review
- stale_pr.py: new module, closes extraction PRs open >30 min with zero claims
- deploy.sh: expanded with new deployment features
- validate.py, extract.py, cascade.py, db.py: minor fixes
- backfill-descriptions.py: utility script
- review_queue.py: minor fix
Note: watchdog + stale_pr not yet deployed to VPS (reverted after missing import crash)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Files consolidated:
- dashboard_routes.py: root copy (39K) overwrites teleo-codex (34K) — has cost fix + connection leak fix
- dashboard_prs.py: root copy overwrites — has cost display rewrite
- dashboard_epistemic.py: root copy overwrites — has Ship rename
- research_tracking.py: new file, existed only in root /diagnostics/ (reviewed by Ganymede, never committed here)
- research_routes.py: new file, same situation
- ops/db.py: new file, unique to root /diagnostics/ops/
After this commit, root /diagnostics/ contains only stale copies and patch files — safe to delete.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move vitality.py/vitality_routes.py from root diagnostics/ to ops/diagnostics/ (canonical location).
Overwrite ops/diagnostics/alerting.py and alerting_routes.py with root versions (newer: SQL injection protection via _ALLOWED_DIM_EXPRS, proper error handling + conn.close).
Remove root diagnostics/*.py — all code now in ops/diagnostics/.
Include diff log documenting resolution of each multi-copy file.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
GitHub Support flagged "how do I" as matching a known support-scam
pattern. Both occurrences are legitimate research sentences — reworded
to avoid the pattern while preserving meaning.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- GEPA self-evolution system (trace-based evolutionary prompt optimization)
- DeMo: Decoupled Momentum Optimization (Peng, Kingma et al. — 85x bandwidth reduction)
- YaRN: Context Window Extension (adopted by Meta and DeepSeek)
- Hermes 4 Technical Report (hybrid reasoning model family)
- Agent Skills open standard (30+ platform adoption, Anthropic-originated)
Per m3ta directive: GEPA and skills ecosystem observations are solid
research material worth extracting as sources regardless of deployment.
Pentagon-Agent: Theseus <46864dd4-da71-4719-a1b4-68f7c55854d3>
- Add domain_agent and domain_model to pr-lifecycle API response (data was
queried but dropped before serialization — evaluator column showed blank)
- Show model name tag next to evaluator (Gemini Flash, GPT-4o, etc.)
- Re-attribute 1201 "pipeline (self-directed)" PRs to @m3taversal — these
were Cory-directed, not autonomous overnight research
- Re-attribute 252 NULL PRs to @m3taversal
- Fix extract.py defaults: new PRs without proposed_by default to @m3taversal
- Fix backfill script defaults: extract/ branches → @m3taversal, not
"pipeline (self-directed)"
- Only agent-named branches (rio/, theseus/, etc.) from research-session.sh
remain as "(self-directed)"
Pentagon-Agent: Ship <B8D06D3F-1589-4777-B2E7-B2460D51C81F>
Three fixes for the reweave merge failure cycle:
1. reweave.py: fetch + reset to origin/main before branch creation,
eliminating the stale-base problem that caused ~75% merge failure rate
2. merge.py: delete remote branch when closing reweave PRs (in reconcile,
merge failure, and conflict retry paths) — prevents discover_external_prs
from rediscovering stale branches and creating new PRs every 18 minutes
3. merge.py: skip cherry-pick retry for reweave branches — reweave modifies
existing files so cherry-pick always fails, go straight to close+delete
Pentagon-Agent: Ship <f3064ef4-c330-4809-ad37-39290b2eaa5b>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The regex fallback was writing list entries as ' - "title"' (2-space
indent + quotes) while existing frontmatter uses '- title' (0-space
indent, no quotes). This caused YAML parse failures during merge.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
date_errors was evaluated but never routed to any fixer, leaving PRs
stuck permanently. Now classified as FIXABLE with targeted prompt guidance.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
