Repository navigation
feat: integrate CodeBuddy Code foreground TUI sessions - #6546
nikhilachale wants to merge 10 commits into
Conversation
🏆 Review leaderboardOct 4–11, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 5 more reviewers
|
|
CodeBuddy TUI qualification evidence is published immutably at
Final daemon/UI/source5827f13d75b639eac6ed76f6d572b6752c060da5:23 green exact-head checks. Earlier native/login/provider/startup/CI/static-renderer/capture failures remain separate. TUI/default permissions only; configured auth/freeform models remain honest. Owned cleanup confirmed; no merge/release/deploy. |
|
Final handoff: source |
i-trytoohard
added
comp/daemon
|
Harness-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.
|
Preserve harness-owned evidence and merge current canonical API, storage, and native Chat updates. Runtime proof remains qualified by its original source.
|
Canonical 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. |
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.
|
Canonical 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. |
|
Canonical 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. |
|
Canonical 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. |
This branch has not been deployed
2 participants
Code changes: +678 -11
Tests: +429 -6
Others: +1069 -3
Binary assets in this source snapshot: 5 (excluded from line counts).
Foreground TUI with native Default/manual permissions; Chat/ACP, Auto, Accept Edits, Bypass, background work, reviewer and handoff excluded.
Current status
Current source snapshot:
a646ae710f8d2273d11be72cf6c78a487b9d2760(basedb77f945db58ce1d9970e99e7e9b68396f38c78b). Open for review; GitHub mergeabilityMERGEABLE, merge stateBLOCKED. Exact-head CI: pending (15 successful, 8 queued/running, 0 unsuccessful among 23 reported checks). CI run 1 · CI run 2 · CI run 3 · CI run 4. Green source CI does not establish current native/UI runtime proof or full integration readiness.This fix created only clean isolated source worktrees and temporary review reports; it created no AO/native sessions, provider profiles or owned runtime processes. No local build, gofmt, test, fixture, provider or UI run was performed.
Historical runtime build: Historical AO/UI source
5827f13d75b639eac6ed76f6d572b6752c060da5, released@tencent-ai/codebuddy-code@2.164.0, Node24.21.0/Ubuntu; launcher SHA256426186a82e36466d5be485f335ced1b0d664539c53b72a5f10ba3a267e60dab6. Earlier lifecycle sources/failures remain separately recorded. Report · evidence index, original receipts, image/provenance hashes. Receipt SHAs/bytes are unchanged. Linux/VPS proof is not Windows/macOS native proof. Runner SHA2568887aa2e7101b9e6d3950bfca08ffddf2e1e6c1c3f1d030c8dec2676443aecearemains historical where reported; manual/standalone proof is not a strict runner PASS.Changes since runtime proof: The harness guide records direct model IDs, supported permissions/input/history bounds and an intentional initials avatar fallback because no asset reuse terms were verified. Native/UI journeys at the current source are NOT_RUN. Current-main reconciliation preserves the integration and upstream migration ledger; current source/CI state is recorded above.
The matrix separates current verification from recorded historical passes;
NOT_RUNdoes not erase those passes. Excluded interfaces/manual model input are deliberate supported-scope decisions.Historical implementation and evidence
Supersedes closed/unmerged contract-only5503 (native2.151.0). Implements current rendered input admission, native profile overrides, bounded additive instructions, exact native-ID history restore and migration0207/historical schema reconciliation. Missing/corrupt/foreign/ambiguous history fails closed; history over32MiB and instructions over64KiB are refused. Credential inventory stays configured; freeform models do not imply a catalog. Suggested prompts remain conservatively nonempty pending native resolution. CI/static output is not an initialized TUI; historical final lab used CI=false. This limited qualification is not a strict catalog/auth runner pass. Historical source 5827f13 had 23/23 green checks; evidence 36f0605 had 5/5/150 fixtures. Earlier native/login/provider/startup/static-renderer/capture, permission-cancel and freed=true assertion failures remain reachable in the report.
historical receipt 1 · historical receipt 2
Reproduction and retained-original limitations
The pinned reports/JSON retain action/result, file/token effects, process identity, cancellation, native-history continuity and capture assertions. A complete sanitized executable reproduction bundle is not established for every manual helper: exact helper bytes/hash and invocation, applicable local-contract bytes/hash with probe argv and interrupt/readiness/draft-cleanup settings, and complete native/AO fingerprints are unavailable where not recorded in the linked receipts; recoverability of those original inputs is unknown. No missing command, contract, hash or result is invented. Later reproductions must use a new attempt and cannot replace original failed/missing evidence.
Recorded owned-process/session/daemon/Electron cleanup is historical. Source worktrees, native profiles/history, dirty scratch workspaces, binaries and raw logs were reported retained privately; a complete current inventory/location/hash and recoverability of every original class are unavailable in the public record. Current recoverability is unknown; this reporting fix reconstructs no missing input and silently substitutes none. Share sanitized artifacts only; exclude credential stores, raw DBs and provider-profile directories. Preserve the retained failures and original screenshots.