theseus: add 5 Nous Research source archives #2514

Closed
theseus wants to merge 7 commits from theseus/nous-research-sources into main

7 commits

Author SHA1 Message Date
3bf4be184d theseus: add 5 Nous Research source archives for codex ingestion
- 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>
2026-04-07 15:54:22 +01:00
0cf1927819 ship: fix evaluator column + correct contributor attribution
- 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>
2026-04-07 13:02:07 +01:00
0e966bbfdf ship: add contributor attribution tracing to PR lifecycle
- Migration v19: submitted_by column on prs + sources tables
- extract.py: propagates proposed_by from source frontmatter → PR record
- merge.py: sets submitted_by from Forgejo author for human PRs
- dashboard_prs.py: redesigned with Contributor column, improved claim
  visibility in expanded rows, cost estimates, evaluator chain display
- dashboard_routes.py: submitted_by + source_path in pr-lifecycle API
- backfill_submitted_by.py: one-time backfill (1525/1777 PRs matched)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-07 12:54:06 +01:00
ab3c2e072a fix: prevent reweave PR flood — freshen base, cleanup branches on failure
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>
2026-04-07 11:38:25 +01:00
77c05887d9 wire cascade, cross_domain, and review_records into pipeline
- merge.py: import + await cascade_after_merge and cross_domain_after_merge
  after reciprocal edges, before branch deletion. Both non-fatal.
  Added conn.commit() before slow branch deletion (Ganymede Q4).
- db.py: add record_review() helper + migration v18 (review_records table
  with indexes). Schema version 17→18.
- evaluate.py: call record_review() at all 3 verdict points:
  domain_rejected → outcome=rejected
  approved → outcome=approved
  changes_requested → outcome=approved-with-changes
  Notes field captures review text (capped 4000 chars).

Pentagon-Agent: Ship <E2A054E5-A6D6-4AE0-B0A3-F51A3B4DBCA5>
2026-04-07 02:28:07 +01:00
8118bf17b4 fix: reweave regex fallback uses consistent YAML list format
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>
2026-04-07 01:28:10 +01:00
779a82eb97 fix: add date_errors to substantive fixer tag routing
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>
2026-04-07 01:01:12 +01:00