Expose entity resolution response schemas to JSON object providers

docs/entity-resolution-v1.md

@@ -122,3 +122,25 @@ and final interpretation together. Success means the model itself proposes a
 context-grounded search, distinguishes Goldark from the affected creature, and
 retains the selected identity and its provenance. A fixture test alone does not
 establish this live-model quality.
+
+## Schema visibility fix (prompt protocol v2)
+
+New resolution runs freeze `protocol_version = 2` in their input artifact. Both
+planning and assessment include the output schema in the user message, so
+providers configured with `response_format = "json_object"` can see the required
+fields. That provider mode only requests JSON; it does not transmit the internal
+request schema. Protocol v1 omitted that message field. Existing v1 artifacts
+retain their original request construction and prompts for immutable replay.
+
+The first live entity-resolution trial exhausted planning validation: two
+`LLM_OUTPUT_SCHEMA` results and one `LLM_INCOMPLETE_OUTPUT`. No lookup was
+executed. The error records do not retain rejected response bodies or the exact
+incomplete finish reason, so they cannot establish each response's detailed
+cause. Do not retry that exhausted case unchanged; use the fresh trial below.
+
+A corrected trial is prepared at `service-data/trials/entity-resolution-schema-20261015`
+with package ID `trial-entity-resolution-schema-BUG-000020-20261015`:
+
+```powershell
+.\.venv\Scripts\python.exe -m viano_bug_analysis.trial run --workspace service-data/trials/entity-resolution-schema-20261015 --llm-config config/llm.timeout300.local.toml --project-config config/project.local.toml --case-id BUG-000020 --package-id trial-entity-resolution-schema-BUG-000020-20261015 --stop-after interpretation --max-dispatches 6
+```