execweave 0.7.7__tar.gz → 0.7.9__tar.gz

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

@@ -0,0 +1,69 @@
+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]"
+
+      - 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/multi_agent_run_fixture.py=v0.7.9 checks four inspector contracts in the browser that were only asserted against source text, so the shared run fixture gains the shapes they need: a second archive owned by the same agent carrying nothing usable, one provider-encrypted delegation, and one answer that quotes routing words as prose. This module is the fixture builder and declares no test node IDs; no existing shape or assertion is removed"
+          --allow-test-change "tests/test_agent_message_viewer.py=v0.7.9 removes the standalone Message Evidence inspector; the same test IDs now assert that exact message-stage relations and payload references survive in the unified static snapshot without the removed panel"
+          --allow-test-change "tests/test_agent_node_labels.py=v0.7.9 removes the standalone conversation fallback; the same test ID now verifies that namespaced agent paths and authenticated conversation refresh are owned by the unified selected-agent inspector without creating a second conversation DOM"
+          --allow-test-change "tests/test_agent_said_panel.py=v0.7.9 replaces the who-said-what transcript renderer with compact Prompt/Final-response and Task/Thinking/Response cards; the same test IDs now pin plaintext, encrypted, and ownership boundaries in that replacement inspector"
+          --allow-test-change "tests/test_agent_topology_evidence.py=v0.7.9 removes the standalone conversation-tree root selector; the same test IDs now verify canonical root/child topology, multi-entry aggregation, and no first-record fallback through the unified selected-agent inspector"
+          --allow-test-change "tests/test_agent_trace_viewer_visibility.py=v0.7.9 removes the standalone provider-visibility prose panel; the same test IDs now verify capability nodes and provider visibility values remain embedded in the unified graph snapshot"
+          --allow-test-change "tests/test_antigravity_linkage_projection.py=v0.7.9 removes the Antigravity-specific standalone inspector; the same test ID now verifies exact identity/linkage evidence remains in the unified snapshot without transcript-path leakage"
+          --allow-test-change "tests/test_claude_hook_viewer.py=v0.7.9 removes the standalone Agent communications panel; the same lifecycle test now verifies Claude task relations remain in the unified graph snapshot"
+          --allow-test-change "tests/test_claude_record.py=v0.7.9 removes the standalone correlation-section DOM; the same record test now verifies correlation metadata is embedded in the unified static graph"
+          --allow-test-change "tests/test_codex_archive_full_fidelity.py=v0.7.9 no longer renders provider-encrypted payload prose; the same full-fidelity test now verifies the encrypted content_state remains embedded while plaintext Task/Response projection stays intact"
+          --allow-test-change "tests/test_codex_record.py=v0.7.9 removes the standalone correlation-section DOM; the same record test now verifies correlation metadata is embedded in the unified static graph"
+          --allow-test-change "tests/test_conversation_access.py=v0.7.9 removes the visible standalone Conversation records panel from viewer.html; the same test now verifies run-local records are embedded in static conversations and the sidecar index files still exist"
+          --allow-test-change "tests/test_conversation_agent_focus.py=v0.7.9 removes the conversation-tree focus implementation; all original test IDs now pin selected-agent routing in the shared compact inspector while keeping Markdown agent identity checks"
+          --allow-test-change "tests/test_conversation_provider_parity.py=v0.7.9 removes legacy visible provider-neutral and raw-evidence copy from the Dashboard; the same test ID now verifies provider-neutral semantics through the conversation-index schema and unified inspector without hidden comment sentinels"
+          --allow-test-change "tests/test_dashboard_information_architecture.py=v0.7.9 removes the standalone rooted conversation tree from Live; the same test ID now verifies the compact selected-agent inspector, encrypted-observed wording, and absence of the legacy conversation DOM"
+          --allow-test-change "tests/test_dashboard_simplification.py=v0.7.9 removes standalone conversation-tree DOM from the static viewer while retaining the shared live dashboard projection; the same test ID now asserts the unified static bootstrap and preserved evidence"
+          --allow-test-change "tests/test_dashboard_ux_and_hook_projection.py=v0.7.9 makes the visible Dashboard theme-toggle the sole theme owner; the same test ID now verifies the canonical control instead of the retired final-only execweave-theme-toggle injector"
+          --allow-test-change "tests/test_delegation_viewer.py=v0.7.9 removes the standalone Delegation Evidence inspector; the same test IDs now verify exact delegation relations, payload paths, and absence of invented linkage in the unified snapshot"
+          --allow-test-change "tests/test_execution_viewer.py=v0.7.9 removes the standalone Execution Evidence inspector; the same test ID now verifies exact execution/error relations and payload paths remain in the unified snapshot"
+          --allow-test-change "tests/test_live_auth.py=v0.7.9 removes the authenticated finished-page /final fetch; the same test ID now verifies the live token stays in memory and is sent as a header for authenticated evidence requests, and asserts completion never fetches, navigates to, or document.write()s a separate document"
+          --allow-test-change "tests/test_live_delta.py=v0.7.9 makes the unified Dashboard own its theme and terminal live state; the same test ID now verifies FINISHED state with the canonical theme-toggle and without the legacy execweave-theme-toggle injector"
+          --allow-test-change "tests/test_live_logs_export.py=v0.7.9 removes the finished-page /final document replacement; the same test ID now verifies authenticated Live remains in-place while replay and GIF export stay supported"
+          --allow-test-change "tests/test_per_agent_conversation_default.py=v0.7.9 removes the default multi-agent conversation tree; all original test IDs now pin namespaced path resolution and sibling isolation in the selected-agent compact inspector"
+          --allow-test-change "tests/test_v069_dashboard_release.py=v0.7.9 retires the separate final-window renderer; the same historical test ID now verifies finished Live remains in the current Dashboard DOM and uses the canonical theme-toggle"
+          --allow-test-change "tests/test_viewer_agent_isolation_e2e.py=v0.7.9 replaces the two rendered viewer surfaces with one live dashboard shell; the same four browser test node IDs now assert the stricter visible product contract and live/viewer parity instead of the removed conversation-tree UI"
+          --allow-test-change "tests/test_viewer_content_inspector.py=v0.7.9 removes the standalone content/activity inspectors; the same test IDs now verify safe content references and communication evidence remain embedded without reviving the removed UI"
+          --allow-test-change "tests/test_viewer_projection.py=v0.7.9 embeds projected clusters through the unified static graph instead of the legacy graph-data renderer; the same test ID now verifies expansion metadata survives without the removed Expand cluster copy"

execweave-0.7.9/.github/workflows/viewer-agent-isolation.yml

@@ -0,0 +1,45 @@
+name: Viewer Agent Isolation
+
+# The release gate opens the actual dashboard in Chromium. It reads the visible
+# root/subagent/non-agent inspectors, compares live with viewer.html, and archives
+# screenshots plus the rendered live.html for a human visual pass.
+on:
+  pull_request:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  viewers:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Install
+        run: python -m pip install -e ".[dev,e2e]"
+
+      - name: Install Chromium
+        run: python -m playwright install --with-deps chromium
+
+      - name: Read live and viewer.html in a browser
+        env:
+          EXECWEAVE_E2E_REQUIRED: "1"
+          EXECWEAVE_VISUAL_ARTIFACT_DIR: visual-artifacts
+        run: python -m pytest -m viewer_e2e -v
+
+      - name: Upload visual release evidence
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: unified-dashboard-visuals
+          path: visual-artifacts
+          if-no-files-found: error
+          retention-days: 7

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: execweave
-Version: 0.7.7
+Version: 0.7.9
 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.9**.
 
 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.9 — one dashboard, while the run happens and afterwards.** Live, the finished run and viewer.html were three renderings of the same evidence, and completion fetched a separate document and wrote it over the page a reader was watching. There is now one shell: finishing a run changes its state in place, and viewer.html is that same dashboard saved offline. Selecting an agent answers one question and stops — a root shows its Prompt and its Final response, a subagent shows its Task, its Thinking where the provider exposed plaintext, and its Response — while a process, a file, a network endpoint or a model shows no conversation at all, because a conversation belongs to an agent. A turn the provider encrypted reads as observed without plaintext rather than as never recorded, the block a provider prepends to every subagent is never presented as one agent's assignment, and an answer that quotes routing words survives intact. The provider-neutral, agent-local multi-agent conversations each agent owns are aggregated across every archive a run wrote, so an agent recorded many times still shows what it said. Release checks drive the shipped dashboard in a real browser through every selection a person can make, in both its live and its finished form.
 
 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.9 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.9}/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.9**.
 
 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.9 — ein Dashboard, während des Runs und danach.** Live, der beendete Run und viewer.html waren drei Darstellungen derselben Evidenz, und der Abschluss holte ein eigenes Dokument und schrieb es über die Seite, die ein Leser gerade betrachtete. Es gibt jetzt nur eine Hülle: Das Beenden eines Runs ändert dessen Zustand an Ort und Stelle, und viewer.html ist genau dieses Dashboard offline gespeichert. Die Auswahl eines Agents beantwortet eine Frage und hört auf — eine Wurzel zeigt ihren Prompt und ihre finale Antwort, ein Subagent zeigt seine Aufgabe, sein Denken dort, wo der Provider Klartext offengelegt hat, und seine Antwort — während ein Prozess, eine Datei, ein Netzwerk-Endpunkt oder ein Modell überhaupt keine Conversation zeigt, denn eine Conversation gehört einem Agent. Ein vom Provider verschlüsselter Turn liest sich als beobachtet ohne Klartext und nicht als nie aufgezeichnet, der Block, den ein Provider jedem Subagent voranstellt, wird nie als die Zuweisung eines Agents dargestellt, und eine Antwort, die Routing-Wörter zitiert, bleibt unversehrt. Die provider-neutralen, agent-lokalen Multi-Agent-Conversations, die jeder Agent besitzt, werden über alle Archive hinweg zusammengeführt, die ein Run geschrieben hat, sodass ein mehrfach aufgezeichneter Agent weiterhin zeigt, was er gesagt hat. Release-Prüfungen fahren das ausgelieferte Dashboard in einem echten Browser durch jede Auswahl, die eine Person treffen kann, in seiner Live- wie in seiner beendeten Form.
 
 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.9 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.9}/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.9**.
 
 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.9 — un seul tableau de bord, pendant le run et après.** Le live, le run terminé et viewer.html étaient trois rendus des mêmes preuves, et la fin d'un run allait chercher un document séparé pour l'écrire par-dessus la page que le lecteur regardait. Il n'y a plus qu'une coque : terminer un run change son état sur place, et viewer.html est ce même tableau de bord enregistré hors ligne. Sélectionner un agent répond à une question et s'arrête — une racine montre son Prompt et sa Réponse finale, un subagent montre sa Tâche, son Raisonnement là où le provider a exposé du texte en clair, et sa Réponse — tandis qu'un processus, un fichier, un point de terminaison réseau ou un modèle ne montre aucune conversation, parce qu'une conversation appartient à un agent. Un turn chiffré par le provider se lit comme observé sans clair plutôt que comme jamais enregistré, le bloc qu'un provider ajoute devant chaque subagent n'est jamais présenté comme l'assignation d'un agent, et une réponse qui cite des mots de routage reste intacte. Les conversations multi-agent provider-neutral et agent-local que chaque agent possède sont agrégées sur toutes les archives qu'un run a écrites, si bien qu'un agent enregistré plusieurs fois montre encore ce qu'il a dit. Les vérifications de release pilotent le tableau de bord livré dans un vrai navigateur, à travers chaque sélection possible, dans sa forme live comme dans sa forme terminé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.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.9 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.9}/README.ja.md

@@ -31,7 +31,7 @@ PyPI から最新の wheel/sdist をインストールします。
 python -m pip install -U execweave
 ```
 
-現在のリリースは **v0.7.7** です。
+現在のリリースは **v0.7.9** です。
 
 開発環境では次のようにインストールできます。
 
@@ -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.9 — 実行中も実行後も、ひとつの Dashboard。** Live、完了後の画面、viewer.html は同じ証拠の三つの描画であり、完了時には別の文書を取得して読者が見ているページに上書きしていました。いまはひとつの shell だけです。完了は開いている画面の状態を変えるだけで、viewer.html はその同じ Dashboard のオフライン保存です。agent を選ぶとひとつの問いに答えて止まります。root は Prompt と Final response を、subagent は Task、provider が平文を公開した場合の Thinking、そして Response を示します。process、file、network endpoint、model は conversation をまったく示しません。conversation は agent のものだからです。provider が暗号化した turn は「観測済みだが平文は非公開」と読まれ、記録されなかったとは読まれません。provider がすべての subagent に前置きするブロックが、ある agent の assignment として示されることはありません。routing の語を引用した回答もそのまま残ります。各 agent が保持する provider-neutral かつ agent-local な multi-agent conversation は、その実行が書き出したすべてのアーカイブを横断して集約されるため、何度も記録された agent も自分が述べたことを示せます。リリース前の検査は、出荷される Dashboard を live と finished の両方の状態で、実物のブラウザで人が行えるあらゆる選択にわたって駆動します。
 
 統合 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.9 は 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.9}/README.ko.md

@@ -31,7 +31,7 @@ PyPI에서 최신 wheel/sdist를 설치합니다.
 python -m pip install -U execweave
 ```
 
-현재 릴리스는 **v0.7.7** 입니다.
+현재 릴리스는 **v0.7.9** 입니다.
 
 개발 설치:
 
@@ -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.9 — 실행 중에도 실행 후에도, 하나의 Dashboard.** Live, 완료된 화면, viewer.html 은 같은 증거의 세 가지 렌더링이었고, 완료 시점에는 별도의 문서를 가져와 읽는 사람이 보고 있던 페이지 위에 덮어썼습니다. 이제 shell 은 하나입니다. 완료는 열려 있는 화면의 상태를 바꿀 뿐이고, viewer.html 은 바로 그 Dashboard 의 오프라인 저장본입니다. agent 를 선택하면 하나의 질문에 답하고 멈춥니다. root 는 Prompt 와 Final response 를, subagent 는 Task 와, provider 가 평문을 노출한 경우의 Thinking, 그리고 Response 를 보여 줍니다. process, file, network endpoint, model 은 conversation 을 전혀 보여 주지 않습니다. conversation 은 agent 의 것이기 때문입니다. provider 가 암호화한 turn 은 기록되지 않은 것이 아니라 관측되었으나 평문이 노출되지 않은 것으로 읽힙니다. provider 가 모든 subagent 앞에 붙이는 블록이 어느 agent 의 assignment 로 제시되는 일도 없습니다. routing 어휘를 인용한 답변도 온전히 남습니다. 각 agent 가 소유한 provider-neutral, agent-local multi-agent conversation 은 그 실행이 남긴 모든 아카이브에 걸쳐 집계되므로, 여러 번 기록된 agent 도 자신이 말한 것을 보여 줍니다. 릴리스 검사는 출시되는 Dashboard 를 live 와 finished 두 상태 모두에서 실제 브라우저로, 사람이 할 수 있는 모든 선택에 걸쳐 구동합니다.
 
 통합 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.9는 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.9}/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.9**.
 
 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.9 — one dashboard, while the run happens and afterwards.** Live, the finished run and viewer.html were three renderings of the same evidence, and completion fetched a separate document and wrote it over the page a reader was watching. There is now one shell: finishing a run changes its state in place, and viewer.html is that same dashboard saved offline. Selecting an agent answers one question and stops — a root shows its Prompt and its Final response, a subagent shows its Task, its Thinking where the provider exposed plaintext, and its Response — while a process, a file, a network endpoint or a model shows no conversation at all, because a conversation belongs to an agent. A turn the provider encrypted reads as observed without plaintext rather than as never recorded, the block a provider prepends to every subagent is never presented as one agent's assignment, and an answer that quotes routing words survives intact. The provider-neutral, agent-local multi-agent conversations each agent owns are aggregated across every archive a run wrote, so an agent recorded many times still shows what it said. Release checks drive the shipped dashboard in a real browser through every selection a person can make, in both its live and its finished form.
 
 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.9 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.9}/README.ru.md

@@ -31,7 +31,7 @@ ExecWeave — source-available, local-first проект наблюдаемос
 python -m pip install -U execweave
 ```
 
-Текущая версия — **v0.7.7**.
+Текущая версия — **v0.7.9**.
 
 Для разработки:
 
@@ -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.9 — одна панель, во время прогона и после него.** Live, завершённый прогон и viewer.html были тремя отрисовками одних и тех же свидетельств, а завершение забирало отдельный документ и записывало его поверх страницы, которую читатель уже смотрел. Теперь оболочка одна: завершение меняет состояние на месте, а viewer.html — это та же панель, сохранённая офлайн. Выбор agent отвечает на один вопрос и останавливается: корень показывает свой Prompt и итоговый ответ, subagent — свою задачу, своё рассуждение там, где provider раскрыл открытый текст, и свой ответ, тогда как процесс, файл, сетевая конечная точка или модель не показывают conversation вовсе, потому что conversation принадлежит agent. Turn, зашифрованный provider, читается как наблюдавшийся без открытого текста, а не как никогда не записанный; блок, который provider добавляет перед каждым subagent, никогда не подаётся как задание какого-либо agent; ответ, цитирующий слова маршрутизации, остаётся целым. Provider-neutral, agent-local multi-agent conversations, которыми владеет каждый agent, собираются по всем архивам, записанным прогоном, поэтому agent, записанный много раз, по-прежнему показывает сказанное им. Релизные проверки ведут поставляемую панель в настоящем браузере через каждый выбор, который может сделать человек, и в live-, и в завершённой форме.
 
 Единый 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.9 объединяет 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.9}/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.9**。
 
 开发安装：
 
@@ -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.9 — 运行中与运行后，同一套 Dashboard。** Live、完成后的画面与 viewer.html 原本是同一批证据的三种渲染，而且运行结束时会去抓另一份文件覆盖读者正在看的页面。现在只有一套 shell：完成只让当前画面转为结束状态，viewer.html 就是同一套 Dashboard 的离线存档。选取一个 agent 只回答一个问题就停——root 显示它的 Prompt 与 Final response，subagent 显示 Task、provider 有公开明文时的 Thinking、以及 Response——而 process、file、网络端点或 model 完全不显示任何对话，因为对话属于 agent。provider 加密的 turn 读作「已观测但未公开明文」，而不是从未记录；provider 加在每个 subagent 前面的内容永远不会被当成某个 agent 的交办；引用了 routing 字眼的回答也完整保留。每个 agent 各自拥有的 provider-neutral、agent-local multi-agent conversation 会跨该次运行写出的所有存档聚合，因此被记录多次的 agent 仍然显示得出它说了什么。发布前的检查会用真实浏览器把出货的 Dashboard 在 live 与 finished 两种状态下走过每一种可操作的选取。
 
 统一 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.9 组合 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.9}/README.zh-TW.md

@@ -31,7 +31,7 @@ ExecWeave 是一個 source-available、local-first 的可觀測性專案，會
 python -m pip install -U execweave
 ```
 
-目前正式版本是 **v0.7.7**。
+目前正式版本是 **v0.7.9**。
 
 開發安裝：
 
@@ -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.9 — 執行中與執行後，同一套 Dashboard。** Live、完成後的畫面與 viewer.html 原本是同一批證據的三種渲染，而且執行結束時會去抓另一份文件覆蓋讀者正在看的頁面。現在只有一套 shell：完成只讓當前畫面轉為結束狀態，viewer.html 就是同一套 Dashboard 的離線存檔。選取一個 agent 只回答一個問題就停——root 顯示它的 Prompt 與 Final response，subagent 顯示 Task、provider 有公開明文時的 Thinking、以及 Response——而 process、file、網路端點或 model 完全不顯示任何對話，因為對話屬於 agent。provider 加密的 turn 讀作「已觀測但未公開明文」，而不是從未記錄；provider 加在每個 subagent 前面的內容永遠不會被當成某個 agent 的交辦；引用了 routing 字眼的回答也完整保留。每個 agent 各自擁有的 provider-neutral、agent-local multi-agent conversation 會跨該次執行寫出的所有存檔聚合，因此被記錄多次的 agent 仍然顯示得出它說了什麼。發布前的檢查會用真實瀏覽器把出貨的 Dashboard 在 live 與 finished 兩種狀態下走過每一種可操作的選取。
 
 統一 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.9 整合 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.9}/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.9 release metadata
+version = "0.7.9"
 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.9}/src/execweave/__init__.py

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