execweave 0.7.7__tar.gz → 0.7.8__tar.gz

{execweave-0.7.7 → execweave-0.7.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: execweave
-Version: 0.7.7
+Version: 0.7.8
 Summary: Turn AI-agent runtime behavior into a local interactive execution graph.
 Project-URL: Homepage, https://github.com/Irish-kw/ExecWeave
 Project-URL: Repository, https://github.com/Irish-kw/ExecWeave
@@ -84,7 +84,7 @@ Install the latest published wheel/sdist from PyPI:
 python -m pip install -U execweave
 ```
 
-The current release is **v0.7.7**.
+The current release is **v0.7.8**.
 
 For development:
 
@@ -120,7 +120,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` keeps the Agent interactive in the launch terminal while opening/attaching the detached Top dashboard according to the host environment.
 
-**v0.7.7 — each agent's own conversation, while the run is still open.** The live dashboard showed every agent every other agent's conversation for the whole run and only became correct once the agent exited: it fetched the conversation index only at finalization, so the per-agent scoping never ran and a flat list of every stored record was drawn in its place — the same list whichever node was selected. That index is now projected from the run's current graph and served during the run, through the same builder the finalized file is written from, so a live dashboard and a recorded viewer cannot disagree about what belongs to an agent; the provider-neutral, agent-local multi-agent conversations each agent owns are the only thing either one draws. Neither viewer keeps a fallback that renders a conversation record outside that per-agent projection. A release check now opens both shipped viewers in a real browser and reads back what each agent shows, so an agent seeing another agent's conversation fails the build instead of reaching a release.
+**v0.7.8 — a conversation belongs to an agent, everywhere a person can click.** Selecting a node that is not an agent used to resolve to the same empty selection an unselected graph does, so a network endpoint or a process drew every agent's conversation; the selection kind is now tracked apart from the focused agent, and anything that is not an agent says so instead. A provider that prepends the same multi-kilobyte block to every subagent had it recorded where each agent's own assignment belongs, so four siblings rendered as four copies of one plugin catalogue: a text appearing verbatim under two or more agents is not any one agent's assignment, and is folded and named for what it is. Where several agents were read from one rollout — Codex records a child's delegation and return in the parent's file — only the agent that owns it offers the raw bytes, and the others name whose record their turns came from, so a link inside a child's section no longer opens the whole run. The provider-neutral, agent-local multi-agent conversations each agent owns are also projected during a run now, not only once it ends. A release check drives both shipped viewers in a real browser through every selection a person can make, so an agent seeing what is not its own fails a build instead of reaching a release.
 
 The unified dashboard brings the execution graph, logs, and conversation records into the same inspection flow. Finalized runs generate `conversations.md` and `conversations.json`, while validated provider transcripts are copied into the run-local SHA-256 content store. Claude Code, OpenAI Codex, Cursor, OpenCode, and Google Antigravity use the strongest provider-exposed multi-agent evidence available to each integration. For gateways and local runtimes that expose only root request/response traffic, ExecWeave shows only that root conversation and does not invent subagents or hidden routing.
 
@@ -329,7 +329,7 @@ Conversation isolation is an attribution/display rule, not a redaction boundary.
 
 ## Current status
 
-v0.7.7 combines cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, direct run-local conversation access, agent-local conversation isolation across provider-neutral projections, and per-agent conversation focus in the standalone and live dashboards. Supported integrations preserve the strongest identity/routing evidence actually exposed by each provider and abstain when that evidence is unavailable. Observed evidence and inference remain separate by design.
+v0.7.8 combines cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, direct run-local conversation access, agent-local conversation isolation across provider-neutral projections, and per-agent conversation focus in the standalone and live dashboards. Supported integrations preserve the strongest identity/routing evidence actually exposed by each provider and abstain when that evidence is unavailable. Observed evidence and inference remain separate by design.
 
 ## Documentation
 

{execweave-0.7.7 → execweave-0.7.8}/README.de.md

@@ -31,7 +31,7 @@ Installieren Sie das neueste veröffentlichte wheel/sdist von PyPI:
 python -m pip install -U execweave
 ```
 
-Die aktuelle Version ist **v0.7.7**.
+Die aktuelle Version ist **v0.7.8**.
 
 Für die Entwicklung:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` hält den Agent im Startterminal interaktiv und öffnet bzw. verbindet gleichzeitig das detached Top dashboard entsprechend der Host-Umgebung.
 
-**v0.7.7 — die eigene Conversation jedes Agents, während der Run noch offen ist.** Das Live-Dashboard zeigte jedem Agent den ganzen Run über die Conversation jedes anderen Agents und wurde erst korrekt, nachdem der Agent beendet war: Es holte den Conversation-Index erst bei der Finalisierung, sodass das Per-Agent-Scoping nie lief und stattdessen eine flache Liste aller gespeicherten Datensätze gezeichnet wurde — dieselbe Liste, gleich welcher Node ausgewählt war. Dieser Index wird nun aus dem aktuellen Graphen des Runs projiziert und während des Runs ausgeliefert, durch denselben Builder, aus dem die finalisierte Datei geschrieben wird; ein Live-Dashboard und ein aufgezeichneter Viewer können sich daher nicht darüber uneinig sein, was zu einem Agent gehört, und das Einzige, was beide zeichnen, sind die provider-neutralen, agent-lokalen Multi-Agent-Conversations, die jeder Agent besitzt. Keiner der beiden Viewer behält einen Fallback, der einen Conversation-Datensatz außerhalb dieser Per-Agent-Projektion rendert. Eine Release-Prüfung öffnet nun beide ausgelieferten Viewer in einem echten Browser und liest zurück, was jeder Agent zeigt: Ein Agent, der die Conversation eines anderen sieht, lässt den Build scheitern, statt in ein Release zu gelangen.
+**v0.7.8 — eine Conversation gehört einem Agent, überall wo eine Person klicken kann.** Die Auswahl eines Nodes, der kein Agent ist, löste sich zur selben leeren Auswahl auf wie ein nicht ausgewählter Graph, sodass ein Netzwerk-Endpunkt oder ein Prozess die Conversation jedes Agents zeichnete; die Art der Auswahl wird nun getrennt vom fokussierten Agent verfolgt, und was kein Agent ist, sagt das auch. Der mehrere Kilobyte große Block, den ein Provider jedem Subagent voranstellt, war dort aufgezeichnet, wo die eigene Zuweisung jedes Agents hingehört, sodass vier Geschwister als vier Kopien eines Plugin-Katalogs erschienen: Ein Text, der wortgleich unter zwei oder mehr Agents auftaucht, ist die Zuweisung keines von ihnen, wird gefaltet und benannt, was er ist. Wo mehrere Agents aus einem Rollout gelesen wurden — Codex hält die Delegation eines Kindes und dessen Rückgabe in der Datei des Elternteils fest — bietet nur der Agent, dem sie gehört, die Rohbytes an, und die übrigen nennen, aus wessen Aufzeichnung ihre Turns gelesen wurden, sodass ein Link in der Sektion eines Kindes nicht mehr den ganzen Run öffnet. Die provider-neutralen, agent-lokalen Multi-Agent-Conversations, die jeder Agent besitzt, werden nun während eines Runs projiziert, nicht erst wenn er endet. Eine Release-Prüfung führt beide ausgelieferten Viewer in einem echten Browser durch jede Auswahl, die eine Person treffen kann: Ein Agent, der sieht, was ihm nicht gehört, lässt den Build scheitern, statt in ein Release zu gelangen.
 
 Das vereinheitlichte Dashboard bringt execution graph, logs und conversation records in denselben Inspection-Flow. Finalisierte Runs erzeugen `conversations.md` und `conversations.json`; validierte Provider-Transcripts werden in den run-local SHA-256 content store kopiert. Claude Code, OpenAI Codex, Cursor, OpenCode und Google Antigravity verwenden jeweils die stärkste Multi-Agent-Evidence, die ihre Integration tatsächlich offenlegt. Wenn ein Gateway oder lokaler Runtime nur root request/response sichtbar macht, zeigt ExecWeave nur diese Root-Conversation und erfindet weder Subagents noch hidden routing.
 
@@ -276,7 +276,7 @@ Conversation isolation ist eine Attribution-/Display-Regel, keine Redaction Boun
 
 ## Aktueller Stand
 
-v0.7.7 kombiniert cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, konservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, direkten run-local conversation access agent-local conversation isolation in provider-neutralen Projektionen und per-agent conversation focus in den Standalone- und Live-Dashboards. Jede Integration bewahrt nur die stärkste identity/routing evidence, die der Provider tatsächlich offenlegt, und enthält sich, wenn diese Evidence fehlt. Observed evidence und inference bleiben konstruktiv getrennt.
+v0.7.8 kombiniert cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, konservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, direkten run-local conversation access agent-local conversation isolation in provider-neutralen Projektionen und per-agent conversation focus in den Standalone- und Live-Dashboards. Jede Integration bewahrt nur die stärkste identity/routing evidence, die der Provider tatsächlich offenlegt, und enthält sich, wenn diese Evidence fehlt. Observed evidence und inference bleiben konstruktiv getrennt.
 
 ## Dokumentation
 

{execweave-0.7.7 → execweave-0.7.8}/README.fr.md

@@ -31,7 +31,7 @@ Installez le dernier wheel/sdist publié depuis PyPI :
 python -m pip install -U execweave
 ```
 
-La version courante est **v0.7.7**.
+La version courante est **v0.7.8**.
 
 Pour le développement :
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` garde l’Agent interactif dans le terminal de lancement tout en ouvrant ou en attachant le dashboard Top détaché selon l’environnement hôte.
 
-**v0.7.7 — la conversation propre à chaque agent, pendant que le run est encore ouvert.** Le live dashboard montrait à chaque agent la conversation de tous les autres pendant tout le run et ne devenait correct qu'une fois l'agent terminé : il ne récupérait l'index des conversations qu'à la finalisation, si bien que le cadrage per-agent ne s'exécutait jamais et qu'une liste plate de tous les enregistrements stockés était dessinée à la place — la même liste quel que soit le node sélectionné. Cet index est désormais projeté depuis le graphe courant du run et servi pendant le run, à travers le même builder que celui qui écrit le fichier finalisé ; un live dashboard et un viewer enregistré ne peuvent donc pas diverger sur ce qui appartient à un agent, et la seule chose que l'un ou l'autre dessine sont les conversations multi-agent provider-neutral et agent-local que chaque agent possède. Aucun des deux viewers ne conserve un repli qui rendrait un enregistrement de conversation hors de cette projection per-agent. Une vérification de release ouvre maintenant les deux viewers livrés dans un vrai navigateur et relit ce que montre chaque agent : un agent voyant la conversation d'un autre fait échouer la construction au lieu d'atteindre une release.
+**v0.7.8 — une conversation appartient à un agent, partout où une personne peut cliquer.** Sélectionner un node qui n'est pas un agent se résolvait comme la sélection vide d'un graphe non sélectionné, si bien qu'un point de terminaison réseau ou un processus dessinait la conversation de tous les agents ; le type de sélection est désormais suivi séparément de l'agent ciblé, et ce qui n'est pas un agent le dit. Le bloc de plusieurs kilo-octets qu'un provider ajoute devant chaque subagent était enregistré là où appartient l'assignation propre de chaque agent, si bien que quatre frères s'affichaient comme quatre copies d'un même catalogue de plugins : un texte apparaissant mot pour mot sous deux agents ou plus n'est l'assignation d'aucun d'eux, il est plié et nommé pour ce qu'il est. Lorsque plusieurs agents ont été lus depuis un seul rollout — Codex enregistre la délégation d'un enfant et son retour dans le fichier du parent — seul l'agent qui le possède offre les octets bruts, et les autres nomment le registre d'où viennent leurs turns, si bien qu'un lien dans la section d'un enfant n'ouvre plus le run entier. Les conversations multi-agent provider-neutral et agent-local que chaque agent possède sont désormais projetées pendant un run, et non une fois seulement qu'il est terminé. Une vérification de release pilote les deux viewers livrés dans un vrai navigateur à travers chaque sélection possible : un agent voyant ce qui ne lui appartient pas fait échouer la construction au lieu d'atteindre une release.
 
 Le dashboard unifié rassemble execution graph, logs et conversation records dans le même flux d’inspection. Les runs finalisés génèrent `conversations.md` et `conversations.json`, et les transcripts provider validés sont copiés dans le content store SHA-256 local au run. Claude Code, OpenAI Codex, Cursor, OpenCode et Google Antigravity exploitent chacun le niveau de multi-agent evidence réellement exposé par leur integration. Lorsqu’un gateway ou un local runtime n’expose que des request/response root, ExecWeave affiche uniquement cette root conversation et n’invente ni subagent ni hidden routing.
 
@@ -276,7 +276,7 @@ La conversation isolation est une règle d’attribution et d’affichage, pas u
 
 ## État actuel
 
-v0.7.7 combine cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, accès direct aux conversations run-local agent-local conversation isolation dans les projections provider-neutral et per-agent conversation focus dans les dashboards standalone et live. Chaque integration conserve uniquement la meilleure identity/routing evidence réellement exposée par le provider et s’abstient lorsque cette evidence manque. Observed evidence et inference restent séparées par conception.
+v0.7.8 combine cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, accès direct aux conversations run-local agent-local conversation isolation dans les projections provider-neutral et per-agent conversation focus dans les dashboards standalone et live. Chaque integration conserve uniquement la meilleure identity/routing evidence réellement exposée par le provider et s’abstient lorsque cette evidence manque. Observed evidence et inference restent séparées par conception.
 
 ## Documentation
 

{execweave-0.7.7 → execweave-0.7.8}/README.ja.md

@@ -31,7 +31,7 @@ PyPI から最新の wheel/sdist をインストールします。
 python -m pip install -U execweave
 ```
 
-現在のリリースは **v0.7.7** です。
+現在のリリースは **v0.7.8** です。
 
 開発環境では次のようにインストールできます。
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` は Agent を起動 terminal 上でインタラクティブなまま保ち、ホスト環境に応じて detached Top dashboard を開くか既存のものに attach します。
 
-**v0.7.7 — 実行中でも、各 agent は自分自身の conversation だけを見る。** live dashboard は実行中ずっと、すべての agent に他の agent の conversation を見せており、agent が終了して初めて正しくなっていました。conversation index を finalization でしか取得しなかったため per-agent scoping が一度も実行されず、代わりに保存済みレコードを平坦に並べた一覧が描かれ、どの node を選んでも同じ一覧でした。この index は実行中の graph から投影され、finalized ファイルが書き出されるのと同じ builder を通して実行中に提供されます。したがって live dashboard と recorded viewer が「何がどの agent のものか」で食い違うことはなく、両者が描くのは各 agent が保持する provider-neutral かつ agent-local な multi-agent conversation だけです。どちらの viewer も、per-agent projection を経ない conversation record を描く fallback を保持しません。リリース前の検査は実物のブラウザで両方の viewer を開き、各 agent が示す内容を読み返すため、agent が他の agent の conversation を見る状態は release に届く前にビルドを失敗させます。
+**v0.7.8 — conversation は agent のものであり、それは人がクリックできるすべての場所で成り立つ。** agent ではない node の選択は、何も選ばれていない状態と同じものに解決されていたため、network endpoint や process がすべての agent の conversation を描いていました。選択の種類は焦点の agent とは別に追跡され、agent でないものはそう述べます。provider がすべての subagent の前に付ける同一の数キロバイトのブロックは各 agent 自身の assignment の位置に記録されており、四つの兄弟が同じプラグイン一覧の四つの複製として描かれていました。二つ以上の agent の下に一字一句同じ形で現れるテキストは、どの agent の assignment でもありません。折りたたまれ、実態どおりに名付けられます。複数の agent が一つの rollout から読まれている場合 — Codex は child の委任と返答を親のファイルに記録します — 生のバイト列を提供するのはそれを所有する agent だけで、他は自分の turn がどの記録から読まれたかを示すため、child のセクション内のリンクが run 全体を開くことはありません。各 agent が保持する provider-neutral かつ agent-local な multi-agent conversation は、実行が終わったあとだけでなく実行中にも投影されます。リリース前の検査は実物のブラウザで両方の viewer を、人が行えるあらゆる選択にわたって駆動するため、agent が自分のものでないものを見る状態は release に届く前にビルドを失敗させます。
 
 統合 dashboard では execution graph、logs、conversation records を同じ inspection flow で確認できます。Finalized run は `conversations.md` と `conversations.json` を生成し、検証済み provider transcript は run-local SHA-256 content store にコピーされます。Claude Code、OpenAI Codex、Cursor、OpenCode、Google Antigravity は、それぞれが実際に公開する最も強い multi-agent evidence を利用します。gateway や local runtime が root request/response しか公開しない場合、ExecWeave は root conversation だけを表示し、subagent や hidden routing を捏造しません。
 
@@ -276,7 +276,7 @@ Conversation isolation は attribution/display の規則であり redaction boun
 
 ## 現在の状態
 
-v0.7.7 は cross-platform runtime collection、materialized execution graph、standalone/live dashboard、保守的な provider↔runtime correlation、content-addressed full-fidelity provider evidence、attributable multi-agent execution trace、run-local conversation access、provider-neutral projection 上の agent-local conversation isolation、standalone および live dashboard での per-agent conversation focus を統合します。各 integration は provider が実際に公開した最も強い identity/routing evidence のみを保持し、不足する場合は abstain します。Observed evidence と inference は設計上分離されたままです。
+v0.7.8 は cross-platform runtime collection、materialized execution graph、standalone/live dashboard、保守的な provider↔runtime correlation、content-addressed full-fidelity provider evidence、attributable multi-agent execution trace、run-local conversation access、provider-neutral projection 上の agent-local conversation isolation、standalone および live dashboard での per-agent conversation focus を統合します。各 integration は provider が実際に公開した最も強い identity/routing evidence のみを保持し、不足する場合は abstain します。Observed evidence と inference は設計上分離されたままです。
 
 ## ドキュメント
 

{execweave-0.7.7 → execweave-0.7.8}/README.ko.md

@@ -31,7 +31,7 @@ PyPI에서 최신 wheel/sdist를 설치합니다.
 python -m pip install -U execweave
 ```
 
-현재 릴리스는 **v0.7.7** 입니다.
+현재 릴리스는 **v0.7.8** 입니다.
 
 개발 설치:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex`는 Agent를 시작 terminal에서 interactive 상태로 유지하면서 host 환경에 따라 detached Top dashboard를 열거나 attach합니다.
 
-**v0.7.7 — 실행 중에도 각 agent 는 자신의 conversation 만 본다.** live dashboard 는 실행 내내 모든 agent 에게 다른 agent 의 conversation 을 보여 주었고, agent 가 종료된 뒤에야 올바르게 동작했습니다. conversation index 를 finalization 에서만 가져왔기 때문에 per-agent scoping 이 한 번도 실행되지 않았고, 그 자리에 저장된 모든 레코드를 평평하게 나열한 목록이 그려졌으며 어떤 node 를 선택하든 같은 목록이었습니다. 이제 그 index 는 실행 중인 graph 에서 투영되어, finalized 파일이 기록되는 것과 동일한 builder 를 거쳐 실행 중에 제공됩니다. 따라서 live dashboard 와 recorded viewer 가 무엇이 어떤 agent 의 것인지에 대해 어긋날 수 없으며, 둘이 그리는 것은 각 agent 가 소유한 provider-neutral, agent-local multi-agent conversation 뿐입니다. 두 viewer 모두 per-agent projection 을 거치지 않은 conversation record 를 그리는 fallback 을 남기지 않습니다. 릴리스 검사는 이제 실제 브라우저로 두 viewer 를 열어 각 agent 가 보여 주는 내용을 되읽으므로, agent 가 다른 agent 의 conversation 을 보는 상태는 release 에 도달하는 대신 빌드를 실패시킵니다.
+**v0.7.8 — conversation 은 agent 의 것이며, 사람이 클릭할 수 있는 모든 곳에서 그렇다.** agent 가 아닌 node 를 선택하면 아무것도 선택하지 않은 상태와 같은 값으로 해석되어, network endpoint 나 process 가 모든 agent 의 conversation 을 그렸습니다. 이제 선택의 종류를 초점이 맞춰진 agent 와 분리해 추적하며, agent 가 아닌 것은 그렇다고 말합니다. provider 가 모든 subagent 앞에 붙이는 동일한 수 킬로바이트 블록이 각 agent 자신의 assignment 자리에 기록되어, 네 형제가 같은 플러그인 목록의 사본 넷으로 그려졌습니다. 둘 이상의 agent 아래에 한 글자도 다르지 않게 나타나는 텍스트는 어느 agent 의 assignment 도 아니므로, 접히고 실제 그대로 이름 붙습니다. 여러 agent 가 하나의 rollout 에서 읽힌 경우 — Codex 는 child 의 위임과 반환을 부모의 파일에 기록합니다 — 원본 바이트를 제공하는 것은 그것을 소유한 agent 뿐이며, 나머지는 자신의 turn 이 누구의 기록에서 읽혔는지 밝히므로 child 섹션의 링크가 run 전체를 열지 않습니다. 각 agent 가 소유한 provider-neutral, agent-local multi-agent conversation 은 실행이 끝난 뒤가 아니라 실행 중에도 투영됩니다. 릴리스 검사는 실제 브라우저로 두 viewer 를 사람이 할 수 있는 모든 선택에 걸쳐 구동하므로, agent 가 자기 것이 아닌 것을 보는 상태는 release 에 도달하는 대신 빌드를 실패시킵니다.
 
 통합 dashboard는 execution graph, logs, conversation records를 하나의 inspection flow에서 제공합니다. Finalized run은 `conversations.md`와 `conversations.json`을 만들며, 검증된 provider transcript는 run-local SHA-256 content store로 복사됩니다. Claude Code, OpenAI Codex, Cursor, OpenCode, Google Antigravity는 각 integration이 실제로 노출하는 가장 강한 multi-agent evidence를 사용합니다. gateway나 local runtime이 root request/response만 노출하면 ExecWeave는 root conversation만 보여 주며 subagent나 hidden routing을 만들어내지 않습니다.
 
@@ -276,7 +276,7 @@ Conversation isolation은 attribution/display 규칙이지 redaction boundary가
 
 ## 현재 상태
 
-v0.7.7는 cross-platform runtime collection, materialized execution graph, standalone/live dashboard, 보수적인 provider↔runtime correlation, content-addressed full-fidelity provider evidence, attributable multi-agent execution trace, run-local conversation access, provider-neutral projection의 agent-local conversation isolation, standalone 및 live dashboard의 per-agent conversation focus를 통합합니다. 각 integration은 provider가 실제로 노출한 가장 강한 identity/routing evidence만 보존하고 충분한 증거가 없으면 abstain합니다. Observed evidence와 inference는 설계상 계속 분리됩니다.
+v0.7.8는 cross-platform runtime collection, materialized execution graph, standalone/live dashboard, 보수적인 provider↔runtime correlation, content-addressed full-fidelity provider evidence, attributable multi-agent execution trace, run-local conversation access, provider-neutral projection의 agent-local conversation isolation, standalone 및 live dashboard의 per-agent conversation focus를 통합합니다. 각 integration은 provider가 실제로 노출한 가장 강한 identity/routing evidence만 보존하고 충분한 증거가 없으면 abstain합니다. Observed evidence와 inference는 설계상 계속 분리됩니다.
 
 ## 문서
 

{execweave-0.7.7 → execweave-0.7.8}/README.md

@@ -31,7 +31,7 @@ Install the latest published wheel/sdist from PyPI:
 python -m pip install -U execweave
 ```
 
-The current release is **v0.7.7**.
+The current release is **v0.7.8**.
 
 For development:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` keeps the Agent interactive in the launch terminal while opening/attaching the detached Top dashboard according to the host environment.
 
-**v0.7.7 — each agent's own conversation, while the run is still open.** The live dashboard showed every agent every other agent's conversation for the whole run and only became correct once the agent exited: it fetched the conversation index only at finalization, so the per-agent scoping never ran and a flat list of every stored record was drawn in its place — the same list whichever node was selected. That index is now projected from the run's current graph and served during the run, through the same builder the finalized file is written from, so a live dashboard and a recorded viewer cannot disagree about what belongs to an agent; the provider-neutral, agent-local multi-agent conversations each agent owns are the only thing either one draws. Neither viewer keeps a fallback that renders a conversation record outside that per-agent projection. A release check now opens both shipped viewers in a real browser and reads back what each agent shows, so an agent seeing another agent's conversation fails the build instead of reaching a release.
+**v0.7.8 — a conversation belongs to an agent, everywhere a person can click.** Selecting a node that is not an agent used to resolve to the same empty selection an unselected graph does, so a network endpoint or a process drew every agent's conversation; the selection kind is now tracked apart from the focused agent, and anything that is not an agent says so instead. A provider that prepends the same multi-kilobyte block to every subagent had it recorded where each agent's own assignment belongs, so four siblings rendered as four copies of one plugin catalogue: a text appearing verbatim under two or more agents is not any one agent's assignment, and is folded and named for what it is. Where several agents were read from one rollout — Codex records a child's delegation and return in the parent's file — only the agent that owns it offers the raw bytes, and the others name whose record their turns came from, so a link inside a child's section no longer opens the whole run. The provider-neutral, agent-local multi-agent conversations each agent owns are also projected during a run now, not only once it ends. A release check drives both shipped viewers in a real browser through every selection a person can make, so an agent seeing what is not its own fails a build instead of reaching a release.
 
 The unified dashboard brings the execution graph, logs, and conversation records into the same inspection flow. Finalized runs generate `conversations.md` and `conversations.json`, while validated provider transcripts are copied into the run-local SHA-256 content store. Claude Code, OpenAI Codex, Cursor, OpenCode, and Google Antigravity use the strongest provider-exposed multi-agent evidence available to each integration. For gateways and local runtimes that expose only root request/response traffic, ExecWeave shows only that root conversation and does not invent subagents or hidden routing.
 
@@ -276,7 +276,7 @@ Conversation isolation is an attribution/display rule, not a redaction boundary.
 
 ## Current status
 
-v0.7.7 combines cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, direct run-local conversation access, agent-local conversation isolation across provider-neutral projections, and per-agent conversation focus in the standalone and live dashboards. Supported integrations preserve the strongest identity/routing evidence actually exposed by each provider and abstain when that evidence is unavailable. Observed evidence and inference remain separate by design.
+v0.7.8 combines cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, direct run-local conversation access, agent-local conversation isolation across provider-neutral projections, and per-agent conversation focus in the standalone and live dashboards. Supported integrations preserve the strongest identity/routing evidence actually exposed by each provider and abstain when that evidence is unavailable. Observed evidence and inference remain separate by design.
 
 ## Documentation
 

{execweave-0.7.7 → execweave-0.7.8}/README.ru.md

@@ -31,7 +31,7 @@ ExecWeave — source-available, local-first проект наблюдаемос
 python -m pip install -U execweave
 ```
 
-Текущая версия — **v0.7.7**.
+Текущая версия — **v0.7.8**.
 
 Для разработки:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` оставляет Agent интерактивным в стартовом terminal и одновременно открывает либо подключает detached Top dashboard в зависимости от host environment.
 
-**v0.7.7 — собственный conversation каждого agent, пока прогон ещё открыт.** Live dashboard весь прогон показывал каждому agent conversation всех остальных и становился правильным лишь после завершения agent: он забирал conversation index только при finalization, поэтому per-agent scoping не выполнялся ни разу, а вместо него рисовался плоский список всех сохранённых записей — один и тот же, какой бы node ни был выбран. Теперь этот index проецируется из текущего графа прогона и отдаётся во время прогона через тот же builder, из которого пишется финализированный файл, поэтому live dashboard и записанный viewer не могут разойтись в том, что принадлежит agent; единственное, что рисует любой из них, — это provider-neutral, agent-local multi-agent conversations, которыми владеет каждый agent. Ни один из viewers не сохраняет запасной путь, рисующий запись conversation в обход этой per-agent projection. Релизная проверка теперь открывает оба поставляемые viewers в настоящем браузере и считывает, что показывает каждый agent, поэтому agent, видящий чужой conversation, роняет сборку вместо того, чтобы попасть в release.
+**v0.7.8 — conversation принадлежит agent, в каждом месте, куда человек может кликнуть.** Выбор node, который не является agent, разрешался в ту же пустую выборку, что и невыбранный граф, поэтому сетевая конечная точка или процесс рисовали conversation всех agents; вид выборки теперь отслеживается отдельно от сфокусированного agent, а то, что не является agent, так и говорит. Многокилобайтный блок, который provider добавляет перед каждым subagent, записывался там, где находится собственное задание каждого agent, и четыре брата отображались как четыре копии одного каталога плагинов: текст, появляющийся дословно под двумя и более agents, не является заданием ни одного из них — он сворачивается и называется тем, что он есть. Там, где несколько agents были прочитаны из одного rollout — Codex записывает делегирование ребёнка и его возврат в файл родителя — сырые байты предлагает только тот agent, которому файл принадлежит, а остальные называют, из чьей записи прочитаны их turns, поэтому ссылка внутри секции ребёнка больше не открывает весь прогон. Provider-neutral, agent-local multi-agent conversations, которыми владеет каждый agent, теперь проецируются во время прогона, а не только после его завершения. Релизная проверка ведёт оба поставляемых viewers в настоящем браузере через каждый выбор, который может сделать человек: agent, видящий не своё, роняет сборку вместо того, чтобы попасть в release.
 
 Единый dashboard объединяет execution graph, logs и conversation records в одном inspection flow. Finalized runs создают `conversations.md` и `conversations.json`, а проверенные provider transcripts копируются в run-local SHA-256 content store. Claude Code, OpenAI Codex, Cursor, OpenCode и Google Antigravity используют наиболее сильную multi-agent evidence, которую реально раскрывает соответствующая integration. Если gateway или local runtime показывает только root request/response, ExecWeave отображает только root conversation и не выдумывает subagents или hidden routing.
 
@@ -276,7 +276,7 @@ Conversation isolation — это правило attribution/display, а не re
 
 ## Текущий статус
 
-v0.7.7 объединяет cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, прямой run-local conversation access agent-local conversation isolation в provider-neutral projections и per-agent conversation focus в standalone и live dashboards. Каждая integration сохраняет только наиболее сильную identity/routing evidence, реально раскрытую provider, и abstain-ит при её отсутствии. Observed evidence и inference по-прежнему разделены архитектурно.
+v0.7.8 объединяет cross-platform runtime collection, materialized execution graphs, standalone/live dashboards, conservative provider↔runtime correlation, full-fidelity content-addressed provider evidence, attributable multi-agent execution traces, прямой run-local conversation access agent-local conversation isolation в provider-neutral projections и per-agent conversation focus в standalone и live dashboards. Каждая integration сохраняет только наиболее сильную identity/routing evidence, реально раскрытую provider, и abstain-ит при её отсутствии. Observed evidence и inference по-прежнему разделены архитектурно.
 
 ## Документация
 

{execweave-0.7.7 → execweave-0.7.8}/README.zh-CN.md

@@ -31,7 +31,7 @@ ExecWeave 是一个 source-available、local-first 的可观测性项目，把 A
 python -m pip install -U execweave
 ```
 
-当前正式版本是 **v0.7.7**。
+当前正式版本是 **v0.7.8**。
 
 开发安装：
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` 会让 Agent 保持在启动 terminal 中交互，并根据主机环境打开或附加 detached Top dashboard。
 
-**v0.7.7 — 运行期间就只看得到自己那一份对话。** live dashboard 在整段运行期间让每个 agent 都看得到其他 agent 的对话，要等 agent 结束才会正确：它只在 finalization 才去取 conversation index，因此 per-agent scoping 从未执行，画面改由一份平铺的全部记录清单顶替，而且不论选取哪个 node 都是同一份。现在该 index 改为从运行中的 graph 投影并在运行期间供应，走的是与 finalized 文件相同的 builder，因此 live dashboard 与 recorded viewer 不可能对「什么属于哪个 agent」有不同答案；两者唯一会画出的，就是每个 agent 各自拥有的 provider-neutral、agent-local multi-agent conversation。两个 viewer 都不再保留任何会绕过 per-agent projection 的 fallback。发布前的检查现在会用真实浏览器打开两种 viewer 并读回每个 agent 显示的内容，因此 agent 看到别人的对话会让构建失败，而不是流到 release。
+**v0.7.8 — 对话属于 agent，在每一个点得下去的地方都成立。** 选取非 agent 的 node 以前会落到与「什么都没选」相同的状态，因此一个网络端点或进程就能画出所有 agent 的对话；现在选取种类与聚焦的 agent 分开追踪，不是 agent 就明说。provider 在每个 subagent 前面加上的同一段数 KB 内容，被记在各 agent 自己的交办栏位，于是四个兄弟渲染成四份相同的插件清单：一段文字若逐字出现在两个以上 agent 身上，它就不是任何一个 agent 的交办，因此折叠并如实命名。多个 agent 读自同一份 rollout 时——Codex 把 child 的交办与回复记在父层文件里——只有拥有它的 agent 提供原始字节，其余显示证据来自谁，child 区块里的链接不再打开整个 run。每个 agent 各自拥有的 provider-neutral、agent-local multi-agent conversation 现在也会在运行期间投影，而非只在结束后。发布前的检查会用真实浏览器把两个 viewer 走过每一种可操作的选取，因此 agent 看到不属于自己的内容会让构建失败，而不是流到 release。
 
 统一 dashboard 把 execution graph、logs 与 conversation records 放进同一条 inspection flow。Finalized run 会生成 `conversations.md` 与 `conversations.json`，经过验证的 provider transcript 也会复制进 run-local SHA-256 content store。Claude Code、OpenAI Codex、Cursor、OpenCode 与 Google Antigravity 都依据各自实际暴露的 evidence 强度建立 multi-agent trace；如果 gateway 或 local runtime 只提供 root request/response，ExecWeave 就只显示 root conversation，不会虚构 subagent 或 hidden routing。
 
@@ -276,7 +276,7 @@ Conversation isolation 是 attribution/display 规则，而不是 redaction boun
 
 ## 当前状态
 
-v0.7.7 组合 cross-platform runtime collection、materialized execution graph、standalone/live dashboard、保守的 provider↔runtime correlation、content-addressed full-fidelity provider evidence、可归属的 multi-agent execution trace、run-local conversation access，provider-neutral projection 上的 agent-local conversation isolation，以及 standalone 与 live dashboard 上的 per-agent conversation focus。各 integration 只保留 provider 实际暴露的最强 identity/routing evidence，证据不足时选择 abstain。Observed evidence 与 inference 从设计上保持分离。
+v0.7.8 组合 cross-platform runtime collection、materialized execution graph、standalone/live dashboard、保守的 provider↔runtime correlation、content-addressed full-fidelity provider evidence、可归属的 multi-agent execution trace、run-local conversation access，provider-neutral projection 上的 agent-local conversation isolation，以及 standalone 与 live dashboard 上的 per-agent conversation focus。各 integration 只保留 provider 实际暴露的最强 identity/routing evidence，证据不足时选择 abstain。Observed evidence 与 inference 从设计上保持分离。
 
 ## 文档
 

{execweave-0.7.7 → execweave-0.7.8}/README.zh-TW.md

@@ -31,7 +31,7 @@ ExecWeave 是一個 source-available、local-first 的可觀測性專案，會
 python -m pip install -U execweave
 ```
 
-目前正式版本是 **v0.7.7**。
+目前正式版本是 **v0.7.8**。
 
 開發安裝：
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` 會讓 Agent 保持在啟動 terminal 中互動，並依主機環境開啟或附加 detached Top dashboard。
 
-**v0.7.7 — 執行期間就只看得到自己那一份對話。** live dashboard 在整段執行期間讓每個 agent 都看得到其他 agent 的對話，要等 agent 結束才會正確：它只在 finalization 才去取 conversation index，因此 per-agent scoping 從未執行，畫面改由一份平鋪的全部記錄清單頂替，而且不論選取哪個 node 都是同一份。現在該 index 改為從執行中的 graph 投影並在執行期間供應，走的是與 finalized 檔案相同的 builder，因此 live dashboard 與 recorded viewer 不可能對「什麼屬於哪個 agent」有不同答案；兩者唯一會畫出的，就是每個 agent 各自擁有的 provider-neutral、agent-local multi-agent conversation。兩個 viewer 都不再保留任何會繞過 per-agent projection 的 fallback。發布前的檢查現在會用真實瀏覽器開啟兩種 viewer 並讀回每個 agent 顯示的內容，因此 agent 看到別人的對話會讓建置失敗，而不是流到 release。
+**v0.7.8 — 對話屬於 agent，在每一個點得下去的地方都成立。** 選取非 agent 的 node 以前會落到與「什麼都沒選」相同的狀態，因此一個網路端點或行程就能畫出所有 agent 的對話；現在選取種類與聚焦的 agent 分開追蹤，不是 agent 就明說。provider 在每個 subagent 前面加上的同一段數 KB 內容，被記在各 agent 自己的交辦欄位，於是四個兄弟渲染成四份相同的外掛清單：一段文字若逐字出現在兩個以上 agent 身上，它就不是任何一個 agent 的交辦，因此折疊並如實命名。多個 agent 讀自同一份 rollout 時——Codex 把 child 的交辦與回覆記在父層檔案裡——只有擁有它的 agent 提供原始位元組，其餘顯示證據來自誰，child 區塊裡的連結不再打開整個 run。每個 agent 各自擁有的 provider-neutral、agent-local multi-agent conversation 現在也會在執行期間投影，而非只在結束後。發布前的檢查會用真實瀏覽器把兩個 viewer 走過每一種可操作的選取，因此 agent 看到不屬於自己的內容會讓建置失敗，而不是流到 release。
 
 統一 dashboard 把 execution graph、logs 與 conversation records 放進同一條 inspection flow。Finalized run 會產生 `conversations.md` 與 `conversations.json`，經驗證的 provider transcript 也會複製進 run-local SHA-256 content store。Claude Code、OpenAI Codex、Cursor、OpenCode 與 Google Antigravity 都依各自實際曝露的 evidence 強度建立 multi-agent trace；若 gateway 或 local runtime 只提供 root request/response，ExecWeave 就只顯示 root conversation，不會虛構 subagent 或 hidden routing。
 
@@ -276,7 +276,7 @@ Conversation isolation 是 attribution/display 規則，不是 redaction boundar
 
 ## 目前狀態
 
-v0.7.7 整合 cross-platform runtime collection、materialized execution graph、standalone/live dashboard、保守的 provider↔runtime correlation、content-addressed full-fidelity provider evidence、可歸屬的 multi-agent execution trace、run-local conversation access，provider-neutral projection 上的 agent-local conversation isolation，以及 standalone 與 live dashboard 上的 per-agent conversation focus。各 integration 只保留 provider 實際曝露的最強 identity/routing evidence，證據不足時選擇 abstain。Observed evidence 與 inference 仍從設計上分離。
+v0.7.8 整合 cross-platform runtime collection、materialized execution graph、standalone/live dashboard、保守的 provider↔runtime correlation、content-addressed full-fidelity provider evidence、可歸屬的 multi-agent execution trace、run-local conversation access，provider-neutral projection 上的 agent-local conversation isolation，以及 standalone 與 live dashboard 上的 per-agent conversation focus。各 integration 只保留 provider 實際曝露的最強 identity/routing evidence，證據不足時選擇 abstain。Observed evidence 與 inference 仍從設計上分離。
 
 ## 文件
 

{execweave-0.7.7 → execweave-0.7.8}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "hatchling.build"
 
 [project]
 name = "execweave"
-# ExecWeave v0.7.7 release metadata
-version = "0.7.7"
+# ExecWeave v0.7.8 release metadata
+version = "0.7.8"
 description = "Turn AI-agent runtime behavior into a local interactive execution graph."
 readme = "README.md"
 requires-python = ">=3.10"

{execweave-0.7.7 → execweave-0.7.8}/src/execweave/__init__.py

@@ -1,3 +1,3 @@
 """ExecWeave runtime graph package."""
 
-__version__ = "0.7.7"
+__version__ = "0.7.8"

{execweave-0.7.7 → execweave-0.7.8}/src/execweave/_conversation_records_core.py

@@ -697,6 +697,89 @@ def _render_markdown(entries: list[dict[str, Any]]) -> str:
     return "\n".join(lines)
 
 
+# A provider may prepend the same block to every subagent it spawns — Codex sends a
+# plugin catalogue and an environment context, several kilobytes of it, recorded in the
+# rollout exactly where that agent's own assignment belongs. Read literally, every
+# sibling was handed an identical multi-kilobyte task and the panel shows four agents
+# that look the same.
+#
+# Nothing about the provider needs to be recognised to see that this is wrong. A text
+# that appears verbatim under two or more agents is, by that fact alone, not any one
+# agent's own assignment. It is marked here, once, in the index both viewers read, so
+# neither has to detect it and they cannot disagree about it.
+SHARED_INJECTED_CONTEXT = "shared_injected_context"
+_MIN_SHARED_CONTEXT_LENGTH = 400
+
+
+def _mark_shared_injected_context(entries: list[dict[str, Any]]) -> None:
+    agents_by_text: dict[str, set[str]] = {}
+    for entry in entries:
+        preview = entry.get("conversation_preview")
+        if not isinstance(preview, dict):
+            continue
+        agent_path = preview.get("agent_path")
+        if not isinstance(agent_path, str) or not agent_path:
+            continue
+        for message in preview.get("messages") or []:
+            if not isinstance(message, dict):
+                continue
+            text = message.get("text")
+            if not isinstance(text, str) or len(text) < _MIN_SHARED_CONTEXT_LENGTH:
+                continue
+            agents_by_text.setdefault(text, set()).add(agent_path)
+
+    shared = {text for text, agents in agents_by_text.items() if len(agents) > 1}
+    if not shared:
+        return
+    for entry in entries:
+        preview = entry.get("conversation_preview")
+        if not isinstance(preview, dict):
+            continue
+        for message in preview.get("messages") or []:
+            if isinstance(message, dict) and message.get("text") in shared:
+                message["content_role"] = SHARED_INJECTED_CONTEXT
+
+
+# One rollout can be the evidence for several agents: Codex records a delegation and
+# the return it receives in the parent's file, so a child's turns are read from the
+# parent's record rather than from one of its own. Every agent then cited that file as
+# its own raw evidence, and the link inside a child's section opened the whole run.
+#
+# The file is still the evidence and has to stay inspectable, so it is attributed
+# instead of hidden: the agent highest in the path hierarchy among those citing it owns
+# it, and the others say whose record their turns were read from.
+EVIDENCE_SHARED_WITH_OWNER = "evidence_shared_with_owner"
+
+
+def _mark_shared_evidence(entries: list[dict[str, Any]]) -> None:
+    agents_by_path: dict[str, set[str]] = {}
+    for entry in entries:
+        preview = entry.get("conversation_preview")
+        relative = entry.get("path")
+        if not isinstance(preview, dict) or not isinstance(relative, str) or not relative:
+            continue
+        agent_path = preview.get("agent_path")
+        if isinstance(agent_path, str) and agent_path:
+            agents_by_path.setdefault(relative, set()).add(agent_path)
+
+    owners = {
+        relative: min(agents, key=lambda path: (path.count("/"), len(path), path))
+        for relative, agents in agents_by_path.items()
+        if len(agents) > 1
+    }
+    if not owners:
+        return
+    for entry in entries:
+        preview = entry.get("conversation_preview")
+        relative = entry.get("path")
+        if not isinstance(preview, dict) or not isinstance(relative, str):
+            continue
+        owner = owners.get(relative)
+        if owner is None or preview.get("agent_path") == owner:
+            continue
+        entry[EVIDENCE_SHARED_WITH_OWNER] = owner
+
+
 def conversation_index_payload(
     graph: dict[str, Any],
     run_root: str | Path,
@@ -710,6 +793,8 @@ def conversation_index_payload(
     """
     root = Path(run_root).expanduser().resolve()
     entries = conversation_record_entries(graph, root)
+    _mark_shared_injected_context(entries)
+    _mark_shared_evidence(entries)
     visible_message_count = sum(
         len(preview.get("messages") or [])
         for entry in entries
@@ -728,11 +813,19 @@ def conversation_index_payload(
 def write_conversation_records(
     graph: dict[str, Any],
     run_root: str | Path,
+    *,
+    payload: dict[str, Any] | None = None,
 ) -> tuple[Path, Path]:
-    """Write deterministic JSON + Markdown indexes beside the viewer artifacts."""
+    """Write deterministic JSON + Markdown indexes beside the viewer artifacts.
+
+    A caller that already built the index passes it in rather than letting a second
+    projection run: the standalone viewer embeds these same entries, and a viewer
+    built from its own projection is free to disagree with the file beside it.
+    """
     root = Path(run_root).expanduser().resolve()
     root.mkdir(parents=True, exist_ok=True)
-    payload = conversation_index_payload(graph, root)
+    if payload is None:
+        payload = conversation_index_payload(graph, root)
     entries = payload["entries"]
     json_path = root / "conversations.json"
     markdown_path = root / "conversations.md"