JVNAUTOSCI-2234: Render promoted summary fields and full literals

[witbrock]

Merge decision: ready — merging makes long relationship literals fully inspectable and copyable, and lets Vontology type policy promote arbitrary fields into the concept summary without changing KCAP salience.

User outcome

A concept-tab user can read and copy the complete text behind a truncated relationship value. Types can also use rendering-specific #V#has_summary_fields policy to place important exact values beside the description at the top of the concept page.

Material changes

• Union direct and inherited summary-field bindings, resolve represented labels/order/configuration, and preserve origin types.
• Project unconsumed text or concept fields generically, including every value in the bounded read, canonical/personal/organisation scope, identifiers, provenance, and honest truncation/degraded-state diagnostics.
• Add release seed v2 for #V#research_description → #V#summary_field_research_description_as_of → #V#has_research_description_as_of; this is explicitly rendering policy and does not alter KCAP salience.
• Render promoted fields with wrapped exact text, accessible expand/collapse and copy controls, scope labels, and concept navigation.
• Replace relationship-table ellipsis-only literals with two-line previews, explicit full-width detail rows, and exact copy controls.
• Jira: JVNAUTOSCI-2234

Evidence

• .venv/bin/pytest -q tests/backend/test_concept_summary_field_resolver.py tests/backend/test_concept_summary_renderer_service.py tests/backend/test_concept_summary_renderer_routes.py — 25 passed.
• Affected frontend Jest suites — 62 passed across summary rendering, relationship disclosure, tab sizing, and concept-tab ID behaviour.
• Pyright on both changed backend services — 0 errors.
• Static frontend lint on both changed JS modules — 0 errors; 15 existing warnings in dynamicTabs.js.
• Isolated AgentTest server plus Chrome/Playwright live app-shell replay at desktop and 390px: exact text retained on both surfaces, both disclosure controls expanded, clipboard matched byte-for-byte, no desktop body overflow, narrow summary stayed inside x=24..366, and the narrow Close control remained a non-wrapping 49x20px.
• Full Jest run: 894 passed and 9 failed in four unrelated suites. A detached clean origin/main worktree reproduced the same 9/9 failures, establishing them as baseline rather than candidate-caused.

Ship boundary

• Minimum ship criteria: exact long literals are readable/copyable; type/ancestor policy promotes arbitrary configured fields without a new domain branch; exact multiple values and scope remain distinct; affected tests and the live responsive replay pass.
• Stop-ship conditions: widened authority, KCAP salience changes, silently selected/dropped values inside the declared bound, blocked core concept hydration, executable markup, inaccessible controls, or a candidate-caused regression on the affected path.
• Non-blocking observations: seed reconciliation/activation is a separate release operation and was not run against live Vontology; the complete repository Jest run retains nine independently reproduced baseline failures.
• Non-goals: remove all specialised summary-card builders, redesign the whole relationship table, deploy/activate a running environment, or repair unrelated Jest timing/mock failures.