Skip to content

feat(claude): install native plugins in an isolated project scope - #480

Closed
777genius wants to merge 3 commits into
feat/project-integration-checkpointsfrom
feat/project-claude-e2e
Closed

777genius wants to merge 3 commits into
feat/project-integration-checkpointsfrom
feat/project-claude-e2e

Conversation

@777genius

@777genius 777genius commented Oct 23, 2026 •

Copy link
Copy Markdown
Owner

Current native result and diagnostic replay

The genuine macOS project test on 2d81027 failed during production add: the Claude plugin-list response was unrecognized. Existing user/runtime suites passed, but do not qualify project scope. The failed run and exact original artifact are preserved in the assembly branch.

Current head 2c767ea adds only a diagnostic replay after two independent plan approvals and two code approvals: on the first installer error, capture bounded read-only plugin lists from A and B, while retaining the original failure. No parser acceptance, success assertion, native-host guard, trust or authentication rule is weakened. The cause and corrective parser behavior must be based on actual raw output; project qualification is still pending.

Why

A project-scoped UAP installation must use Claude's actual native project plugin scope and exact selected repository, without borrowing user receipts or changing another project's state.

Changes

  • Add scoped plugin installation/removal with fixed project cwd and preserved user configuration context.
  • Require exact native scope, source, version and clean installPath/projectPath spellings; reject aliases, scope mismatches and symlink traversal instead of promoting them to installed evidence.
  • Keep package data through update/repair and incomplete native listing/restart recovery.
  • Add a source-only native project test and hosted matrix routing without weakening disposable-runner guards or historical release lanes.

Verification

The production fix at 32dd485e received two independent final GO reviews, committed with the implementation evidence. Project client/provider and SDK user/A/B lifecycle tests pass, including exact old-pin repair after source movement, retained data, foreign state, removal, and recovery after post-commit native listing failure. Python native-runner tests pass and changed-line lint reports zero issues.

A local pinned Claude help probe could not launch in this sandbox; no native project runtime qualification is claimed. The authored project discovery test must run on the real disposable GitHub-hosted runner. Prepared/installed, native listing, MCP initialization and model behavior remain distinct evidence levels.

Stack

Client-specific draft for #472, temporarily based on the reviewed integration checkpoint branch. Retarget and merge only into the project feature branch after applicable CI and native source gate; do not merge into main. Integration must preserve both the Codex and Claude source-only native matrix rows.

Delivered in #499

Delivered by #499, merged into main as 3b93148c. The integrated source 3386c72a91e7e9b3574f12ce0613b399227a1ada passed all 74 check runs and 24 PR workflows; the actual merge tree is identical to that validated source.

This PR's reviewed head 2c767ea0a2eb3e3e2640afcff0fbab5cfa31973b is preserved by ancestry in the integrated source and the main merge. Closing as incorporated; no separate merge into the earlier stacked base is needed.

@coderabbitai

coderabbitai Bot commented Oct 23, 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.

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