fix: align Event Lineage shell with UI UX guide

AGENTS.md

@@ -34,7 +34,7 @@ reimplementing them:
   tree assembly (`reconstruct.py`'s `_walk`/`thread_messages` calls).
 - [RankWeave](https://github.com/ContextualWisdomLab/RankWeave) for
   multi-channel score fusion (`weighted_convex_fuse` in
-  `reconstruct.py`) and the buyer-facing Rankings port
+  `reconstruct.py`) and the reader-facing Rankings port
   (`rankweave_client.py`) -- never invent a fused score or a theta.
 - [TEPP](https://github.com/ContextualWisdomLab/TEPP)'s published wire
   contract for calibrated measurement (`tepp_client.py`) -- never
@@ -127,7 +127,7 @@ contextual-orchestrator owns model discovery and selection.
   retaining the original asset and provenance. Recognize image DOM/visual
   regions before OCR, descriptions, Keyman extraction, or embeddings. Store
   region-level evidence; never show an internal LLM instruction such as
-  `This post is an image` to a buyer.
+  `This post is an image` to a reader.
 
 ## Source parsing and semantic units
 
@@ -146,10 +146,10 @@ contextual-orchestrator owns model discovery and selection.
 - Remove presentation-only visual line alignment inside a paragraph (for
   example continuation lines manually aligned after `-`, `*`, `1.`, or `.`)
   from derived semantic text, while retaining the source body and meaningful
-  list/heading nesting. A buyer-facing post view must render semantic
+  list/heading nesting. A reader-facing post view must render semantic
   paragraphs, not the authoring application's spacing workaround.
 - Image descriptions, OCR text, and region evidence are analysis artifacts,
-  not buyer-facing prompt instructions. Buyer UI shows the source content and
+  not reader-facing prompt instructions. The workspace UI shows the source content and
   useful captions/evidence only, with provenance where appropriate.
 
 ## Pluggable channels: never fake a missing signal

ARCHITECTURE.md

@@ -64,7 +64,7 @@ flowchart LR
 | `chunking.py` | Splits a document into meaning-identifiable units (paragraph, sentence, DOM, conversation-turn) plus embedded-image extraction, in document order |
 | `embedding_client.py` | Pluggable text-embedding channel (`Null` default, `OpenAiCompatible` real impl) + `chunked_max_similarity` |
 | `adjudication_client.py` | Pluggable LLM-judgment channel (`Null` default, `ContextualOrchestrator` real impl) |
-| `image_content.py` | Pluggable vision channel: OCR + object recognition/tagging for embedded images (`Null` default, `OpenAiCompatibleVisionClient` real impl). The product popup (`frontend/src/PostBody.tsx`) renders each `data:image` payload in document order so the buyer sees the picture, not the base64 string; GET does not call the vision client. |
+| `image_content.py` | Pluggable vision channel: OCR + object recognition/tagging for embedded images (`Null` default, `OpenAiCompatibleVisionClient` real impl). The product popup (`frontend/src/PostBody.tsx`) renders each `data:image` payload in document order so the reader sees the picture, not the base64 string; GET does not call the vision client. |
 | `tepp_client.py` | TEPP's published `AnalysisRunRequest` wire contract, pluggable transport |
 | `rankweave_client.py` | Fail-closed RankWeave ranking port (`weighted_reciprocal_rank_fuse` in-process; never invent a fused score or a theta) |
 | `reconstruct.py` | The pipeline: group → candidate window → score → fuse → thread |
@@ -326,7 +326,7 @@ Keymen are affiliated with (`lineageweave/affiliate_tree.py`, loaded by
 set of those leaves, not the whole company directory -- a sibling the
 post never mentions is omitted. People on the tree are buttons that
 reuse `GET /api/keymen/{person_id}/related` so the popup Keyman walk
-starts from the affiliation the buyer clicked. A resolved organization
+starts from the affiliation the reader clicked. A resolved organization
 is the same walk via `GET /api/corporate-entities/{id}/related`. An affiliation that did not resolve to
 a `corporate_entity` row stays as its own root (`resolved=false`); that
 is the same never-guess-a-parent rule
@@ -467,15 +467,15 @@ truly have no dated open tickets.
 
 ## Phase 6-M2: authorized analysis-run evidence (read projection)
 
-Issue #79's first buyer-visible Milestone 2 slice is a source-redacting
+Issue #79's first reader-visible Milestone 2 slice is a source-redacting
 read of the #89 registry. `GET /api/analysis-runs` and
 `GET /api/analysis-runs/{id}` require `post_read` and apply the scope
 in SQL: the requester always sees their own run; a corporate-entity or
 process-unit scope is visible only to affiliated accounts; a
 thread-group scope is visible only when the account can already see a
 post in that group; `all_visible` is requester-only. Hidden runs 404. Detail also lists ABAC-visible post titles in the
 run's scope whose `created_at` is at or before `knowledge_cutoff`
-(ADR 0016) so a buyer can open a post the run was allowed to know
+(ADR 0016) so a reader can open a post the run was allowed to know
 without seeing later live rows or hidden bodies. Detail also returns
 revision and configuration digest prefixes.
 `POST /api/analysis-runs` records a Pending lineage run on a new
@@ -925,7 +925,7 @@ code. Wired into both `keyman_ingestion.py`'s affiliation loop and
 ## Standards-complete W3C PROV-O provenance layer
 
 ADR 0011 separates standards-complete provenance from the compact
-buyer-facing navigation graph. `lineageweave/prov_o.py` validates
+reader-facing navigation graph. `lineageweave/prov_o.py` validates
 and materializes all 50 normative PROV-O properties, including
 literal-valued times/values and qualified Influence resources.
 `migrations/0017_prov_o_standard_relations.sql` stores definitions,

CHANGELOG.md

@@ -6,11 +6,31 @@ All notable changes to this project are documented here. Format follows
 
 ## [Unreleased]
 
+### Changed
+
+- Renamed "Buyer" terminology to reader/workspace naming across the frontend
+  shell, backend evidence helpers, and living docs (ADR 0119). LineageWeave
+  has no explicit buyer role, so `BuyerNav`/`BuyerDestination` became
+  `WorkspaceNav`/`WorkspaceDestination`, `.buyer-gnb*` CSS became
+  `.workspace-gnb*`, and prose referring to the reading user now says
+  "reader" instead of "buyer". Historical ADRs and changelog entries keep
+  their original wording as a point-in-time record.
+
 ### Fixed
 
 - `make smoke` and `make seed` now run through the locked project `uv`
   environment, so local OIDC and synthetic-data workflows resolve the same
   pinned dependencies as CI.
+- The workspace Event Lineage global Search action now retries focus after the
+  board finishes loading, so navigation from Customer master, Calendar, or
+  Ask Agent lands the cursor in the search box. The handled request is consumed,
+  so later board navigation does not steal focus, and Search closes an open
+  mobile drawer like every other destination change.
+- Mobile Event Lineage evidence cards now read their translated column labels
+  from the rendered cells instead of hardcoded English CSS, and the two drawer
+  close controls have distinct accessible names.
+- Event Lineage SVG edges now retain their instance-specific direction markers,
+  so parent-to-child arrows remain visible when multiple lineage groups render.
 - All OpenAI-compatible chat-completion consumers now validate the shared
   response envelope before parsing it, preventing malformed provider bodies
   from escaping as raw `KeyError` or response-shape details.

backend/app/analysis_run_ingestion.py

@@ -249,7 +249,7 @@ async def fetch_outbox_deliveries(
     """Labeled claim/delivery events for one already-visible run.
 
     Missing outbox tables mean migration 0023 is not applied. Stream
-    entry ids stay off the payload -- they are not buyer evidence.
+    entry ids stay off the payload -- they are not reader-facing evidence.
     """
     try:
         rows = await conn.fetch(
@@ -285,7 +285,7 @@ async def _serialize_runs(
     conn: asyncpg.Connection,
     rows: list[asyncpg.Record],
 ) -> list[dict[str, Any]]:
-    """Project registry rows into the authorized buyer-facing payload."""
+    """Project registry rows into the authorized reader-facing payload."""
     if not rows:
         return []
     count_rows = await _counts_by_run(conn, [str(row["analysis_run_id"]) for row in rows])
@@ -346,7 +346,7 @@ async def fetch_visible_analysis_runs(
     """Runs the account requested or whose scope they may already walk.
 
     Once real source-import evidence is visible, the synthetic `make seed`
-    Demo Corp runs stop appearing here -- a buyer must not mistake that
+    Demo Corp runs stop appearing here -- a reader must not mistake that
     fabricated narrative for real evidence (ADR 0001 / ADR 0042).
     """
     # Safe SQL: this immutable module query contains only closed schema SQL; request values remain bound below.

backend/app/demo_scope.py

@@ -4,7 +4,7 @@
 something to show. Once an account can see at least one post carrying real
 source-import evidence, the synthetic Demo Corp tree is no longer needed to
 fill an empty screen and must stop appearing next to real evidence -- a
-buyer must never mistake a fabricated contact (e.g. Ada West, Priya Nair)
+reader must never mistake a fabricated contact (e.g. Ada West, Priya Nair)
 for a real one.
 """
 

backend/app/entity_relationship_ingestion.py

@@ -128,11 +128,11 @@ async def fetch_relationship_network(
     can be a customer in one post, a competitor in another (their own
     product line competes with ours elsewhere), the customer of our
     customer in a third, or a supplier -- Customer Master's per-post
-    reads never rolled these up, so buyers could only see one role at
+    reads never rolled these up, so readers could only see one role at
     a time and never the entity's whole network. This groups every
     visible, eligible post's classifications by counterparty name,
     keeping every distinct relationship type observed (not just the
-    most frequent), so a buyer can see a name marked both Customer and
+    most frequent), so a reader can see a name marked both Customer and
     Competitor and know that reflects the real, mixed relationship
     rather than a classification error.
 

backend/app/issue_ticket_ingestion.py

@@ -173,7 +173,7 @@ async def upsert_commitment_ticket(
 
     Re-deriving the same post must not stack duplicate calendar rows --
     an existing open ticket with a commitment_summary is updated in place.
-    A closed ticket is left alone so the buyer can keep the historical
+    A closed ticket is left alone so the reader can keep the historical
     record and still derive a fresh open one.
     """
     existing = await conn.fetchrow(

backend/app/knowledge_graph.py

@@ -576,7 +576,7 @@ async def fetch_person_role_history(
     responsibility, in posts at different times (a job change, a title
     change, a move between projects). ``post_summary_role`` already
     carries this per post; this simply orders it chronologically for
-    one person instead of leaving a buyer to open every post that
+    one person instead of leaving a reader to open every post that
     mentions them and compare manually.
 
     ``visible_post_ids`` must already be ABAC-filtered by the caller
@@ -590,7 +590,7 @@ async def fetch_person_role_history(
     rows = await conn.fetch(
         """
         select role.post_id, post.post_title, post.created_at,
-               role.responsibility, role.affiliated_organization_name
+               role.responsibility_text, role.affiliated_organization_name
           from post_summary_role role
           join source_post post on post.post_id = role.post_id
          where role.cataloged_person_id = $1
@@ -605,7 +605,7 @@ async def fetch_person_role_history(
             "post_id": str(row["post_id"]),
             "post_title": row["post_title"],
             "created_at": row["created_at"].isoformat(),
-            "responsibility": row["responsibility"],
+            "responsibility": row["responsibility_text"],
             "affiliated_organization_name": row["affiliated_organization_name"],
         }
         for row in rows