Bind the Workspace-Edit Rule on the Session the Reload Hits, Not on Where the Editor Runs #2834

Defect

#2815 scoped the workspace-edit rule in GOVERNANCE.md "Verification Discipline" (carried by the agent-conduct Skill) by where the editing agent runs: an agent inside VS Code is bound, and an agent in a standalone console "edits the file directly, even while a window has that file loaded". The rule's own reason is that a reload destroys the context of "an agent session running in it", meaning in the window that reloads. That session need not be the editing agent.

Constructed scenario: a window has Example.code-workspace loaded and hosts a Claude Code session in the VS Code extension. A console agent working in the same checkout edits that file. The window reloads, and the extension-hosted session loses its context. The current text permits the edit.

The reverse case is over-restricted. An agent in window A is barred from editing a file that only window B has loaded, even when B hosts no session.

Nit

GOVERNANCE.md "Editor and Tasks", last sentence: "Opening the folder rather than the workspace is what keeps a checkout's own file editable." Under the new scope that holds only for an agent running inside VS Code, since a console agent may edit either way.

Open question, not verified

VS Code's persistent terminals may keep an integrated-terminal process alive across a window reload. If so, only an extension-hosted session is lost, and binding the integrated terminal is stricter than the hazard. That errs on the safe side, and it is unmeasured.

Possible direction

Bind on whether a window that has the file loaded hosts a live agent session, the editing agent's own or another's, rather than on where the editing agent runs. Then qualify the "Editor and Tasks" sentence to match.

Context

Found by a frontier-tier review of #2815, run because its only Copilot round was a quota refusal. The maintainer accepted the narrowing as deliberate for now, since the harmful case needs a VS Code-hosted session and a console agent on the same workspace at once, and chose to track the gap here rather than hold the promotion.