execweave 0.7.2__tar.gz → 0.7.4__tar.gz

{execweave-0.7.2 → execweave-0.7.4}/.github/workflows/ci.yml

@@ -150,6 +150,12 @@ jobs:
         run: python scripts/check_correlation_graph.py claude-record-smoke/graph.correlated.json
       - name: Check correlated standalone viewer JavaScript syntax
         run: python scripts/check_viewer_js.py claude-record-smoke/viewer.correlated.html --output claude-record-smoke/viewer.correlated.js
+      - name: Verify Claude materialized conversations
+        run: >
+          python scripts/check_conversation_records.py claude-record-smoke
+          --expect-agent /root
+          --expect-root-text "CI CLAUDE PROMPT"
+          --expect-root-text "CI CLAUDE FINAL ANSWER"
       - name: Gemini run-bound semantic and correlation smoke
         run: execweave-gemini-record --backend auto --no-files --no-network --output-dir gemini-record-smoke -- python scripts/emit_gemini_hook_smoke.py
       - name: Validate Gemini runtime stream
@@ -162,6 +168,12 @@ jobs:
         run: python scripts/check_correlation_graph.py gemini-record-smoke/graph.correlated.json
       - name: Check Gemini correlated viewer JavaScript syntax
         run: python scripts/check_viewer_js.py gemini-record-smoke/viewer.correlated.html --output gemini-record-smoke/viewer.correlated.js
+      - name: Verify Gemini materialized conversations
+        run: >
+          python scripts/check_conversation_records.py gemini-record-smoke
+          --expect-agent /root
+          --expect-root-text "CI GEMINI PROMPT"
+          --expect-root-text "CI GEMINI FINAL ANSWER"
       - name: Cursor run-bound semantic and correlation smoke
         run: execweave-cursor-record --backend auto --no-files --no-network --output-dir cursor-record-smoke -- python scripts/emit_cursor_hook_smoke.py
       - name: Validate Cursor runtime stream
@@ -174,6 +186,12 @@ jobs:
         run: python scripts/check_correlation_graph.py cursor-record-smoke/graph.correlated.json
       - name: Check Cursor correlated viewer JavaScript syntax
         run: python scripts/check_viewer_js.py cursor-record-smoke/viewer.correlated.html --output cursor-record-smoke/viewer.correlated.js
+      - name: Verify Cursor materialized conversations
+        run: >
+          python scripts/check_conversation_records.py cursor-record-smoke
+          --expect-agent /root
+          --expect-root-text "CI CURSOR PROMPT"
+          --expect-root-text "CI CURSOR FINAL ANSWER"
       - name: OpenCode plugin installer smoke
         run: execweave-opencode-plugin --install --root opencode-plugin-smoke
       - name: OpenCode run-bound semantic and correlation smoke
@@ -188,6 +206,40 @@ jobs:
         run: python scripts/check_correlation_graph.py opencode-record-smoke/graph.correlated.json
       - name: Check OpenCode correlated viewer JavaScript syntax
         run: python scripts/check_viewer_js.py opencode-record-smoke/viewer.correlated.html --output opencode-record-smoke/viewer.correlated.js
+      - name: Verify OpenCode materialized conversations
+        run: >
+          python scripts/check_conversation_records.py opencode-record-smoke
+          --expect-agent /root
+          --expect-root-text "CI OPENCODE FINAL ANSWER"
+          --forbid-agent /root/ci-opencode-session
+      - name: Codex hook command smoke
+        run: python scripts/check_codex_hook.py
+      - name: Codex run-bound semantic and correlation smoke
+        run: execweave-codex-record --backend auto --no-files --no-network --output-dir codex-record-smoke -- python scripts/emit_codex_hook_smoke.py
+      - name: Validate Codex runtime stream
+        run: execweave validate codex-record-smoke/events.jsonl
+      - name: Validate Codex merged stream
+        run: execweave validate codex-record-smoke/events.semantic.jsonl
+      - name: Validate Codex correlated stream
+        run: execweave validate codex-record-smoke/events.correlated.jsonl
+      - name: Verify Codex conservative correlation edge
+        run: python scripts/check_correlation_graph.py codex-record-smoke/graph.correlated.json
+      - name: Check Codex correlated viewer JavaScript syntax
+        run: python scripts/check_viewer_js.py codex-record-smoke/viewer.correlated.html --output codex-record-smoke/viewer.correlated.js
+      # Codex reports a subagent stop with the child rollout on agent_transcript_path
+      # and the parent rollout on transcript_path. Archiving the parent is the
+      # v0.7.2 regression, so assert the child conversation survives end to end.
+      - name: Verify Codex agent-local subagent conversations
+        run: >
+          python scripts/check_conversation_records.py codex-record-smoke
+          --min-entries 2
+          --expect-agent /root
+          --expect-agent /root/explorer
+          --expect-root-text "CI ROOT PROMPT"
+          --expect-root-text "CI ROOT FINAL ANSWER"
+          --expect-owned "/root=CI ROOT COMMENTARY"
+          --expect-owned "/root/explorer=CI CHILD PRIVATE REASONING"
+          --forbid-agent /root/01a04cea-67b2-7683-9f6b-cd644497b862
       - name: Model runtime CLI smoke
         run: python scripts/check_model_runtime_cli.py
       - name: Inference gateway CLI smoke

{execweave-0.7.2 → execweave-0.7.4}/.github/workflows/publish.yml

@@ -3,21 +3,30 @@ name: Publish to PyPI
 on:
   release:
     types: [published]
+  workflow_dispatch:
+    inputs:
+      release_tag:
+        description: Release tag to publish
+        required: true
+        type: string
 
 permissions:
   contents: read
 
+env:
+  RELEASE_TAG: ${{ github.event.release.tag_name || inputs.release_tag }}
+
 jobs:
   build:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+        with:
+          ref: ${{ env.RELEASE_TAG }}
       - uses: actions/setup-python@v5
         with:
           python-version: "3.12"
       - name: Verify release tag matches package version
-        env:
-          RELEASE_TAG: ${{ github.event.release.tag_name }}
         run: |
           python - <<'PY'
           import os
@@ -75,5 +84,4 @@ jobs:
       - name: Attach distributions to GitHub Release
         env:
           GH_TOKEN: ${{ github.token }}
-          RELEASE_TAG: ${{ github.event.release.tag_name }}
         run: gh release upload "$RELEASE_TAG" dist/* --clobber --repo "$GITHUB_REPOSITORY"

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: execweave
-Version: 0.7.2
+Version: 0.7.4
 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.2**.
+The current release is **v0.7.4**.
 
 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.2 — provider-neutral, agent-local multi-agent conversations.** ExecWeave now projects provider-exposed conversation evidence into agent-scoped dashboard threads instead of duplicating one full transcript across every agent node. Parent → child task assignments, routed inter-agent messages, waits/results, and child → parent final responses are preserved when the provider exposes authoritative identity or routing evidence. A child agent keeps only its own visible task and conversation; inherited parent history and sibling-private content are excluded. The common merge layer also scopes by provider, raw thread identity, and agent identity, so even a reused provider thread ID cannot fold Agent 1 into Agent 2.
+**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.
 
 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.2 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, and agent-local conversation isolation across provider-neutral projections. 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.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.
 
 ## Documentation
 

{execweave-0.7.2 → execweave-0.7.4}/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.2**.
+Die aktuelle Version ist **v0.7.4**.
 
 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.2 — provider-neutral, agent-local multi-agent conversations.** ExecWeave projiziert die vom Provider tatsächlich offengelegte conversation evidence jetzt in agent-spezifische Dashboard-Threads, statt denselben vollständigen Transcript in jeden agent node zu kopieren. Wenn der Provider authoritative identity / routing evidence bereitstellt, werden parent → child task assignments, inter-agent messages, waits/results und child → parent final responses erhalten. Ein Child Agent enthält nur die Task, die er tatsächlich erhalten hat, sowie seine eigene Conversation; inherited parent history und sibling-private content werden ausgeschlossen. Die gemeinsame Merge-Schicht scoped zusätzlich nach Provider, raw thread identity und agent identity, sodass selbst ein wiederverwendeter Provider-thread-ID Agent 1 und Agent 2 nicht zusammenführen kann.
+**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.
 
 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.2 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 und agent-local conversation isolation in provider-neutralen Projektionen. 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.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.
 
 ## Dokumentation
 

{execweave-0.7.2 → execweave-0.7.4}/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.2**.
+La version courante est **v0.7.4**.
 
 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.2 — conversations multi-agent provider-neutral et agent-local.** ExecWeave projette désormais les conversation evidence réellement exposées par le provider dans des threads de dashboard propres à chaque agent, au lieu de dupliquer un transcript complet dans tous les agent nodes. Lorsque le provider expose une identity ou un routing faisant autorité, ExecWeave conserve les task assignments parent → child, les inter-agent messages, les waits/results et les final responses child → parent. Un child agent ne garde que la tâche qu’il a réellement reçue et sa propre conversation ; l’inherited parent history et le contenu privé des siblings sont exclus. La couche de merge commune scope également par provider, raw thread identity et agent identity, de sorte qu’un thread ID réutilisé ne puisse pas fusionner Agent 1 avec Agent 2.
+**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.
 
 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.2 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 et agent-local conversation isolation dans les projections provider-neutral. 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.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.
 
 ## Documentation
 

{execweave-0.7.2 → execweave-0.7.4}/README.ja.md

@@ -31,7 +31,7 @@ PyPI から最新の wheel/sdist をインストールします。
 python -m pip install -U execweave
 ```
 
-現在のリリースは **v0.7.2** です。
+現在のリリースは **v0.7.4** です。
 
 開発環境では次のようにインストールできます。
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` は Agent を起動 terminal 上でインタラクティブなまま保ち、ホスト環境に応じて detached Top dashboard を開くか既存のものに attach します。
 
-**v0.7.2 — provider-neutral かつ agent-local な multi-agent conversation。** ExecWeave は provider が実際に公開した conversation evidence を agent ごとの dashboard thread に投影し、同じ完全 transcript をすべての agent node に複製しません。provider が権威ある identity / routing evidence を公開している場合、parent → child の task assignment、inter-agent message、wait/result、child → parent final response を保持します。Child agent には、その agent が実際に受け取った task と自身の conversation だけを残し、継承された parent history や sibling-private content は除外します。共通 merge layer も provider、raw thread identity、agent identity を組み合わせて scope するため、provider が同じ thread ID を再利用しても Agent 1 と Agent 2 が混ざりません。
+**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 自体は変更していません。
 
 統合 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.2 は 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 を統合します。各 integration は provider が実際に公開した最も強い identity/routing evidence のみを保持し、不足する場合は abstain します。Observed evidence と inference は設計上分離されたままです。
+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 は設計上分離されたままです。
 
 ## ドキュメント
 

{execweave-0.7.2 → execweave-0.7.4}/README.ko.md

@@ -31,7 +31,7 @@ PyPI에서 최신 wheel/sdist를 설치합니다.
 python -m pip install -U execweave
 ```
 
-현재 릴리스는 **v0.7.2** 입니다.
+현재 릴리스는 **v0.7.4** 입니다.
 
 개발 설치:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex`는 Agent를 시작 terminal에서 interactive 상태로 유지하면서 host 환경에 따라 detached Top dashboard를 열거나 attach합니다.
 
-**v0.7.2 — provider-neutral, agent-local multi-agent conversation.** ExecWeave는 provider가 실제로 노출한 conversation evidence를 각 agent의 dashboard thread에 투영하며, 동일한 전체 transcript를 모든 agent node에 복제하지 않습니다. provider가 authoritative identity / routing evidence를 제공하면 parent → child task assignment, inter-agent message, wait/result, child → parent final response를 보존합니다. Child agent에는 자신이 실제로 받은 task와 자신이 생성한 conversation만 남고 inherited parent history 및 sibling-private content는 제외됩니다. 공통 merge layer 역시 provider, raw thread identity, agent identity로 scope하므로 provider가 동일한 thread ID를 재사용해도 Agent 1과 Agent 2가 섞이지 않습니다.
+**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 자체는 변경되지 않았습니다.
 
 통합 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.2는 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을 통합합니다. 각 integration은 provider가 실제로 노출한 가장 강한 identity/routing evidence만 보존하고 충분한 증거가 없으면 abstain합니다. Observed evidence와 inference는 설계상 계속 분리됩니다.
+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는 설계상 계속 분리됩니다.
 
 ## 문서
 

{execweave-0.7.2 → execweave-0.7.4}/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.2**.
+The current release is **v0.7.4**.
 
 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.2 — provider-neutral, agent-local multi-agent conversations.** ExecWeave now projects provider-exposed conversation evidence into agent-scoped dashboard threads instead of duplicating one full transcript across every agent node. Parent → child task assignments, routed inter-agent messages, waits/results, and child → parent final responses are preserved when the provider exposes authoritative identity or routing evidence. A child agent keeps only its own visible task and conversation; inherited parent history and sibling-private content are excluded. The common merge layer also scopes by provider, raw thread identity, and agent identity, so even a reused provider thread ID cannot fold Agent 1 into Agent 2.
+**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.
 
 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.2 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, and agent-local conversation isolation across provider-neutral projections. 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.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.
 
 ## Documentation
 

{execweave-0.7.2 → execweave-0.7.4}/README.ru.md

@@ -31,7 +31,7 @@ ExecWeave — source-available, local-first проект наблюдаемос
 python -m pip install -U execweave
 ```
 
-Текущая версия — **v0.7.2**.
+Текущая версия — **v0.7.4**.
 
 Для разработки:
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` оставляет Agent интерактивным в стартовом terminal и одновременно открывает либо подключает detached Top dashboard в зависимости от host environment.
 
-**v0.7.2 — provider-neutral, agent-local multi-agent conversations.** ExecWeave теперь проецирует conversation evidence, реально раскрытую provider, в отдельные dashboard threads для каждого agent, вместо копирования одного полного transcript во все agent nodes. Если provider предоставляет authoritative identity / routing evidence, сохраняются parent → child task assignments, inter-agent messages, waits/results и child → parent final responses. Child agent содержит только фактически полученную им task и собственную conversation; inherited parent history и sibling-private content исключаются. Общий merge layer также scope-ит данные по provider, raw thread identity и agent identity, поэтому даже повторно использованный thread ID не сможет объединить Agent 1 и Agent 2.
+**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 не изменена.
 
 Единый 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.2 объединяет 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. Каждая integration сохраняет только наиболее сильную identity/routing evidence, реально раскрытую provider, и abstain-ит при её отсутствии. Observed evidence и inference по-прежнему разделены архитектурно.
+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 по-прежнему разделены архитектурно.
 
 ## Документация
 

{execweave-0.7.2 → execweave-0.7.4}/README.zh-CN.md

@@ -31,7 +31,7 @@ ExecWeave 是一个 source-available、local-first 的可观测性项目，把 A
 python -m pip install -U execweave
 ```
 
-当前正式版本是 **v0.7.2**。
+当前正式版本是 **v0.7.4**。
 
 开发安装：
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` 会让 Agent 保持在启动 terminal 中交互，并根据主机环境打开或附加 detached Top dashboard。
 
-**v0.7.2 — provider-neutral、agent-local 的 multi-agent conversation。** ExecWeave 现在会把 provider 真正暴露的 conversation evidence 投影到各自 agent 的 dashboard thread，而不是把同一份完整 transcript 复制到每个 agent node。当 provider 提供权威的 identity / routing evidence 时，会保留 parent → child task assignment、inter-agent message、wait/result，以及 child → parent final response。Child agent 只保留自己实际收到的 task 与自己生成的 conversation；继承的 parent history 与 sibling-private content 会被排除。公共 merge layer 还会同时按 provider、raw thread identity 与 agent identity 做 scope，因此即使 provider 重复使用同一个 thread ID，也不会把 Agent 1 和 Agent 2 混到一起。
+**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 本身没有变动。
 
 统一 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.2 组合 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。各 integration 只保留 provider 实际暴露的最强 identity/routing evidence，证据不足时选择 abstain。Observed evidence 与 inference 从设计上保持分离。
+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 从设计上保持分离。
 
 ## 文档
 

{execweave-0.7.2 → execweave-0.7.4}/README.zh-TW.md

@@ -31,7 +31,7 @@ ExecWeave 是一個 source-available、local-first 的可觀測性專案，會
 python -m pip install -U execweave
 ```
 
-目前正式版本是 **v0.7.2**。
+目前正式版本是 **v0.7.4**。
 
 開發安裝：
 
@@ -67,7 +67,7 @@ execweave record --open -- python my_agent.py
 
 `execweave top -- codex` 會讓 Agent 保持在啟動 terminal 中互動，並依主機環境開啟或附加 detached Top dashboard。
 
-**v0.7.2 — provider-neutral、agent-local 的 multi-agent conversation。** ExecWeave 現在會把 provider 真正曝露的 conversation evidence 投影到各自 agent 的 dashboard thread，不再把同一份完整 transcript 複製到每一個 agent node。當 provider 有權威的 identity / routing evidence 時，會保留 parent → child task assignment、inter-agent message、wait/result，以及 child → parent final response。Child agent 只保留自己實際收到的 task 與自己產生的 conversation；繼承的 parent history 與 sibling-private content 會被排除。共用 merge layer 也會用 provider、raw thread identity 與 agent identity 一起 scope，所以就算 provider 重複使用同一個 thread ID，也不會把 Agent 1 與 Agent 2 混在一起。
+**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 本身沒有變動。
 
 統一 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.2 整合 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。各 integration 只保留 provider 實際曝露的最強 identity/routing evidence，證據不足時選擇 abstain。Observed evidence 與 inference 仍從設計上分離。
+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 仍從設計上分離。
 
 ## 文件
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.de.md

@@ -30,7 +30,6 @@ ExecWeave zeichnet Evidenz aus Codex-Lifecycle-Hooks neben unabhängig erfasster
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 Unbekannte oder upstream nicht verfügbare Ereignisse werden nicht erfunden. Hook-Schemata und Dispatch-Abdeckung können sich zwischen Codex-Versionen ändern.
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.fr.md

@@ -30,7 +30,6 @@ ExecWeave enregistre les preuves issues des hooks de cycle de vie Codex à côt
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 ExecWeave n'invente pas les événements absents ou indisponibles côté fournisseur. Les schémas et la couverture peuvent changer selon les versions de Codex.
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.ja.md

@@ -30,7 +30,6 @@ ExecWeave は Codex lifecycle-hook evidence を独立した OS runtime telemetry
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 未知または利用できない upstream event は作りません。Hook schema と dispatch coverage は Codex version により変わる可能性があります。
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.ko.md

@@ -30,7 +30,6 @@ ExecWeave는 Codex 라이프사이클 훅 증거를 독립적인 OS 런타임
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 업스트림에 없거나 사용할 수 없는 이벤트를 ExecWeave가 만들어내지는 않습니다. Codex 버전에 따라 훅 스키마와 디스패치 범위가 달라질 수 있습니다.
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.md

@@ -30,7 +30,6 @@ ExecWeave records Codex lifecycle-hook evidence beside independent OS runtime te
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 Unknown or unavailable upstream events are not invented. Hook schemas and dispatch coverage can change between Codex versions.
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.ru.md

@@ -30,7 +30,6 @@ ExecWeave записывает evidence из lifecycle hooks Codex рядом с
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 Неизвестные или недоступные upstream events не выдумываются. Hook schemas и dispatch coverage могут меняться между версиями Codex.
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.zh-CN.md

@@ -30,7 +30,6 @@ ExecWeave 将 Codex lifecycle-hook evidence 与独立 OS runtime telemetry 并
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 ExecWeave 不会伪造 upstream 未知或不可用的 event。Hook schema 与 dispatch coverage 可能随 Codex 版本改变。
 

{execweave-0.7.2 → execweave-0.7.4}/docs/codex-hooks.zh-TW.md

@@ -30,7 +30,6 @@ ExecWeave 會把 Codex lifecycle-hook evidence 與獨立 OS runtime telemetry
 - `SubagentStart`
 - `SubagentStop`
 - `Stop`
-- `Interrupt`
 
 ExecWeave 不會捏造 upstream 未知或不可用的 event。Hook schema 與 dispatch coverage 可能隨 Codex 版本改變。
 

{execweave-0.7.2 → execweave-0.7.4}/pyproject.toml

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

{execweave-0.7.2 → execweave-0.7.4}/scripts/audit_i18n_parity.py

@@ -32,9 +32,18 @@ DOCS = [
     (Path("docs/run-integrity.md"), "docs/run-integrity"),
 ]
 
+
+def current_release_tag() -> str:
+    pyproject = Path("pyproject.toml").read_text(encoding="utf-8")
+    match = re.search(r'(?m)^version\s*=\s*"([^\"]+)"\s*$', pyproject)
+    if match is None:
+        raise RuntimeError("project version not found in pyproject.toml")
+    return f"v{match.group(1)}"
+
+
 README_REQUIRED_SNIPPETS = [
     "v0.6.9",
-    "v0.7.2",
+    current_release_tag(),
     "execweave live --open -- cursor",
     "execweave live --open -- opencode",
     "execweave live --open -- ollama serve",
@@ -120,8 +129,9 @@ def audit_coverage() -> int:
                 print(f"FAIL missing {lang:5}: {path}")
                 failures += 1
 
-    for lang in ALL_LANGS:
-        path = Path(f"README.{lang}.md")
+    readmes = [("en", Path("README.md"))]
+    readmes.extend((lang, Path(f"README.{lang}.md")) for lang in ALL_LANGS)
+    for lang, path in readmes:
         if not path.exists():
             continue
         text = path.read_text(encoding="utf-8")

{execweave-0.7.2 → execweave-0.7.4}/scripts/check_codex_hook.py

@@ -65,22 +65,16 @@ def main() -> int:
         check=True,
     )
     parsed = json.loads(config.stdout)
-    required = {
-        "PreToolUse",
-        "PermissionRequest",
-        "PostToolUse",
-        "PreCompact",
-        "PostCompact",
-        "SessionStart",
-        "SessionEnd",
-        "UserPromptSubmit",
-        "SubagentStart",
-        "SubagentStop",
-        "Stop",
-        "Interrupt",
-    }
+    # Bound to the shipped event set rather than a second hardcoded copy, which had
+    # drifted to expect an "Interrupt" hook ExecWeave does not register.
+    from execweave.codex_hook_lifecycle import OFFICIAL_CODEX_HOOK_EVENTS
+
+    required = set(OFFICIAL_CODEX_HOOK_EVENTS)
     if set(parsed.get("hooks", {})) != required:
-        raise SystemExit("generated Codex hook config is incomplete")
+        raise SystemExit(
+            "generated Codex hook config does not match the official event set: "
+            f"{sorted(set(parsed.get('hooks', {})) ^ required)}"
+        )
     for event_name in {"PreToolUse", "PermissionRequest", "PostToolUse"}:
         if parsed["hooks"][event_name][0].get("matcher") != "*":
             raise SystemExit(f"Codex {event_name} hook is not configured for all tools")