feat(sandbox): add edit_file (str_replace) tool for partial edits — scaffold

[iroiro147]

What

Scaffold PR for #1523: adds a framework edit_file tool that performs a single unique substring replacement, avoiding the token cost of full-file write_file regeneration.

Changes (139 LOC, 3 files)

File	Change
runtime/framework-tools/edit-file.ts (NEW, 129 LOC)	Zod input/output schemas, executeEditFileOnSandbox executor with unique-substring guarantee, EDIT_FILE_TOOL_DEFINITION definition
runtime/framework-tools/index.ts (+2)	Import + register EDIT_FILE_TOOL_DEFINITION alongside existing tools
public/tools/defaults.ts (+12)	Export editFile public tool surface matching readFile/writeFile pattern

Behavior

• edit_file({filePath, oldString, newString})
• Reads file → enforces oldString appears exactly once → replaces → writes back
• Throws descriptive error when oldString is missing, empty, or >1 occurrence
• Returns {path, replacements: 1}

Design tradeoffs (intentionally deferred to maintainer review)

• Atomicity: read-then-write is one sandbox call (not two round trips). Rationale: agent already has file contents in context; the race window is bounded by turn-time.
• Failure signaling: descriptive errors ("not found", "ambiguous match") let the agent retry with more context rather than silent corruption. Mirrored from Claude Code's Edit tool behavior.
• API surface: only uses existing SandboxSession primitives — no new deps.

Verification

• Local typecheck: not run (no node_modules in this workspace). npx tsc --noEmit in a dev checkout is the verification gate.
• Code review only. Maintainers: if design shape looks right, this is a clean scaffold to extend with tests/telemetry.

Closes #1523 (design-shaped; whether this is THE implementation or a starting point is maintainer call)

[vercel]

@iroiro147 is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[iroiro147]

Both VADE findings fixed in a8919ad:

1. read-file stamp refresh — executeEditFileOnSandbox now refreshes the read-file stamp after a successful write, so a subsequent write_file on the same file no longer fails with "modified since it was last read". Mirrors the stamp-refresh pattern in executeWriteFileOnSandbox.

2. $-pattern replacer — String.replace(oldString, newString) was interpreting $$, $&, $`, $', $n in newString as special replacement patterns. Now passes a replacer function () => args.newString so the replacement text is inserted literally.

Typecheck still gated on CI (no local node_modules in this worktree).

[iroiro147]

CI status note: typecheck + lint + test-integration(ubuntu) + test-scenario all green on a8919ad. test-unit and test-integration(windows) fail identically to my other open eve PRs (#1528–#1532) — consistent with fork-scoped CI credentials, not the change (which is contained to packages/eve/src/runtime/framework-tools/). DCO signoff present. Ready for design/impl review when a maintainer gets a chance.

[iroiro147]

Standing-health check (re-verified against current main 021dbbf2, 2 commits past this branch's base):

• Merge dry-run vs current `main`: clean, zero conflicts. The 2 new commits touch `cli/dev/tui` + a version-package bump — disjoint from this PR's surface (`runtime/framework-tools`).
• CI: `unit/windows/e2e/Vercel-deploy` remain failing — these are fork-CI infrastructure constraints (Vercel deploy `Authorization required`, e2e needs Pro sandbox credentials), not regressions from this change. `typecheck/lint/test-integration(ubuntu)/test-scenario` green on the PR head (per prior run).
• This is a draft scaffold; the `blocked` merge state is the draft/review gate, intended.

Ready for a maintainer shape-review whenever convenient; no action required from contributors.