feat: focus Keyman after GNB Event Lineage names it next (v2.19.0)

AGENTS.md

@@ -181,6 +181,8 @@ Opening an Ask Agent cited post uses the same focus path (ADR 0096). Do not
 invent a cited post.
 A linked Event Lineage node opened from that focused popup keeps the
 originating flags (ADR 0097). Do not invent a cited post.
+That open then focuses Keyman as the named next read (ADR 0100). Do not invent
+a week, a theta, a cutoff body, a CalDAV event, a customer, or a cited post.
 
 
 ## Tests

ARCHITECTURE.md

@@ -286,7 +286,8 @@ Calendar commitments use the same Event Lineage focus path (ADR 0094),
 Customer master related posts use the same Event Lineage focus path
 (ADR 0095). Ask Agent cited posts use the same Event Lineage focus path
 (ADR 0096). A linked Event Lineage node opened from a focused popup keeps
-those flags (ADR 0097), and the full detail popup includes Korean
+those flags (ADR 0097) and then focuses Keyman as the named next read
+(ADR 0100). The full detail popup includes Korean
 summary/key-events/R&R, VOC evidence excerpts, an Event Lineage panel
 (direct vs. indirect links; a link opens that post), the Keyman
 affiliate tree (resolved ancestors plus unresolved org roots), Keyman +

CHANGELOG.d/2.19.0-gnb-event-lineage-focus-keyman.md

@@ -0,0 +1,5 @@
+# 2.19.0 GNB Event Lineage focuses Keyman as the next read
+
+Opening a GNB-focused post keeps Event Lineage current and moves focus
+to Keyman so the named next action is landable. A home-list open does
+not. No TEPP theta is invented.

CHANGELOG.d/2.19.0-remove-source-fix-artifacts.md

@@ -0,0 +1,8 @@
+# 2.19.0 — Remove one-shot repair artifacts
+
+## Fixed
+
+- Removed the self-modifying pnpm repair workflow and unreferenced root-level
+  source-rewrite scripts after their one-time repairs were completed. Product
+  behavior now lives in reviewed source and normal CI rather than a workflow
+  that edits and pushes its own branch.

CHANGELOG.d/2.20.0-global-ask-public-verification.md

@@ -0,0 +1,7 @@
+# 2.20.0 — Global Ask public semantic verification
+
+- Global Ask may nominate source posts from persisted semantic, ontology, and Knowledge Graph evidence instead of requiring the buyer's term to appear in raw post text.
+- Multilingual contains-search uses one indexable predicate per semantic field and migration 0054 adds matching `pg_trgm` GIN indexes; concatenated expression scans are regression-tested out.
+- An explicit public-verification boundary uses SearXNG retrieval and contextual-orchestrator verification while keeping external URLs separate from internal post citations.
+- Private source evidence, Keyman/person facts, TEPP measurement artifacts, and fast-mlsirm measurement data are ineligible for public-search egress.
+- Public corroboration remains review evidence and never authority-promotes an inferred graph or ontology assertion.

CHANGELOG.d/2.20.0-project-history-contract.md

@@ -0,0 +1,7 @@
+# 2.20.0 Project-history response contract
+
+Project-history storage projections now emit the same strict evidence-bound
+shape that the HTTP response validates. Project identity display names retain
+their authoritative code/key, event source IDs and time basis are explicit,
+and the endpoint no longer fails with a validation error for an authorized
+timeline.

CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to this project are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.19.0] - 2026-08-20
+
+### Added
+
+- Opening a Board Weekly VOC post, Calendar commitment, Customer master
+  related post, or Ask Agent cited post now keeps Event Lineage current
+  and focuses Keyman as the named next read. A linked Event Lineage DAG
+  walk from that popup keeps the same Keyman focus. A home-list open
+  does not add that focus or copy. No TEPP theta is invented. No cited
+  post, customer, week, or cutoff body is invented (ADR 0100 / ADR 0097
+  / ADR 0016).
+
 ## [2.17.0] - 2026-08-19
 
 ### Added
@@ -32,7 +44,7 @@ All notable changes to this project are documented here. Format follows
   Keyman and evaluation as the next read. Customer master names authorized
   customer entities as current before that open. Home-list opens do not add
   that focus or copy. No TEPP theta is invented. No customer is invented
-(ADR 0095 / ADR 0037 / ADR 0016).
+  (ADR 0095 / ADR 0037 / ADR 0016).
 
 ## [2.14.0] - 2026-08-19
 

CLAUDE.md

@@ -105,3 +105,12 @@ cited post.
 From a GNB-focused popup, open a linked Event Lineage node: Event Lineage
 stays focused and names the new post as current (ADR 0097). A home-list
 DAG walk does not. Do not invent a theta.
+
+## GNB Event Lineage focuses Keyman (v2.19.0)
+
+A GNB-origin popup (Weekly VOC, Calendar, Customer master, Ask Agent, or a
+linked Event Lineage DAG walk from one of those) keeps Event Lineage
+current and moves focus to the Keyman heading once Keyman rows have
+settled (ADR 0100). The report-member auto-land chain to related nodes
+and Ask is not used for GNB origins. A home-list open does not gain that
+ focus. Do not invent a theta.