Skip to content

feat: complete remaining native project client E2E - #520

Draft
777genius wants to merge 23 commits into
mainfrom
feat/project-native-e2e-remaining-20261025
Draft

777genius wants to merge 23 commits into
mainfrom
feat/project-native-e2e-remaining-20261025

Conversation

@777genius

@777genius 777genius commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

Problem and current owner scope

Project-scope installation landed in #499 and capture cleanup in #519. This program completes source-bound native E2E coverage for the remaining clients while preserving Claude/Codex/OpenCode and user-scope behavior.

Owner update, 2026-10-27: VS Code is deferred and skipped. Complete the nine active leaves #521–#529. Keep #530 as a deferred draft and preserve its existing source, evidence and unpublished work. New VS Code qualification and merge are outside this continuation; its incomplete qualification does not block the active program. Existing baseline regression coverage remains intact. This decision is recorded in the owner scope and both consolidated plans by 443fa8d, a reviewed three-file documentation-only change.

Shared implementation and gates

  • Official pinned acquisition and complete runtime identity, bounded ordinary archive inventory, genuine disposable GitHub-hosted admission, and exact clean source commit/tree.
  • Original user authority separate from real projects A/B and outside cwd. Public CLI lifecycle actions retain source, ownership and data receipts.
  • Bounded capture, private-token redaction, closed evidence admission, original deadlines and complete process cleanup.
  • Research, a single installed exchange, full lifecycle, native restart/removal, MCP initialization/list/call, vendor authentication and real-model use remain separate claims.
  • Two independent plan reviews precede implementation; independent code critics review the actual candidate and fixes before incremental publication. Existing runtime failures are never relabelled as passes.

Active leaves — source-bound checkpoint, 2026-10-27

Client PR / current published head Verified progress and remaining gate
Cursor #521 / 86730e8 The genuine pinned official acquisition again returned HTTP 403 before binary bytes or execution. Acquisition remains blocked.
Grok #522 / b4a2d5d Public add and native inspection join the exact disabled, untrusted Prepared candidate. Ordinary startup reaches vendor sign-in. A documented custom-provider observation is now separately planned and reviewed; it has not run. Project MCP remains unsupported.
Qoder #523 / c14b497 The new bounded diagnostic identifies the owned original-profile entry logs/latest as a symlink before catalog/startup. Its target is not yet observed. A narrow no-follow inventory amendment is under review; complete profile preservation remains mandatory.
Kimi #524 / 55f5d84 Published schema, Windows-path and context corrections are preserved. Actual public installation and receipt proof pass; both native API attempts then fail before useful private captures. Reviewed finite stage/category/actual-cleanup diagnostics are now published; new native jobs are pending.
Cline #525 / 9d01aef Fresh genuine installed ACP exchange passes in run 40456413669. Closed native/provider/probe evidence joins the exact installed root/data, session and one MCP call, with ordinary cleanup. Full user/A/B/update/repair/restart/removal coverage remains the next slice; all five lifecycle/MCP qualification flags and vendor/model flags remain false.
Gemini #526 / c887f66 Exact observed synthetic signature and separate HTTP/native call IDs are implemented from pinned source and retained request2. The exact measured skills-refresh diagnostic is admitted only for its successful fixed command. Both slices passed independent reviews, inert tests and applicable lint; fresh native results are pending.
Copilot #527 / f7421c5 Runtime expectation now matches the measured native expansion against held original HOME, preserving the materialized literal. Finite strict-JSON refusal diagnostics are published; the separate original-config preservation failure stays fatal. Fresh native result pending.
Windsurf / pinned Devin CLI #528 / 370be21 Published Windows fixture corrections are preserved. Actual startup reports login cancellation and a changed original config digest. Reviewed bounded hash/type/equality diagnostics are published; the guard and all qualification flags remain unchanged. New native result pending.
Kiro #529 / 6e99cbe Public Prepared installation and receipt proof pass. Native read-only and startup captures reach the account boundary. No native source-selection, full lifecycle, restart/removal or MCP qualification is claimed.

These leaves remain drafts while their applicable gates are unproved. VS Code #530 is a preserved deferred draft, not an active completion dependency.

Recent reviewed validation

Cline's exact measured grammar contracts, real captured-stream replay and shared Python closure tests pass; both affected lint gates report zero issues. Its fresh source-bound native archive is independently verified as a closed 21-member success with ten ACP frames and three correlated probe events. The frontend has a closed 31-member capture with matching command streams and no forced stop/kill. This proves the single installed exchange only.

Copilot focused inert contracts pass in 0.033 s, with zero affected/all-file lint findings. Kimi's 47 collector/attempt/service inert tests pass in 16.404 s. Windsurf focused/shared CLI contracts pass in 0.016 s, all 18 shared Python tests pass, its retained failed artifact replays unchanged, and both lint gates report zero issues. Gemini's 31 research contracts pass in 0.388 s; provider contracts plus exact retained request2 replay pass in 0.013 s, the final affected cases pass in 0.011 s, and both lint gates report zero issues. These local checks ran no vendor executable.

The preceding executable program head b16b5c5d28cdc734856ac414521d40d9c8d8dfd5 has successful Required CI 40392785306. Current parent 443fa8d adds only the owner-scope documentation notice. Client checks remain bound to each actual leaf source; a green research or fixture job does not satisfy missing native proof.

Preserved earlier shared corrections

The program retains the independently reviewed Darwin completed-process cleanup correction from 2f7a885ec00622cb500ca1189b93659ca5bd9216. Its motivating failure was Gemini baseline job 121728625314. The correction accepts only an exited original child plus confirmed absence of its original process group and sends no destructive retry. Twelve inert capture and twelve service tests passed; both critics approved tree 30d2c7b3cc963029c48ec4e6ac0675a2cb9307e1. Preserve the Go 1.22 fixture corrections, adapter-based version dispatch and strict architecture gates as well.

Completion and merge

The governing source plan is docs/plans/project-install-e2e/remaining-native-qualification.md, with the latest VS Code deferral at its top. Active-client evidence still requires public user/A/B lifecycle, unchanged reconciliation, explicit update, exact-pin repair, native restart/removal and separately correlated MCP operation where supported. Explicit authentication/capability boundaries stay visible and unqualified.

Merge each applicable reviewed leaf into this program only after its current-source checks and evidence pass. Then refresh main, review the combined source, run the affected final gates and merge this PR with expected-head protection. Workers/reviewers use the owner's GPT-6.1 Sol/xhigh selection. No release publication is included.

@coderabbitai

coderabbitai Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codecov

codecov Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.87%. Comparing base (d5c1685) to head (443fa8d).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #520   +/-   ##
=======================================
  Coverage   60.87%   60.87%           
=======================================
  Files        1776     1776           
  Lines      105136   105136           
=======================================
+ Hits        64000    64003    +3     
+ Misses      31946    31944    -2     
+ Partials     9190     9189    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

…efusal

Apply the twice-reviewed Darwin cleanup correction without a destructive retry after reaping. Preserve ordinary permission failures, shared service refusal rules, deadlines and stream bounds. Add deterministic absence/refusal tests while retaining real-process capture contracts.

Copy link
Copy Markdown
Owner Author

@coderabbitai full review

Owner requested independent review before merging this program and its existing children #521–530. Current observed parent head: b16b5c5d28cdc734856ac414521d40d9c8d8dfd5. Review only: no autofix, branch edits, ready-state transition, auto-merge, merge or release.

Review shared acquisition/source identity, exact test selection, immutable runtime pins, original-user/project separation, process cleanup, budgets, closed/redacted artifact admission and concurrency isolation. Preserve legacy Claude/Codex/OpenCode behavior and solver/store/receipt/transaction/security mechanisms. The leaf branches are not merged: do not treat this parent as containing their implementation or combine old-source proofs into current-source qualification. All applicable leaf native gates and subsequent combined-head checks remain necessary. Please anchor findings to reviewed source and report concrete correctness/security or validation gaps rather than speculative refactoring.

@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
⚠️ Action not completed

Review rate limited.


Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 59 minutes.

@777genius 777genius left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge-readiness review — NO-GO, 2026-10-27 05:28 UTC

This is a source-bound CI/evidence/readiness review, not approval of every changed line. No branch/ref/checkout changes, auto-merge, ready-state transitions, release, or blind CI retries were made. Root coordination checkpoint is unavailable in this execution environment; external Cline commits confirm ongoing work, so competing source edits were deliberately avoided.

Independent review actually obtained

  • Manual CodeRabbit full review was requested on each existing PR #520–530, without enabling autofix.
  • #524 at a4a211d60595abbb8592e76e27846ba6c349a6d0: CodeRabbit completed its 39-file review with no actionable code findings (#524 (comment)). This is not native qualification. Current-source Core fast, Terminal UI, and legacy Native Client Runtime are successful; Project Native Runtime 40452608070 failed in both Kimi cases.
  • Further full-review requests encountered CodeRabbit's included review limit; #521 explicitly reports it (#521 (comment)). Do not treat a skipped/limited review as approval or keep retriggering it.
  • For #526, CodeRabbit independently confirmed the pinned-source parser issue and gave ONE constrained plan GO (#526 (comment)). Codex could not supply a second decision because its review allowance is exhausted (#526 (comment)). The plan is therefore NOT fully approved for implementation.

New exact Gemini finding and plan checkpoint

At eef6c202abf02489338db54c0ffbb9cb2c283ca6, provider-request-2 in native artifact 12698460531 has the observed model functionCall plus thoughtSignature: "skip_thought_signature_validator". Outer SHA-256 independently verified: 0aba508ca5cbaebc1054a04654d6afc6b534ecdc298b91497a14857cecb03cc0. geminiProjectContents rejects this at line 44 (len(part) != 1), causing Gemini part union before the returned tool result can be joined. Exact vendor source 6006c14a4decfe4b891c6263ad6ad5992e404b5b, historyHardening.ts blob d58274161f6075f29b62ea7aabc4cdcb54e02148, confirms the field and literal.

Plan: #526 (comment); focused inline review 5662606701. Incorporate the independent review constraints: exact key sets and explicit model role; normal/countTokens history versus systemInstruction must be separated; no arbitrary metadata, no alteration of issued call/result identity or wait_for_previous schema. Preserve the current no-metadata cases. Do not claim the existing flattened parser already proves full role/order grammar. Obtain the second independent decision before implementation, then code review and fresh hosted proof. No qualification flags have been raised.

Preserve fresh external Cline fixes; do not repeat stale lint work

#525 advanced from 6b76908e9b7284d9a1a5fd7eea438aa833687503 through dab49d096636afa7052b6ec2264fd160badb6ca9 to 8d278b1d0766931be192447733e1e8ffbd0167b5. The exact two-commit delta fixes the ten old lint issues, preserves ACP cancelled, context-aware HTTP/listener calls, checked snapshot cleanup and original event-order cases. Those are external commits, not changes made by this review.

Current 8d278b1 legacy Native Client Runtime 40453453993 has a separate Windows Codex MCP failure. Job 122021520006 and artifact 12711451552 were read; outer SHA-256 verified 13e51312b86855b1dbbdb13b8cce78b7c0108b953424bc8a5f592eb27bacdb2e. In trusted-add-rpc.jsonl, the first mcpServerStatus/list returns default: starting and explicit: connected; only explicit has emitted startupStatus: ready. The test immediately requires both connected and fails before any tool call. This establishes the observed readiness boundary, not a proven persistent vendor failure, nor a defect caused by the Cline-only lint delta. Do not accept starting as success or rerun blindly. Other three Codex native tests in that job passed; five other legacy matrix jobs passed. The Cline-specific Project Native Runtime 40453454042 also remains failed.

Observed current-head qualification gates

PR Observed head Relevant gate
#521 Cursor 86730e880ff4da254e9111c5703e26eba02cf993 acquisition/research 40235265317: failed; no acquisition/native proof
#522 Grok b4a2d5dea1cc2cd9a0165660924732ec6e1df811 native 40408742120: failed
#523 Qoder 0d1bfa7225937f4f581958022ef103200ee14301 native 40408766184: failed
#524 Kimi a4a211d60595abbb8592e76e27846ba6c349a6d0 native 40452608070: failed
#525 Cline 8d278b1d0766931be192447733e1e8ffbd0167b5 native 40453454042 and legacy 40453453993: failed
#526 Gemini eef6c202abf02489338db54c0ffbb9cb2c283ca6 native 40405537328: failed; exact parser finding above
#527 Copilot 5afd897d4b10de6286d1e0c97d358ec4e15f0250 native 40408790152: failed
#528 Windsurf/Devin 8006c406f749b5143483e6f265d8addbc35aa88c native 40440079451: failed
#529 Kiro 6e99cbec984b7482923d1940f6adb6214993ef1c native 40399399094: failed
#530 VS Code 0db4d25a17c95eee23ad230f9399bf325f1251b2 dedicated trusted VS Code 40440148560: failed

Parent b16 has successful ordinary CI, but Project Native Runtime 40392784331 contains successful admission followed by SKIPPED native matrix job 121879403273; that is not combined leaf qualification. Likewise a generic green workflow on #530 does not replace its failed dedicated VS Code gate. Refresh all refs before further action. No leaf or parent is approved for merge by this review.

@777genius 777genius left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scope correction to readiness review 5662612447: the latest owner instruction recorded at 2026-10-27 05:12 UTC is «Vscode не приоритет, его пропускаем». PR #530 is excluded from the current completion scope and must remain draft; its earlier matrix row is historical information only, NOT a gate blocking #521–529 or their eventual integration into #520. No further VS Code implementation/review requests/merge are authorized by this completion task. The current in-scope NO-GO is independently supported by the unsuccessful native gates of #521–529, the concrete Gemini finding, and incomplete independent reviews—not by VS Code. Preserve the active root's ongoing nine-client work. No code/ref or automation changes were made here.

Copy link
Copy Markdown
Owner Author

Coordination, 2026-10-27 05:41 UTC: the owner has issued a new direct instruction in this session to continue implementation/review and incremental commit/push, preserving existing branches; VS Code #530 remains excluded. This session does not have the root workspace/checkpoint, so it will not edit those checkouts or the checkpoint. Fresh refs show active external Cline 9d01aefb and Qoder c14b4974; those ongoing slices are preserved, not duplicated. I am inspecting current evidence and plan/code review records for the remaining branches and can provide an independent review of the newly published slices. Any publication from this session will use a fresh exact-head lease and force=false; no merge or qualification promotion without the required proof. No CI retries or new PRs have been requested.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant