Apply revision-checked semantic patches to Screenplay models

[woksin]

Scope

Expose a versioned semantic snapshot for AI/Studio and allowlisted typed patch operations by stable semantic ID. Apply patches atomically against an expected revision, update workspace/CST, bind/validate, print, compile and return a new revision or typed conflict.

Acceptance criteria

• Stale revisions fail without partial changes.
• Add/update/rename/move/remove/link/specification operations are typed and reference validated.
• Canonical print/compile/semantic equivalence is required after every patch.
• Compiler-authored repair templates use diagnostic codes/node IDs rather than parsing messages.
• Human and AI edits use the same transaction contract.
• Studio and Prologue can preview patches without applying them.

Depends on the ESM and workspace children of #128.

[cratis-direct]

Thanks for opening this - it has been received and will be looked at.

---

Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.

[woksin]

First implementation slice started on feat/semantic-patches: typed UpdateSliceDescription by stable SemanticId, source-map Description role with exact non-zero span, expected-current-value drift detection, exact UTF-8/BOM-preserving splice, and existing atomic ScreenplayWorkspace.Propose preview/apply/write-plan path. Missing/fenced descriptions, non-slice IDs, ambiguity and same-document multi-edit fail typed; no arbitrary raw-text patch or printer synthesis.

[woksin]

Implementation reached a 9-file source-plumbing/operation draft and Debug-compiles, but had 2 StyleCop ordering warnings and no specs yet. The same agent is resumed with no-suppression type reordering, full adversarial spec matrix, docs, Debug/Release/full/corpus gates, and logical commits. No partial commit or PR will be accepted.

[woksin]

First typed patch slice is in Screenplay#175: UpdateSliceDescription by stable SemanticId, exact Description source-map span, expected-current-value drift check, UTF-8/BOM-preserving splice, typed stale/unknown/unsupported/multi-owner/compilation conflicts, and existing atomic workspace preview/apply. Local gates: Debug+Release zero warnings, 2220/2220 Screenplay specs, 20/20 canonical parity, LSP clean. CI is running.

[woksin]

First allowlisted operation landed in Screenplay#175. Keep #138 open for additional typed semantic operations, preview/apply client surfaces and broader repair templates; arbitrary raw text patching remains out of scope.

[woksin]

Work has started locally as part of the coordinated end-to-end Screenplay/Stage/Studio/CLI delivery effort tracked in #174. @woksin is coordinating implementation in dependency order with repository-specific AI corpus instructions and specifications. Existing work/PRs will be reconciled rather than duplicated. This is a kickoff, not a completion claim; focused progress, verification evidence and blockers will follow here.

[woksin]

The bounded semantic mapping-patch increment is now implemented and verified locally. It addresses one existing produced-event mapping by stable semantic IDs, preserves exact authored bytes outside the RHS, and rejects stale, ambiguous, wrong-owner/type and unsupported changes without a candidate/write plan.

Independent review found no functional defect and passed the adversarial Unicode/document-ownership probe. Its four real style findings were repaired without changing cases or assertions. The exact parent warnings-as-errors gate now passes all 880 selected facts, including the 66 new facts; full Debug/Release repair builds are clean. Earlier full/vector/package evidence is retained separately.

No commit, publication, broader patch-completeness or constrained-implementation (#139) claim. #174 remains open.

[woksin]

Partial increment PR created: #182

Changes:

• ProducesParser captures SourceLocation and SourceLength for mappings
• ProducedEventMappingPatch and ProducedEventMappingSourcePatch types added
• Workspace transaction support for mapping patches
• 22 new specs covering mapping edge cases

Verification:

• 2,346 language specs + 22 canonical checks pass
• Verified across net8.0, net9.0, net10.0
• Clean Debug/Release builds

[woksin]

Status after v4.20.0 (triage of what shipped in v4.18.0–v4.20.0):

The spine is in: stale revisions fail with no partial change (Workspaces/WorkspaceTransactions.cs:202), canonical print/compile/semantic equivalence is enforced after every patch, Propose is pure preview (ScreenplayWorkspace.cs:99-104), and MCP routes through the identical contract (Screenplay.Mcp/McpWorkspaces.cs:71). Typed ops now cover documents, AST nodes, logical rename, slice description (#175) and produced-event mapping source (#182).
Remaining: typed link and specification operations, and the whole repair-template surface — no Repair/CodeAction/QuickFix type exists anywhere in Source/. Both are straightforward extensions of the existing operation pattern.

[woksin]

Ruled and recorded as accepted decision 0014 (PR #255): a repair is a typed workspace edit proposal keyed by diagnostic code and node handle, reviewed and applied through the same revision-checked transaction as any other edit; raw text edits are not adopted. "Link" is covered by adding nodes whose references are validated on compile. Ready to implement.

[woksin]

Screenplay v4.35.0 ships decision 0014: compiler-authored repairs are typed workspace proposals (diagnostic code, node handle, typed operations), previewed and applied through the revision-checked authoring contract, and exposed over MCP (read-workspace view repairs, propose-repair; never auto-applied). The first repair migrates deprecated validate csharp blocks (PLAY0397). The link criterion is covered by decision 0014: adding a typed node validates its references when the candidate compiles, and unresolved references are refused under the safe policy, so no separate link operation is needed. Still open here: more repairs and the specification operation.