From 8779666c55d7e816f328751dbe7fb31c1ff6c15b Mon Sep 17 00:00:00 2001
From: AstroQore <69107895+AstroQore@users.noreply.github.com>
Date: Mon, 31 Aug 2026 18:53:08 +0800
Subject: [PATCH 1/2] Say who actually uses this, and which lane

Used by listed Vibe Bar and then the single word Auspex, and predated the
Rust lane entirely. It now names all three consumers, what each one takes,
and the fact that Auspex is the only user of AgentSessionLive -- which is
the thing a reader most wants to know before touching that target.

It also states the consequence of static linking that the version section
explains but this list did not: a kit release reaches nobody until the app
that consumes it ships a build.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 README.md | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 0fa22bd..ea57189 100644
--- a/README.md
+++ b/README.md
@@ -614,11 +614,30 @@ of its own. Nothing updates in place.
 
 ## Used by
 
+**Swift lane.**
+
 - [Vibe Bar](https://github.com/AstroQore/vibe-bar) — macOS menu-bar app for
   agent quota, usage, and cost. This package was extracted from it, and Vibe
   Bar pins it `exact:` and compiles it into the app; its Settings › System
-  pane shows the bundled `AgentSessionKitInfo.version`.
-- Auspex.
+  pane shows the bundled `AgentSessionKitInfo.version`. It uses
+  `AgentSessionKit` for the session index, transcripts, deletion planning and
+  the MCP transport.
+- [Auspex](https://github.com/AstroQore/auspex) — a macOS app that watches the
+  agent sessions running on one machine. It is the only consumer of **both**
+  products: `AgentSessionKit` for what is on disk, and `AgentSessionLive` for
+  the tailing, liveness and event pipeline that turns it into a live view.
+
+**Rust lane.**
+
+- [Vibe Bar Desktop](https://github.com/AstroQore/vibe-bar-desktop) — the
+  cross-platform client of the same product, on Windows and Linux as well as
+  macOS. It depends on `agent-session-core` for read-only index access,
+  Codex/Claude Code discovery, transcript paging and resume commands, so both
+  Vibe Bar clients read sessions by one set of rules rather than two.
+
+Vibe Bar and Auspex ship their own release trains and bump the pin
+independently; nothing here is loaded at runtime, so a kit release reaches a
+user only inside the next build of the app that consumes it.
 
 ## License
 

From ea80a02e037a9474f2ecf88facf263587cabde32 Mon Sep 17 00:00:00 2001
From: AstroQore <69107895+AstroQore@users.noreply.github.com>
Date: Mon, 31 Aug 2026 19:25:20 +0800
Subject: [PATCH 2/2] Let the required check run on every pull request

Scoping CI (Swift) to Swift and contract paths made sense for pushes, but
Build and test is a required status check: a filtered workflow never
reports on a docs-only change, so the branch rule waits for a run that can
never start and the pull request cannot be merged at all -- not even with
admin. This one hit that on its own README change.

Pushes to main keep the filter, where the run is informational rather than
a gate.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 .github/workflows/ci-swift.yml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/ci-swift.yml b/.github/workflows/ci-swift.yml
index b0159bc..ba5f363 100644
--- a/.github/workflows/ci-swift.yml
+++ b/.github/workflows/ci-swift.yml
@@ -8,12 +8,11 @@ on:
       - "implementations/swift/**"
       - "contracts/**"
       - ".github/workflows/ci-swift.yml"
+  # No path filter on pull requests: "Build and test" is a required check, and
+  # a filtered workflow simply never reports on a docs-only change, so the
+  # branch rule waits forever for a run that cannot start. Pushes to main stay
+  # filtered — there the run is informational, not a gate.
   pull_request:
-    paths:
-      - "Package.swift"
-      - "implementations/swift/**"
-      - "contracts/**"
-      - ".github/workflows/ci-swift.yml"
   workflow_dispatch:
 
 concurrency: