feat(agent): harness adapter — miner-auto-dev profile + driving loop (#781) - #850
Conversation
…781) Phase 2: extend init-client into a first-class auto-dev profile that wires the miner's local harness (Claude Code/Codex/Cursor) to the gittensory MCP + the plan→implement→push driving loop. Closes out Phase 2. - packages/gittensory-mcp/bin/gittensory-mcp.js: new `miner-auto-dev` agent profile. Unlike the human-approved-only profiles, it is GATE-THROTTLED: it wires the new Phase-2 tools (run_local_scorer #782, build_plan/plan_status/ record_step_result #783, open_pr/file_issue/apply_labels/post_eligibility_ comment/create_branch/delete_branch #780) plus preflight/slop/predict-gate, and carries a 5-step driving loop — select reward-optimal work (respect the open-PR gate, credibility floor, time-decay) → plan a step DAG → harness implements locally → gate-check (scorer + slop + preflight) → push via the local write-tools only when the gate passes. formatAgentProfile renders the driving loop; the init-client note for an auto-dev profile reflects local execution after the gate (not the human-approved framing). Tests: the new profile round-trip (Phase-2 tools wired, driving loop present + gate-throttled, local-execution boundary + note, no token leakage). Existing profile tests unchanged (the new profile is intentionally NOT in the human-approved-only set). Full suite green (2118); CLI smoke + node --check ok. Note: the published MCP CHANGELOG is regenerated at mcp-release time (not a per-PR gate).
|
Note Gittensory Gate skippedPR closed before full evaluation. No late first comment was created.
💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. |
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #850 +/- ##
=======================================
Coverage 96.68% 96.68%
=======================================
Files 108 108
Lines 14609 14609
Branches 5288 5288
=======================================
Hits 14125 14125
Misses 105 105
Partials 379 379 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
gittensory · advisory review Reviewed 2 changed file(s) — two independent AI reviewers. Changed files: Suggested action: ✅ Safe to merge — both reviewers found no blocking issues. Reviewer A · Suggestions
Worth double-checking
Reviewer B · Suggestions
Worth double-checking
|
Closes #781
What & why
Phase 2 (#770) — final piece. Extends
init-clientinto a first-class auto-dev profile that wires the miner's local harness (Claude Code/Codex/Cursor) to the gittensory MCP + the plan→implement→push driving loop. With this, Phase 2 is complete.How
New
miner-auto-devagent profile in the published CLI (packages/gittensory-mcp/bin/gittensory-mcp.js). Unlike the existing human-approved-only profiles, it is gate-throttled:gittensory_run_local_scorer(feat(agent): local gittensor-root scorer MCP wrapper #782),gittensory_build_plan/plan_status/record_step_result(feat(agent): multi-step action DAG executor #783),gittensory_open_pr/file_issue/apply_labels/post_eligibility_comment/create_branch/delete_branch(feat(agent): miner write-tools (open_pr/file_issue/...) — local-executed #780), plus preflight / slop / predict-gate.formatAgentProfilerenders the driving loop; theinit-clientnote for an auto-dev profile reflects local execution after the gate (not the human-approved framing of the other profiles).Boundary
Every GitHub write is run by the miner's own harness with its own credentials via a write-tool's returned command — gittensory supplies content + the gate only, never performs the write, never sees source.
Tests
The new profile round-trip (Phase-2 tools wired, driving loop present + gate-throttled, local-execution boundary + note, no token leakage). Existing profile tests unchanged (the new profile is intentionally not in the human-approved-only set). Full suite green (2118); CLI smoke +
node --checkok.Note: the published MCP CHANGELOG is regenerated at mcp-release time (not a per-PR gate), so it's intentionally untouched here.