execweave 0.7.4__tar.gz → 0.7.6__tar.gz

execweave-0.7.6/.github/workflows/provider-capability-stage-integrity.yml

@@ -0,0 +1,48 @@
+name: Provider Capability Stage Integrity
+
+# No path filter. This job guards release red lines — the disabled CONNECT handler,
+# the existing test set, the conversation completeness vocabulary, release metadata —
+# so it must run on every pull request. A filter listing only the capability-probe
+# files would arm the guard exactly when the guarded files are NOT the ones changing:
+# a pull request that weakens http_proxy.py, deletes a test, or bumps the version
+# while touching none of those paths would skip this job entirely.
+on:
+  pull_request:
+  workflow_dispatch:
+    inputs:
+      baseline_ref:
+        description: Base commit or ref used to reconstruct baseline test node IDs
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  integrity:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out pull request
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Install
+        run: python -m pip install -e ".[dev]"
+
+      # Every --allow-test-change lives here on purpose: it names the file and the
+      # reason in the workflow diff and in the job output, so editing an existing
+      # test is never something that happens quietly. It cannot remove a test —
+      # deletions and renames stay refused and the node-ID floor still requires
+      # every baseline test to survive.
+      - name: Validate stage integrity
+        run: >-
+          python scripts/check_release_stage_integrity.py
+          --baseline-ref "${{ github.event.pull_request.base.sha || inputs.baseline_ref }}"
+          --allow-test-change "tests/test_dashboard_information_architecture.py=the assertion pinned the colliding eight-character id fallback, which was the defect itself; the labels-are-provider-neutral subject is unchanged and still asserted"

{execweave-0.7.4 → execweave-0.7.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: execweave
-Version: 0.7.4
+Version: 0.7.6
 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
@@ -82,7 +82,7 @@ Install the latest published wheel/sdist from PyPI:
 python -m pip install -U execweave
 ```
 
-The current release is **v0.7.4**.
+The current release is **v0.7.6**.
 
 For development:
 
@@ -118,7 +118,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.4 — per-agent conversation focus in the dashboard.** Building on the provider-neutral, agent-local multi-agent conversations materialized in v0.7.3, selecting an agent node now scopes the conversation panel to that agent alone, with its visible item count and a control to restore the full tree. A click resolves to a thread by graph agent node identity rather than by label matching, so agents that share a provider nickname stay distinct. Markdown conversation sections now lead with the agent path instead of the provider nickname, so every section names the agent it belongs to. Both the standalone viewer and the live dashboard are covered; conversation materialization itself is unchanged.
+**v0.7.6 — an agent panel that answers what the agent said, and streamed responses rebuilt into one record.** Selecting an agent now opens with that agent's own turns, read as who said what, keeping the provider-neutral, agent-local multi-agent conversations each agent already owned. Consecutive turns a provider did not expose collapse into one line that still names the agents they were addressed to, and the multi-kilobyte preamble a provider prepends to every subagent is folded rather than leading the panel; the node evidence and trace stay one disclosure away. Graph labels resolve each agent's declared path, so siblings spawned in the same millisecond no longer render as the same fragment of a time-ordered id. Underneath, a streamed response is reassembled into the same canonical record its non-streamed twin would produce — text, reasoning and tool calls split across frames are rejoined before anything is materialized, and a stream that ended early is recorded as interrupted rather than completed.
 
 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.
 
@@ -327,7 +327,7 @@ Conversation isolation is an attribution/display rule, not a redaction boundary.
 
 ## Current status
 
-v0.7.4 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.6 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.4 → execweave-0.7.6}/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.4**.
+Die aktuelle Version ist **v0.7.6**.
 
 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.4 — Conversation-Fokus pro Agent im Dashboard.** Aufbauend auf den in v0.7.3 materialisierten provider-neutralen, agent-lokalen Multi-Agent-Conversations begrenzt die Auswahl eines agent node das Conversation-Panel jetzt auf genau diesen Agent, samt Anzahl der sichtbaren Einträge und einem Control zum Wiederherstellen des vollständigen Baums. Ein Klick wird über die identity des graph agent node und nicht über Label-Vergleich zu einem Thread aufgelöst, sodass Agents mit demselben Provider-Nickname unterscheidbar bleiben. Markdown-Conversation-Abschnitte beginnen nun mit dem agent path statt mit dem Provider-Nickname, sodass jeder Abschnitt den zugehörigen Agent benennt. Sowohl der Standalone-Viewer als auch das Live-Dashboard sind abgedeckt; die Conversation-Materialisierung selbst bleibt unverändert.
+**v0.7.6 — ein Agent-Panel, das beantwortet, was der Agent gesagt hat, und gestreamte Antworten, die zu einem Datensatz zusammengesetzt werden.** Die Auswahl eines Agents öffnet nun mit dessen eigenen Turns, gelesen als wer was gesagt hat, und behält die provider-neutralen, agent-lokalen Multi-Agent-Conversations bei, die jeder Agent bereits besaß. Aufeinanderfolgende Turns, die ein Provider nicht offengelegt hat, klappen zu einer Zeile zusammen, die weiterhin die adressierten Agents nennt, und die mehrere Kilobyte lange Präambel, die ein Provider jedem Subagent voranstellt, wird gefaltet statt an den Anfang gestellt; Node-Evidence und Trace bleiben eine Offenlegung entfernt. Graph-Labels lösen den deklarierten Path jedes Agents auf, sodass in derselben Millisekunde erzeugte Geschwister nicht mehr als dasselbe Fragment einer zeitgeordneten Id erscheinen. Darunter wird eine gestreamte Antwort zu demselben kanonischen Datensatz zusammengesetzt, den ihr nicht gestreamtes Gegenstück erzeugen würde: über Frames verteilte Texte, Reasoning und Tool Calls werden vor der Materialisierung wieder verbunden, und ein früh beendeter Stream wird als unterbrochen festgehalten.
 
 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.4 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.6 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.4 → execweave-0.7.6}/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.4**.
+La version courante est **v0.7.6**.
 
 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.4 — focus de conversation par agent dans le dashboard.** En s’appuyant sur les conversations multi-agent provider-neutral et agent-local matérialisées en v0.7.3, sélectionner un agent node restreint désormais le panneau de conversation à cet agent seul, avec le nombre d’éléments visibles et un contrôle pour restaurer l’arbre complet. Un clic est résolu en thread via l’identity du graph agent node et non par correspondance de label, de sorte que des agents partageant un même provider nickname restent distincts. Les sections de conversation Markdown commencent maintenant par l’agent path plutôt que par le provider nickname, si bien que chaque section nomme l’agent auquel elle appartient. Le viewer standalone et le live dashboard sont tous deux couverts ; la matérialisation des conversations est inchangée.
+**v0.7.6 — un panneau d’agent qui répond à ce que l’agent a dit, et des réponses en flux reconstruites en un seul enregistrement.** Sélectionner un agent ouvre désormais sur ses propres turns, lus comme qui a dit quoi, en conservant les conversations multi-agent provider-neutral et agent-local que chaque agent possédait déjà. Les turns consécutifs qu’un provider n’a pas exposés se replient en une ligne qui nomme toujours les agents destinataires, et le préambule de plusieurs kilo-octets qu’un provider ajoute devant chaque subagent est plié plutôt que placé en tête du panneau ; l’evidence du node et la trace restent à une divulgation de distance. Les libellés du graphe résolvent le path déclaré de chaque agent, si bien que des frères créés dans la même milliseconde ne s’affichent plus comme le même fragment d’un id ordonné par le temps. En dessous, une réponse en flux est réassemblée dans le même enregistrement canonique que produirait sa jumelle non diffusée : texte, reasoning et tool calls répartis sur plusieurs frames sont rejoints avant toute matérialisation, et un flux interrompu est consigné comme interrompu.
 
 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.4 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.6 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.4 → execweave-0.7.6}/README.ja.md

@@ -31,7 +31,7 @@ PyPI から最新の wheel/sdist をインストールします。
 python -m pip install -U execweave
 ```
 
-現在のリリースは **v0.7.4** です。
+現在のリリースは **v0.7.6** です。
 
 開発環境では次のようにインストールできます。
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` は Agent を起動 terminal 上でインタラクティブなまま保ち、ホスト環境に応じて detached Top dashboard を開くか既存のものに attach します。
 
-**v0.7.4 — dashboard での per-agent conversation focus。** v0.7.3 で materialize された provider-neutral かつ agent-local な multi-agent conversation を土台に、agent node を選択すると conversation panel がその agent だけに絞り込まれ、表示項目数と全体ツリーに戻すコントロールが付きます。クリックは label の一致ではなく graph agent node identity で thread に解決されるため、同じ provider nickname を共有する agent どうしも混ざりません。Markdown の conversation セクションは provider nickname ではなく agent path で始まるようになり、各セクションがどの agent のものかを明示します。standalone viewer と live dashboard の両方が対象で、conversation materialization 自体は変更していません。
+**v0.7.6 — その agent が何を言ったかに答える agent panel と、ひとつのレコードに再構成される streamed response。** agent を選択すると、その agent 自身の turn が「誰が何を言ったか」として最初に表示され、各 agent がすでに保持していた provider-neutral かつ agent-local な multi-agent conversation を引き継ぎます。provider が公開しなかった連続する turn は 1 行にまとめられますが、宛先の agent は列挙されたままです。provider がすべての subagent に前置きする数キロバイトの内容は 折りたたまれ、パネルの先頭を占めません。node evidence と trace も開示ひとつ分の距離にあります。Graph label は各 agent が 宣言した path を解決するため、同一ミリ秒で生成された兄弟が同じ time-ordered id の断片として描画されることはありません。内部では streamed response が非ストリーミング版と同じ canonical record に再構成され、frame をまたいで分割されたテキスト、reasoning、tool call は materialize の前に結合され、途中で終わったストリームは完了ではなく中断として記録されます。
 
 統合 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.4 は 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.6 は 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.4 → execweave-0.7.6}/README.ko.md

@@ -31,7 +31,7 @@ PyPI에서 최신 wheel/sdist를 설치합니다.
 python -m pip install -U execweave
 ```
 
-현재 릴리스는 **v0.7.4** 입니다.
+현재 릴리스는 **v0.7.6** 입니다.
 
 개발 설치:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex`는 Agent를 시작 terminal에서 interactive 상태로 유지하면서 host 환경에 따라 detached Top dashboard를 열거나 attach합니다.
 
-**v0.7.4 — dashboard의 per-agent conversation focus.** v0.7.3에서 materialize된 provider-neutral, agent-local multi-agent conversation을 토대로, 이제 agent node를 선택하면 conversation panel이 해당 agent만 보여주며 표시 항목 수와 전체 트리로 복원하는 컨트롤이 함께 제공됩니다. 클릭은 label 비교가 아니라 graph agent node identity로 thread에 매핑되므로 동일한 provider nickname을 공유하는 agent끼리도 섞이지 않습니다. Markdown conversation 섹션은 provider nickname 대신 agent path로 시작하여 각 섹션이 어떤 agent의 것인지 명시합니다. standalone viewer와 live dashboard 모두 적용되며 conversation materialization 자체는 변경되지 않았습니다.
+**v0.7.6 — 그 agent가 무엇을 말했는지에 답하는 agent panel, 그리고 하나의 레코드로 재조립되는 streamed response.** agent를 선택하면 그 agent 자신의 turn이 '누가 무엇을 말했는가'로 가장 먼저 표시되며, 각 agent가 이미 보유하던 provider-neutral, agent-local multi-agent conversation을 그대로 이어갑니다. provider가 노출하지 않은 연속된 turn은 한 줄로 접히지만 수신한 agent들은 그대로 나열됩니다. provider가 모든 subagent 앞에 붙이는 수 킬로바이트 서두는 접혀서 패널 머리를 차지하지 않고, node evidence와 trace도 한 번의 펼침 거리에 있습니다. Graph label은 각 agent가 선언한 path를 해석하므로 같은 밀리초에 생성된 형제가 동일한 time-ordered id 조각으로 그려지지 않습니다. 내부적으로 streamed response는 비스트리밍 버전과 동일한 canonical record로 재조립되어, frame을 가로질러 나뉜 텍스트·reasoning·tool call이 materialize 전에 이어 붙고, 일찍 끝난 스트림은 완료가 아니라 중단으로 기록됩니다.
 
 통합 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.4는 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.6는 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.4 → execweave-0.7.6}/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.4**.
+The current release is **v0.7.6**.
 
 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.4 — per-agent conversation focus in the dashboard.** Building on the provider-neutral, agent-local multi-agent conversations materialized in v0.7.3, selecting an agent node now scopes the conversation panel to that agent alone, with its visible item count and a control to restore the full tree. A click resolves to a thread by graph agent node identity rather than by label matching, so agents that share a provider nickname stay distinct. Markdown conversation sections now lead with the agent path instead of the provider nickname, so every section names the agent it belongs to. Both the standalone viewer and the live dashboard are covered; conversation materialization itself is unchanged.
+**v0.7.6 — an agent panel that answers what the agent said, and streamed responses rebuilt into one record.** Selecting an agent now opens with that agent's own turns, read as who said what, keeping the provider-neutral, agent-local multi-agent conversations each agent already owned. Consecutive turns a provider did not expose collapse into one line that still names the agents they were addressed to, and the multi-kilobyte preamble a provider prepends to every subagent is folded rather than leading the panel; the node evidence and trace stay one disclosure away. Graph labels resolve each agent's declared path, so siblings spawned in the same millisecond no longer render as the same fragment of a time-ordered id. Underneath, a streamed response is reassembled into the same canonical record its non-streamed twin would produce — text, reasoning and tool calls split across frames are rejoined before anything is materialized, and a stream that ended early is recorded as interrupted rather than completed.
 
 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.4 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.6 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.4 → execweave-0.7.6}/README.ru.md

@@ -31,7 +31,7 @@ ExecWeave — source-available, local-first проект наблюдаемос
 python -m pip install -U execweave
 ```
 
-Текущая версия — **v0.7.4**.
+Текущая версия — **v0.7.6**.
 
 Для разработки:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` оставляет Agent интерактивным в стартовом terminal и одновременно открывает либо подключает detached Top dashboard в зависимости от host environment.
 
-**v0.7.4 — фокус на conversation отдельного agent в dashboard.** Опираясь на provider-neutral, agent-local multi-agent conversations, материализованные в v0.7.3, выбор agent node теперь ограничивает conversation panel только этим agent, показывая число видимых элементов и control для возврата к полному дереву. Клик сопоставляется с thread по identity graph agent node, а не по совпадению label, поэтому agents с одинаковым provider nickname остаются различимыми. Секции conversation в Markdown теперь начинаются с agent path, а не с provider nickname, так что каждая секция называет свой agent. Покрыты и standalone viewer, и live dashboard; сама материализация conversation не изменена.
+**v0.7.6 — панель agent, отвечающая на вопрос, что этот agent сказал, и потоковые ответы, собранные в одну запись.** Выбор agent теперь открывается его собственными turns, читаемыми как кто что сказал, сохраняя provider-neutral, agent-local multi-agent conversations, которыми каждый agent уже владел. Подряд идущие turns, не раскрытые provider, сворачиваются в одну строку, которая по-прежнему называет agents-получателей, а многокилобайтная преамбула, добавляемая provider перед каждым subagent, сворачивается, а не открывает панель; evidence узла и trace остаются в одном раскрытии. Метки графа разрешают объявленный path каждого agent, поэтому братья, созданные в ту же миллисекунду, больше не отображаются как один и тот же фрагмент упорядоченного по времени id. Ниже потоковый ответ пересобирается в ту же каноническую запись, что и его непотоковый двойник: текст, reasoning и tool calls, разделённые между frames, соединяются до материализации, а рано оборвавшийся поток фиксируется как прерванный.
 
 Единый 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.4 объединяет 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.6 объединяет 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.4 → execweave-0.7.6}/README.zh-CN.md

@@ -31,7 +31,7 @@ ExecWeave 是一个 source-available、local-first 的可观测性项目，把 A
 python -m pip install -U execweave
 ```
 
-当前正式版本是 **v0.7.4**。
+当前正式版本是 **v0.7.6**。
 
 开发安装：
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` 会让 Agent 保持在启动 terminal 中交互，并根据主机环境打开或附加 detached Top dashboard。
 
-**v0.7.4 — dashboard 的 per-agent conversation focus。** 延续 v0.7.3 已经 materialize 的 provider-neutral、agent-local multi-agent conversation，现在点选某个 agent node，conversation panel 只会显示该 agent 自己的 thread，并附带可见项目数与还原完整树状视图的控件。点击是以 graph agent node identity 对应到 thread，而不是比对 label，因此即使多个 agent 共用同一个 provider nickname 也不会被混在一起。Markdown 的 conversation 章节现在以 agent path 开头，而不是 provider nickname，每个章节都能明确指出自己属于哪一个 agent。standalone viewer 与 live dashboard 都覆盖；conversation materialization 本身没有变动。
+**v0.7.6 — 回答「这个 agent 说了什么」的 agent panel，以及被重新组装成单一记录的 streamed response。** 选取一个 agent，现在最先看到的是该 agent 自己的 turn，以「谁说了什么」呈现，并延续每个 agent 原本就各自拥有的 provider-neutral、agent-local multi-agent conversation。provider 未暴露的连续 turn 会收合成一行，但仍列出它们寄给哪些 agent；provider 加在每个 subagent 前面的数 KB 前置内容改为折叠，不再占据面板开头，node evidence 与 trace 也只隔一次展开。Graph label 会解析每个 agent 声明的 path，因此同一毫秒生成的兄弟不再显示成同一段 time-ordered id 片段。底层则把 streamed response 重组成与非流式版本相同的 canonical record —— 跨 frame 切开的文字、reasoning 与 tool call 会先接回再 materialize，提前结束的流记为中断而非完成。
 
 统一 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.4 组合 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.6 组合 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.4 → execweave-0.7.6}/README.zh-TW.md

@@ -31,7 +31,7 @@ ExecWeave 是一個 source-available、local-first 的可觀測性專案，會
 python -m pip install -U execweave
 ```
 
-目前正式版本是 **v0.7.4**。
+目前正式版本是 **v0.7.6**。
 
 開發安裝：
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` 會讓 Agent 保持在啟動 terminal 中互動，並依主機環境開啟或附加 detached Top dashboard。
 
-**v0.7.4 — dashboard 的 per-agent conversation focus。** 延續 v0.7.3 已經 materialize 的 provider-neutral、agent-local multi-agent conversation，現在點選某個 agent node，conversation panel 會只顯示該 agent 自己的 thread，並附上可見項目數與還原完整樹狀檢視的控制項。點擊是以 graph agent node identity 對應到 thread，而不是比對 label，所以即使多個 agent 共用同一個 provider nickname 也不會被混在一起。Markdown 的 conversation 章節現在以 agent path 開頭，而不是 provider nickname，每個章節都能明確指出自己屬於哪一個 agent。standalone viewer 與 live dashboard 都涵蓋；conversation materialization 本身沒有變動。
+**v0.7.6 — 回答「這個 agent 說了什麼」的 agent panel，以及被重新組裝成單一記錄的 streamed response。** 選取一個 agent，現在最先看到的是該 agent 自己的 turn，以「誰說了什麼」呈現，並延續每個 agent 原本就各自擁有的 provider-neutral、agent-local multi-agent conversation。provider 未曝露的連續 turn 會收合成一行，但仍列出它們寄給哪些 agent；provider 加在每個 subagent 前面的數 KB 前置內容改為折疊，不再佔據面板開頭，node evidence 與 trace 也只隔一次展開。Graph label 會解析每個 agent 宣告的 path，因此同一毫秒生成的兄弟不再顯示成同一段 time-ordered id 片段。底層則把 streamed response 重組成與非串流版本相同的 canonical record —— 跨 frame 切開的文字、reasoning 與 tool call 會先接回再 materialize，提早結束的串流記為中斷而非完成。
 
 統一 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.4 整合 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.6 整合 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 仍從設計上分離。
 
 ## 文件