[saphid]

Server plugins cannot read the files in the thread they serve through the public SDK. Server API version 2 adds workspace.listEntries({ threadId, directoryPath? }) and workspace.readFile({ threadId, relativePath }).

Each call resolves the active thread and project, uses the thread worktree or project folder, and reuses the existing shallow listing and bounded text reader. Absolute paths, traversal and symlinks outside the workspace are refused. The SDK README includes an MCP tool example. This is a read-only API for trusted plugins, with the existing 1 MiB text limit. Reads under .git retain existing workspace behavior; errors can include host paths. There is no Files renderer or editing API in this slice, and no client UI change.

Depends on the plugin platform #33606, which is not merged. This branch preserves ashx-j's platform and Maria's follow-up commits, rebased onto main ddc4f576. Their branches and PR ownership are unchanged. The full upstream diff includes that prerequisite. This counterpart keeps its existing feat/plugin-system base; its diff also includes the main refresh. Review the feature and follow-up fixes. Paired PR: upstream #33808.

Published head c780dff2081 adds the shared platform review corrections: structured host lifecycle errors that retain the original cause and existing plugin diagnostics, route-visibility styling owned by SidebarInset, and removal of one static home-region test. The additive feature behavior is unchanged. The earlier ancestry-only merge 66285781965 is retained, keeping the original author base as an ancestor without retargeting either PR. Platform owner refs remain untouched.

Verification on this source tree: CI=true VITEST_MAX_WORKERS=1 vp run check:changed origin/main passed all stages: 1,100 tests in 79 files, 42 package typechecks, format, lint, knip, GraphQL, unused patches and React Compiler. The frozen tree fac078efb3e434587fa854c78a0cc1c42f072d8e matches the committed tree exactly; commit hooks passed. Focused shared-patch verification in the workspace tree passed 42 server tests and 13 browser tests. A fresh independent GPT-6.1 Sol review (high reasoning, Codex harness) approved the exact six-file patch across all three branches with no actionable findings; its additional runtime check passed 27 stage/cause combinations. The earlier isolated Linux suite passed 249 tests in 37 files before this shared follow-up; it was not repeated for these edits. All eight required upstream checks passed on c780dff2081; live upstream checks. This fork reported no check runs or workflow runs on the preceding identical commit; no fork-CI pass is claimed.

The refresh retains main's MCP tool search, settings translations/accessibility, and current composer dictation/submission behavior. The shared browser test now selects the “New thread in…” submenu by name instead of assuming an optional project row exists; Enter activation and project highlight assertions remain. No production keyboard behavior, timeout or retry changed. At the previous publication, all three branches merged cleanly with newer main ed54f306; that later main revision was checked for merge conflicts, not represented as the tested base.

Landing gates: this is additive feature work dependent on the unmerged platform. Upstream's current contribution policy requires a maintainer request for feature PRs; this description makes no claim that such a request or merge approval has been given. Approvability also requires human review of platform/default-primary-environment loading, diagnostic suppressions and intentional plugin exception-text exposure; those gates remain open. Macroscope correctness review was cost-limited and was not bypassed or retriggered. GitHub's clean merge result is not a merge-readiness verdict. Kept open and unmerged; tracked in saphid/personal-ops#128.

Created and integrated with Claude Opus 5.5 in Claude Code and GPT-6.1 Sol in Codex through T3 Code. Fresh integration and shared-fix reviews: GPT-6.1 Sol, high reasoning, Codex harness.