Skip to content

Say who actually uses this, and which lane - #16

Merged
AstroQore merged 2 commits into
mainfrom
docs/used-by
Aug 31, 2026
Merged

Say who actually uses this, and which lane#16
AstroQore merged 2 commits into
mainfrom
docs/used-by

Conversation

@AstroQore

Copy link
Copy Markdown
Owner

Summary

Used by listed Vibe Bar, then the single word "Auspex.", and predated the Rust lane entirely.

It now names all three consumers and what each takes:

  • Vibe BarAgentSessionKit for the index, transcripts, deletion planning and the MCP transport.
  • Auspex — the only consumer of both products, and the only user of AgentSessionLive. That is the thing a reader most wants to know before touching that target, and the old entry did not say it.
  • Vibe Bar Desktopagent-session-core, so both Vibe Bar clients read sessions by one set of rules rather than two.

Also states the consequence of static linking that the versioning section explains but this list did not: a kit release reaches nobody until the app consuming it ships a build.

Docs only.

🤖 Generated with Claude Code

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>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T10:57:04.014597Z 8779666 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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>
@AstroQore
AstroQore merged commit 4e5c19d into main Aug 31, 2026
1 check passed
@AstroQore
AstroQore deleted the docs/used-by branch August 31, 2026 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant