Repository navigation
feat: add Neovate Code terminal harness - #8209
milesatao-svg wants to merge 28 commits into
Conversation
Move the unmerged harness migration to unused 209 and recover requested_output for historical Neovate databases that burned main migration 195. Preserve all harness-owned evidence.
Build the real daemon in PR CI for isolated VPS runtime verification without local validation suites or dependency installations. Record source revision, Go build info, and executable hash.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… /login - Model catalog lists every built-in Neovate v0.28.5 provider model, defaulting to configured or keyed providers (env vars or native /login). - Seed AO's model through the plugin config hook instead of --model, which disabled native /model for the whole session. - Configure opens Neovate and sends /login once the TUI is ready. - Add the official Neovate mark and show a saved credential as Connected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copied source evidence 1/3Historical material from original PR #6494, copied for this account migration. Source PR head when copied: Original comment by @nikhilachale on 2026-10-10T07:49:54ZEvidence correction from the skill packaging review: the historical Neovate Code 0.28.5 — VPS audit report, 2026-10-10 Functional lifecycle: 17/17 PASS. CI on the audited commit: 24/24 PASS. Overall audit: BLOCKED. This is diagnostic lifecycle coverage; a full strict audit PASS is not claimed. Audited commit: Gate totals: 25 PASS, 2 NOT_RUN, 1 BLOCKED. These are gate counts, separate from the 24 CI checks. Local CLI
AO / AOS11
Cross-check
AO reports credentials as configured, not provider-verified. Real Z.ai calls succeeded, so this metadata gap is not evidence of an expired login. The inspected native CLI exposes no supported model-list command; native listing/exact catalog comparison remain NOT_RUN. No Neovate production change was required during the VPS audit. Earlier continuation was sent before the restored native UI mounted. A controlled same-session retry and final attempt 3 waited for the real native composer and verified the original history, proof-file fields and refreshed standing instructions. Cancellation used Neovate's Escape key through AO's actual terminal WebSocket mux. The original strict skill remains unchanged. The separate diagnostic runner continues lifecycle testing only after successful direct native proof and AO installation/freshness checks; it retains the original non-passing auth/model gates. The runner revision used here passed 80/80 fixture tests; subsequent generic improvements passed 91/91. Audited-head backend/aggregate CI · Pinned released-native conformance Cleanup confirmed: the created session was terminated and the isolated daemon/native PTY processes stopped. A final audit-wide process scan found no remaining owned test processes. Credentials and raw native IDs are omitted here. Previous failed attempts and controlled comparisons remain preserved in the audit bundle. Real terminal text was captured; screenshots, Electron UI and native non-Linux harness coverage are not claimed. Evidence identity
Original comment by @nikhilachale on 2026-10-10T09:01:33ZEvidence correction from the skill packaging review: the historical Neovate 0.28.5 — failed-attempt report, 2026-10-10 The original failures remain preserved even though the final diagnostic run passed all 17 lifecycle gates. The full strict audit remains BLOCKED: AO reports configured credentials, and native model discovery/comparison are NOT_RUN. See the final gate-by-gate report. All times below are UTC on 2026-10-10. Testing ran on the Ubuntu VPS, with real Z.ai calls; no local Mac checks were run.
Original failed gate reasons included: Those downstream failures mean continuity was not proven in those attempts; they do not demonstrate that native history was deleted. The successful same-session control and final attempt provide separate positive continuity evidence. Remaining gaps: configured credentials are authorized for this audit but still not classified as provider-verified by AO; this is not an expired-login finding. Local model listing and exact catalog comparison remain NOT_RUN because no valid native model-list contract was supplied. Screenshot coverage: the historical attempts have real terminal text/ANSI captures, but no PNG screenshots. No rendered log or recreated error image is claimed as an original screenshot. Evidence paths above are relative to the preserved VPS report directory Original comment by @nikhilachale on 2026-10-10T09:56:18ZThe reusable integration/testing skill and consolidated session report are now in #6509.
The report includes two redacted, actual screenshots from the new Open Interpreter early-send reproduction; they are published repository evidence, not historical screenshots of Tau or Neovate. Original captures remain unchanged. The historical instruction-refresh correction remains explicit: the old Original comment by @nikhilachale on 2026-10-10T18:41:17ZFresh current-runner VPS follow-up: Neovate Code 0.28.5 / Z.ai aozai/glm-5.3-flash / TUI finished Fresh restore-only instructions were introduced after confirmed kill, written/read back through the project API, then consumed after the same native-ID/workspace restore. An end-anchored cue established the initialized empty composer with configured model and exact audit workspace before continuation. Mutation/history/fresh instructions passed. Cancellation proves the observed active-turn Escape→settled transition; it does not prove already-running subprocess reaping. Functional source Actual AO Electron/preload bridge and exact session selected, source-matched UI; actual scrot/Xvfb at Curated gates, exact provenance/native fingerprint and cleanup. Historical failures remain unchanged. Historical 17/17 label did not prove fresh instructions; older native mirrors did not qualify as AO UI. Original preflight auth screenshot unavailable because no session existed. Cleanup complete: audited session API-killed/termination confirmed; exact main Electron and current run-file daemon gone; exact GUI scratch auth PTY host terminated after it survived daemon shutdown. The first incomplete cleanup and GPU-PID rejection are retained. Unrelated AO/native processes and regular data untouched. Final evidence-head CI verified at Original comment by @nikhilachale on 2026-10-12T16:52:27ZHarness-specific reports, JSON receipts, screenshots and provenance now live on this integration PR branch, rather than the skill PR #6509. Evidence index with embedded screenshots and JSON links. Historical successes, failures and scope limitations remain as recorded. Moving these files does not rerun native/AO testing or upgrade any verdict. This is evidence relocation only. Existing tested source/native hashes and failures are preserved; the documentation commit is not a fresh runtime pass. Applicable checks run in PR CI. Original comment by @nikhilachale on 2026-10-12T18:13:51ZCanonical main conflicts reconciled at Validation is PR CI only; current-head checks are pending until GitHub reports them. This merge does not constitute a new native/AO run or promote historical fresh/restore/provider-role proof. Harness evidence stays on this integration PR; PR6509 remains reusable guidance and linked summaries. Original comment by @nikhilachale on 2026-10-12T18:18:19ZCanonical main conflicts reconciled at Validation is PR CI only; current-head checks are pending until GitHub reports them. This merge does not constitute a new native/AO run or promote historical fresh/restore/provider-role proof. Harness evidence stays on this integration PR; PR6509 remains reusable guidance and linked summaries. Original comment by @nikhilachale on 2026-10-12T20:57:37ZCanonical main conflicts reconciled at Validation is PR CI only; current-head checks are pending until GitHub reports them. This merge does not constitute a new native/AO run or promote historical fresh/restore/provider-role proof. Harness evidence stays on this integration PR; PR6509 remains reusable guidance and linked summaries. Original comment by @nikhilachale on 2026-10-12T22:55:31ZNeovate actual AO evidence is owned by this integration PR at Original comment by @nikhilachale on 2026-10-18T17:40:25ZContinuing this existing draft on the VPS. Live head is Plan: (1) finish that ancestry-preserving merge, (2) inspect current official Neovate release/source for real ACP initialize/load/resume and additive plugin support, (3) only if mandatory exact restore is supported, add a thin nativeacp/persistenthost binding and meaningful regression tests, then qualify real native and AO Chat behavior, (4) otherwise keep Chat gated and publish the precise upstream blocker. Routine suites run in PR CI only. No new evidence files, no PR6509 activity, no merge/release/deploy. Current free disk is 229 MiB; avoid allocations until native viability is known. Historical TUI receipts do not establish Chat conformance or executing-child interruption. Original comment by @nikhilachale on 2026-10-18T17:42:57ZBLOCKED — native ACP exact restore is unavailable; draft retained. VPS-only bounded investigation on 2026-10-18T17:42:57.252651+00:00. This is not READY_FROM_OUR_SIDE. Live PR head Supported scope remains the existing terminal harness. There is no registered Neovate Chat binding. Shared nativeacp/persistenthost was inspected and left unchanged. A fresh native conversation must never masquerade as load/resume.
Sanitized first-failure receipt, from the installed released executable, not source inference: {"method":"initialize","result":{"protocolVersion":1,"agentCapabilities":{}}}
{"method":"session/load","error":{"code":-32603,"message":"Internal error","data":{"details":"Method not implemented."}}}
{"method":"session/resume","error":{"code":-32603,"message":"Internal error","data":{"details":"Method not implemented."}}}
{"method":"authenticate","error":{"code":-32603,"message":"Internal error","data":{"details":"Method not implemented."}}}Native executable Current-head CI observation:
Required external change: a supported first-party native ACP release implementing deterministic persistent session load/resume, workspace/history validation and replay. Current master has no such implementation; a future source patch/fork must stay explicitly gated until qualified. After that, rerun all real native/AO Chat gates including independent additive plugin consumption and direct screenshot attachment. This report retains the original implementation failures and does not upgrade any historical TUI result. Original comment by @nikhilachale on 2026-10-18T17:44:42ZBLOCKED; not READY_FROM_OUR_SIDE. Final current head The full gate table, exact released-native fingerprint, sanitized first failures, UI/attachment gaps and cleanup remain applicable: stock Neovate 0.28.5 ACP initializes with empty capabilities, then both session/load and session/resume unconditionally return A subsequent genuine CI failure was investigated and repaired in
Exact current-head workflow observations:
Cleanup remains complete for the exact owned ACP process; no AO daemon/Electron/foreground child was launched, and no production or unrelated processes/data were changed. Historical evidence and first failures remain intact. No new report/evidence assets in Git, no PR6509 modifications/comments, no merge/release/deploy. External action: qualify a first-party ACP load/resume implementation/release (or separately gated upstream fix), then run the full native/Chat instruction, permission, executing-interrupt/Kill, exact restore/reconnect, UI attachment and independent review gates. CI completion remains separately pending. Original comment by @nikhilachale on 2026-10-18T21:55:56ZReconciliation pass only. Refreshed live head Original comment by @nikhilachale on 2026-10-18T21:58:36ZRECONCILED — reconciliation pass complete; ACP readiness is not claimed. Pushed normal merge Conflict decisions: retain both Neovate and main’s Memcode registration/activity/catalog enums and independent selection tests; combine DTO/generated API harness enums; retain ledger 209 alongside main’s 210–212 and preserve every burned entry. Main does not own migration 209; no merged migration was modified. Keep main’s account/lifecycle changes and Neovate’s native cancellation/environment propagation. API generation exposed a duplicate auto-merged LaunchConfig.Env and missing environment arguments in newer interactive restore/account-switch paths; these were reconciled to use the selected launch/account environment. No whole-file ours/theirs replacement.
Current-head checks:
Cleanup: parent removed only verified unused ignored historical node_modules, disposable npm cache and two superseded unused Codex vendor versions; affected checkout status and lockfile hashes were unchanged. No additional cleanup performed here. Historical code/evidence/history/screenshots and first failures preserved. No new report/evidence files, dependency installation, native/AO/UI runtime, production mutation, or PR6509 activity. API generation used existing tools; about 1.9 GiB disk remains. No owned live runtime processes were started to clean up. Draft retained. ACP implementation and full current-head CI qualification belong to the following ACP pass; this is not READY_FROM_OUR_SIDE. Original comment by @nikhilachale on 2026-10-18T22:57:52ZContinuing ACP on the VPS at Plan: (1) repair current-head CI reconciliation defects: install inventory coverage and a Memcode negative fixture that unintentionally lacks Neovate; (2) inspect latest official release/current upstream ACP plus supported SDK/plugin restore paths, retaining exact native identity and replay requirements; (3) qualify additive plugin delivery independently where native permits, and keep Chat unregistered unless real gates pass; (4) submit reviewable source/tests to CI, refresh both branches before push/final publication, and report exact remaining native/UI gates inline. No routine suites on VPS, no evidence files committed, no PR6509 activity, no production mutations. Original comment by @nikhilachale on 2026-10-18T23:04:55ZFresh ACP investigation on VPS, source Real provider Controlled attempt 3 native conversation SHA256 First failures retained: attempt 1 probe refused an unimplemented fs/read_text_file client callback and cleaned up; attempt 2 added workspace-bounded filesystem callbacks and produced the three files, but its strict JSON reader failed on native plain stdout. Attempt 3 separately captured that line and collected final native errors. Owned PID/birth witnesses: attempt1 Source progress: fixed both current-head CI reconciliation regressions, explicit Neovate Chat rejection regression, and remote-only pinned-release additive plugin fixture. Independent read-only source review found no actionable defects; no local suites ran. Following the newly observed native stdout defect, the fixture is being scoped explicitly to provider request construction (additive private/default/project prompt composition), not completed ACP protocol conformance. Chat stays unregistered and PR draft; exact restore, NEW instructions after Kill, reject/cancel, executing interrupt/Kill, reconnect/replay and actual AO Chat/UI remain unqualified. No real AO UI screenshot exists for unsupported Chat; screenshot unavailable. All current-head CI remains separately pending and will be read at the final head. |
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
Copied source evidence 2/3Historical material from original PR #6494, copied for this account migration. Source PR head when copied: Original comment by @nikhilachale on 2026-10-18T23:08:38ZBLOCKED — source progress pushed; not READY_FROM_OUR_SIDE. Draft retained; Neovate Chat stays unregistered. Current released native ACP lacks exact load/resume and contaminates protocol stdout. Fresh private additive instructions now independently proven in native ACP; restore instruction refresh remains unproven. Current head Implemented reviewable progress:
Sanitized live receipts, first failures and native/source analysis remain inline. Real-provider proof used stock Current upstream source
First failures remain preserved: probe 1 refused unsupported client fs callback; probe 2's strict JSON reader exposed native plain stdout after creating requested files; controlled probe 3 retained the offending line and collected exact load/resume errors. These diagnostic probes are not AO Chat qualification. Historical reports/assets and their earlier failure corrections are untouched. Exact-head workflows (queried for
Published job snapshot (Go workflow pending may not yet expose job check-runs):
No failure conclusion exists yet on this final head at publication. The earlier Cleanup: all exact owned native PIDs/births verified absent ( Remaining external/native blocker: supported exact ACP load/replay with permission-preserving session ownership and clean JSON-RPC output. After that, qualify fresh NEW instructions after Kill, reject/cancel, executing interrupt and AO Kill/control, exact missing history/workspace, reconnect/replay, supported options, actual AO Chat screenshots/direct attachment and independent full review, plus all final-head CI. Checkpoint verdict blocked; supervisor may advance without interpreting this queue exit as readiness. Original comment by @nikhilachale on 2026-10-21T05:49:14ZFresh testing-only retest starting for Original comment by @nikhilachale on 2026-10-21T06:01:07ZBounded fresh harness retest — Neovate / PR #6494 — 2026-10-21T06:00:54.560773+00:00 Verdict: FAIL. Strict TUI audit: FAIL. AO UI capture and attachment evidence: BLOCKED. Full integration PASS is unavailable. Tested source: Native Model/provider: Attempts and first failures (UTC):
Independent native witness: 75-second timeout, no output and no matching file; stdout/stderr SHA256 each Native ACP returned an empty agentCapabilities object and one available/current model Strict result (
No diagnostic runner attempt: native direct file proof failed, so diagnostic prerequisites were not met. Missing native model-list CLI stays NOT_RUN; no command was invented. Safe independent daemon API receipt (05:56 UTC): AO read-only offers: installer uses Completion matrix:
Screenshot checkpoint index (all required rows, plus explicit Chat/reviewer subjourneys): U1 = actual current-head Electron setup BLOCKED by capacity. Fresh A1 = no approved working GitHub attachment uploader. AO UI attachment evidence: BLOCKED. Private attachment queue exists with zero PNG entries; no fake image URLs or substitute images. No checkpoint counts as published screenshot proof. No capture timestamp/session/generation is asserted for a nonexistent image.
Current-head CI (GitHub only; no local unit/race/lint/vet/typecheck/build-fixture/runner-fixture suites executed): 26 check runs, all completed/success, no failing or pending check runs. Legacy combined-status endpoint returns
GitHub merge state: Safe reproduction (paths intentionally generic; no installation/login): export GOMAXPROCS=1 GOFLAGS=-p=1 GOMEMLIMIT=384MiB
export NODE_OPTIONS=--max-old-space-size=384
export HOME="$RUNTIME/native-home" USERPROFILE="$RUNTIME/native-home"
export TMPDIR="$RUNTIME/tmp" NEOVATE_SELF_UPDATE=none
node "$STAGED_SKILL/scripts/audit_ao.mjs" --agent neovate \
--repo "$TESTED_SOURCE" --ao "$RUNTIME/bin/ao" \
--local-contract "$RUNTIME/native-contract-001.json" \
--report "$RUNTIME/attempts/NEW-ATTEMPT/report" \
--timeout-seconds 35 --startup-timeout-seconds 60Runtime contract SHA256: Cleanup and retained data: strict daemon PID 1463726 and independent API daemon PID 1464353 each exited 0; all native/ACP/npm launches reaped. Exact owned PID/kernel-start/process-group inventory found zero remaining processes at 2026-10-21T05:57:45.551997+00:00. No provider AO session was created; no Kill/restore/cancellation lifecycle claim follows from daemon cleanup. Worktree clean. Private runtime retains strict JSON/Markdown/issues/logs, API/native/ACP receipts, protected isolated profile, binary, workspace and empty attachment queue outside every Git checkout. No new evidence commit, pushes, merges, old-comment edits, provider installs, account resets, production changes or external reviewer publication. Parent final owned-process verification/worktree removal remains separate. Unresolved next actions: establish a successful independent native provider/file witness without changing accepted account state; resolve AO configured-only readiness in an authorized product-work scope; derive real native composer/restore/interrupt evidence before lifecycle work; qualify required Chat/reviewer scope independently rather than inferring it from TUI; provision sufficient isolated UI disk capacity, capture every action/result and have the parent attach reviewed PNGs using an approved route; resolve PR conflicts outside this testing-only worker. Current PR contains historical committed evidence, which was not reused or modified here. PR-description link to this new evidence comment is pending for parent; description was not edited. No full integration completion claim. |
Copied source evidence 3/3Historical material from original PR #6494, copied for this account migration. Source PR head when copied: Original comment by @nikhilachale on 2026-10-21T06:02:00ZFinal evidence copy for exact readback. First fresh evidence comment remains unchanged. Its readback changed only textual Escape notation; this copy uses hexadecimal notation. These are the same test attempts, not a rerun. Bounded fresh harness retest — Neovate / PR #6494 — 2026-10-21T06:00:54.560773+00:00 Verdict: FAIL. Strict TUI audit: FAIL. AO UI capture and attachment evidence: BLOCKED. Full integration PASS is unavailable. Tested source: Native Model/provider: Attempts and first failures (UTC):
Independent native witness: 75-second timeout, no output and no matching file; stdout/stderr SHA256 each Native ACP returned an empty agentCapabilities object and one available/current model Strict result (
No diagnostic runner attempt: native direct file proof failed, so diagnostic prerequisites were not met. Missing native model-list CLI stays NOT_RUN; no command was invented. Safe independent daemon API receipt (05:56 UTC): AO read-only offers: installer uses Completion matrix:
Screenshot checkpoint index (all required rows, plus explicit Chat/reviewer subjourneys): U1 = actual current-head Electron setup BLOCKED by capacity. Fresh A1 = no approved working GitHub attachment uploader. AO UI attachment evidence: BLOCKED. Private attachment queue exists with zero PNG entries; no fake image URLs or substitute images. No checkpoint counts as published screenshot proof. No capture timestamp/session/generation is asserted for a nonexistent image.
Current-head CI (GitHub only; no local unit/race/lint/vet/typecheck/build-fixture/runner-fixture suites executed): 26 check runs, all completed/success, no failing or pending check runs. Legacy combined-status endpoint returns
GitHub merge state: Safe reproduction (paths intentionally generic; no installation/login): export GOMAXPROCS=1 GOFLAGS=-p=1 GOMEMLIMIT=384MiB
export NODE_OPTIONS=--max-old-space-size=384
export HOME="$RUNTIME/native-home" USERPROFILE="$RUNTIME/native-home"
export TMPDIR="$RUNTIME/tmp" NEOVATE_SELF_UPDATE=none
node "$STAGED_SKILL/scripts/audit_ao.mjs" --agent neovate \
--repo "$TESTED_SOURCE" --ao "$RUNTIME/bin/ao" \
--local-contract "$RUNTIME/native-contract-001.json" \
--report "$RUNTIME/attempts/NEW-ATTEMPT/report" \
--timeout-seconds 35 --startup-timeout-seconds 60Runtime contract SHA256: Cleanup and retained data: strict daemon PID 1463726 and independent API daemon PID 1464353 each exited 0; all native/ACP/npm launches reaped. Exact owned PID/kernel-start/process-group inventory found zero remaining processes at 2026-10-21T05:57:45.551997+00:00. No provider AO session was created; no Kill/restore/cancellation lifecycle claim follows from daemon cleanup. Worktree clean. Private runtime retains strict JSON/Markdown/issues/logs, API/native/ACP receipts, protected isolated profile, binary, workspace and empty attachment queue outside every Git checkout. No new evidence commit, pushes, merges, old-comment edits, provider installs, account resets, production changes or external reviewer publication. Parent final owned-process verification/worktree removal remains separate. Unresolved next actions: establish a successful independent native provider/file witness without changing accepted account state; resolve AO configured-only readiness in an authorized product-work scope; derive real native composer/restore/interrupt evidence before lifecycle work; qualify required Chat/reviewer scope independently rather than inferring it from TUI; provision sufficient isolated UI disk capacity, capture every action/result and have the parent attach reviewed PNGs using an approved route; resolve PR conflicts outside this testing-only worker. Current PR contains historical committed evidence, which was not reused or modified here. PR-description link to this new evidence comment is pending for parent; description was not edited. No full integration completion claim. Original comment by @nikhilachale on 2026-10-22T00:20:09Z
|
🏆 Review leaderboardNov 5–12, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 6 more reviewers
|
Account migration verification
|
Resolve 23 conflicts against main adf9f6a: - harness lists: keep Neovate alongside main's Hermes everywhere - session manager: keep main's launchPath/nativeRestoreMetadata and its existing Env plumbing; drop the PR's now-duplicate RestoreConfig.Env and LaunchConfig Env keys; keep the PR's env on preflight and native restore - schema repair: keep both 0195 (Neovate fork) and 0199 repairs; normalize Neovate out before exact historical repairs and re-append it last, as main does for Hermes - settings UI: keep main's unverified/renewal auth states; Neovate's saved credential still reads "Connected" via the existing loggedIn key, so the PR's duplicate settings.harness.connected strings are dropped - schema.ts: main's generated file plus Neovate in the three harness enums - add Neovate to main's new exhaustive doctor, shell-agent and tone maps Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Neovate 0.28.5 reads 28 provider key variables, but AuthStatus checked only eight, so a MiniMax (MINIMAX_API_KEY) or other env-only provider read as unconfigured. Check the full pinned registry list, and offer Neovate's main provider keys (including MiniMax and Z.ai) in AO's provider-key setup, which main's exhaustive setup-method test requires. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Main now allocates UTC-timestamped migration IDs. Retire the unmerged 0209 candidate the same way main retired Hermes' 0203: reserve 209 in the ledger and burnedVersion, and add 20261114173957269, ordered after main's latest 20261114072016988. The new migration follows the Hermes template: Up is idempotent, so pre-merge installs that already applied 0209 pass through it, and a schema guard fails loudly on an unrecognized constraint. Down refuses while Neovate rows exist and removes Neovate wherever it sits, instead of assuming it immediately precedes 'fake'. Verify Neovate last in the schema repair, matching its append order, so the Memcode negative fixture still reports Memcode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Neovate's catalog includes every built-in provider's models, which stay selectable until native /login stores a key, so treat it as a multi-provider harness and do not hide its catalog behind setup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Current-head reconciliation and ao-agent-harness receiptHead: Changes in this pass
Provider compatibility (pinned @neovate/code 0.28.5 registry)
Neovate 0.28.5 does not read Skill steps
Validation
Still a draft. This is not ready to merge: it still needs CI, a fresh review, maintainer approval and the live and UI audits. |




Code changes: +904 -29
Tests: +1138 -5
Others: +16 -3
What
feat: add Neovate Code terminal harness
Original PR description, preserved
Binary assets in current PR diff: 9.
Adds the pinned native Neovate terminal integration with additive AO plugin instructions and preserved native/user/project controls. Chat, reviewers and cross-interface handoff are unsupported.
Actual AO audit is mixed: primary fresh private/project/user actions passed; a separate fresh private action failed. Exact restored NEW-token consumption failed despite read-only native composed-system configuration containing NEW only. Executing Escape failed to settle. Independent AO Kill and specific missing-transcript rejection passed. Earlier invalid overlapping controls and blank frames are retained separately.
Harness-owned report and receipts. Runtime and UI source were
6be36883; evidence commits do not relabel the executable. Stock @neovate/code0.28.5 matched all12 released package files. Authenticated third-party wire role NOT_CAPTURED.PR remains draft. Native ACP load/resume are unimplemented in released 0.28.5 and current upstream. Current batch status and exact-head CI. GitHub CI only. Historical evidence below remains unchanged.
Latest reconciliation pass and current-head CI. ACP readiness remains unqualified.
Latest ACP source progress, native blocker and final-head CI. Chat remains unregistered; draft retained.
Current-main recheck (2026-10-21): merged
7c83bd68c1and explicitly disabled unattended terminal version refresh until exact-conversation restore is qualified. CLI/daemon checks on8d1c3ac3c7installed Neovate 0.28.5 successfully, opened the native provider chooser (an additional Enter was needed in the terminal check), listed a configured project model, and created a standalone TUI task through the New task API. The fresh task exited because no native model was configured. The existing configured-provider credential returned HTTP 401. A successful authenticated task response is not verified. The follow-up commit only adds the disabled refresh capability and its matrix expectation; draft retained.Why
The contributor is moving this harness submission to @milesatao-svg. The linked source preserves the implementation and review history.
Before / After
116129b6c81f111e65b82b1c24a86e07dc07c2f2116129b6c81f111e65b82b1c24a86e07dc07c2f2Original product behavior and existing UI evidence are included in the preserved description and copied evidence comments.
How
Copy the source head into
milesatao-svg/agent-orchestrator:codex/copy-pr-6494-neovateand target upstreammain.Testing
Historical test results and screenshots are reproduced in the evidence comments with their original sources. Fresh validation is tracked by this PR's GitHub checks.
Checklist
Account migration verification
116129b6c81f111e65b82b1c24a86e07dc07c2f2.milesatao-svg/agent-orchestrator:codex/copy-pr-6494-neovate. Base:main.