Bump agent-document-renderer to 1095077 for node-located content diagnostics
Why: agent-document-renderer 1095077 (origin/main 10950774) adds node-located content diagnostics (required_content_missing, intentionally_empty, template_placeholder_left, mapping_fallback, signature_data_missing, mapping_unresolved, mapping_ambiguous), a mapping Required flag, the intentionally-empty model property, refusal of approved output with missing required content or trusted signature data, expansion of empty w:sdtContent so content lands inside content controls, and nested mapped content controls rendered inside parent slots. Backend pinned 31fbe54. Evidence: go generate ./internal/docgen and go run ./internal/docgen/internal/genrendereridentity -check ok; go vet ./... exit 0; gofmt -l on changed Go files empty; go test -count=1 ./... exit 0 (42 packages ok, including renderer integration tests in internal/docgen); renderer submodule go test -count=1 ./... ok at 10950774. New TestRendererNodeDiagnosticsPassThroughUnchanged asserts renderer codes, severities, NodeID and RulePath pass unchanged through the manifest and DiagnosticError. git diff --cached --check clean. Impact: Renderer identity and the published pin move to 10950774736b64b5d8e544ce03d45ae5a6ceca7c. Backend only renders ordinary workspace working/preview documents; approved and review modes still route to RDM before the renderer runs, so the approved refusal paths are not reachable from Backend. Typical Backend documents produce no new diagnostics and their DOCX output is unchanged in the test suite. Node diagnostics on the failure path are still returned only as DiagnosticError values and are not added to the operation receipt, which carries error text only; that contract is unchanged. Refs: unified renderer plan Tasks 10/13 Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Vendored
+1
-1
Submodule deps/agent-document-renderer updated: 31fbe54fae...1095077473
Reference in New Issue
Block a user