You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
An experimental, opt-in VS Code bridge offers the C# PLAY0166 repair (declare a missing produced event) and the PLAY0478 repair (explicitly route to the command identifier) through a configured, trusted Screenplay executable. Each repair shows read-only previews of every source and identity change and is applied only after an explicit final confirmation. (part of #341)
Repairs are refused while affected files have unsaved or untitled changes, and a stale review is refused at Apply time when source files, identity state or referenced attachments changed on disk, even if no file notification arrived. (part of #341)
When an Apply outcome is uncertain, the extension preserves your typing and never retries; a definite refusal after dispatch is treated as uncertain too. Read-only inspection of the retained root and explicit consent through Screenplay: Resume repairs after inspection allow the next repair to start a fresh, revision-checked session without reusing old tokens or reviews. (part of #341)
The VS Code guide documents how to enable and use the repair bridge, inspect recovery state and resume repairs safely. (part of #341)
Changed
The VS Code board and local language assistance remain available in Restricted Mode, while C# repair processes require workspace trust. Workspace overrides for source roots and repair settings are restricted until the workspace is trusted. (part of #341)