execweave 0.7.3__tar.gz → 0.7.5__tar.gz

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

@@ -0,0 +1,42 @@
+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 }}"

{execweave-0.7.3 → execweave-0.7.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: execweave
-Version: 0.7.3
+Version: 0.7.5
 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.5**.
 
 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.5 — per-agent conversation isolation by default, and an evidence availability matrix.** Building on the provider-neutral, agent-local multi-agent conversations materialized in earlier releases, opening a run now shows one self-contained section per agent: each holds the turns that agent sent and the turns addressed to it, so a child keeps its own assignment and answer while a sibling's exchange never appears. Field-level availability is recorded separately from conversation completeness, so an encrypted reasoning field no longer drags an otherwise archived transcript down. An offline capability probe reports, per client and surface, what each provider actually exposes, and records what cannot be read without claiming to know why.
 
 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.5 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.3 → execweave-0.7.5}/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.5**.
 
 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.5 — Conversation-Isolation pro Agent als Standard und eine Evidence-Availability-Matrix.** Beim Öffnen eines Runs hat jeder Agent nun einen eigenen Abschnitt: Er enthält die Turns, die dieser Agent gesendet hat, und die an ihn gerichteten, sodass ein Child seine eigene Assignment und Antwort behält, während ein Austausch zwischen Siblings nie erscheint. Field-level availability wird getrennt von der conversation completeness erfasst, sodass ein verschlüsseltes Reasoning-Feld ein ansonsten vollständig archiviertes Transcript nicht mehr herabstuft. Eine Offline-Capability-Probe meldet je Client und Surface, was der Provider tatsächlich offenlegt, und hält Nichtlesbares fest, ohne den Grund zu behaupten.
 
 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.5 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.3 → execweave-0.7.5}/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.5**.
 
 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.5 — isolation des conversations par agent par défaut, et matrice de disponibilité des evidence.** À l’ouverture d’un run, chaque agent dispose désormais de sa propre section : elle contient les turns que cet agent a envoyés et ceux qui lui étaient adressés, si bien qu’un child conserve son assignment et sa réponse tandis qu’un échange entre siblings n’apparaît jamais. La field-level availability est enregistrée séparément de la conversation completeness, de sorte qu’un champ reasoning chiffré ne dégrade plus un transcript par ailleurs archivé. Une capability probe hors ligne rapporte, par client et par surface, ce que chaque provider expose réellement, et consigne ce qui reste illisible sans prétendre en connaître la raison.
 
 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.5 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.3 → execweave-0.7.5}/README.ja.md

@@ -31,7 +31,7 @@ PyPI から最新の wheel/sdist をインストールします。
 python -m pip install -U execweave
 ```
 
-現在のリリースは **v0.7.2** です。
+現在のリリースは **v0.7.5** です。
 
 開発環境では次のようにインストールできます。
 
@@ -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.5 — 既定で per-agent conversation isolation、そして evidence availability matrix。** run を開くと各 agent が独立したセクションを持ち、その agent が送った turn と宛てられた turn だけを含みます。child は自身の assignment と answer を保持し、sibling 同士のやり取りは現れません。field-level availability は conversation completeness と分けて記録されるため、reasoning フィールドが暗号化されていても、完全に保存された transcript が一緒に降格されることはありません。オフラインの capability probe は client と surface ごとに provider が実際に公開したものを報告し、読み取れないものは理由を断定せずに記録します。
 
 統合 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.5 は 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.3 → execweave-0.7.5}/README.ko.md

@@ -31,7 +31,7 @@ PyPI에서 최신 wheel/sdist를 설치합니다.
 python -m pip install -U execweave
 ```
 
-현재 릴리스는 **v0.7.2** 입니다.
+현재 릴리스는 **v0.7.5** 입니다.
 
 개발 설치:
 
@@ -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.5 — 기본값이 된 per-agent conversation isolation, 그리고 evidence availability matrix.** run을 열면 각 agent가 독립된 섹션을 가지며, 그 agent가 보낸 turn과 그 agent에게 전달된 turn만 포함합니다. child는 자신의 assignment와 answer를 유지하고 sibling 간의 교환은 나타나지 않습니다. field-level availability는 conversation completeness와 분리되어 기록되므로 reasoning 필드가 암호화되어도 완전히 보관된 transcript가 함께 강등되지 않습니다. 오프라인 capability probe는 client와 surface별로 provider가 실제 노출한 것을 보고하고, 읽을 수 없는 것은 이유를 단정하지 않고 기록합니다.
 
 통합 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.5는 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.3 → execweave-0.7.5}/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.5**.
 
 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.5 — per-agent conversation isolation by default, and an evidence availability matrix.** Building on the provider-neutral, agent-local multi-agent conversations materialized in earlier releases, opening a run now shows one self-contained section per agent: each holds the turns that agent sent and the turns addressed to it, so a child keeps its own assignment and answer while a sibling's exchange never appears. Field-level availability is recorded separately from conversation completeness, so an encrypted reasoning field no longer drags an otherwise archived transcript down. An offline capability probe reports, per client and surface, what each provider actually exposes, and records what cannot be read without claiming to know why.
 
 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.5 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.3 → execweave-0.7.5}/README.ru.md

@@ -31,7 +31,7 @@ ExecWeave — source-available, local-first проект наблюдаемос
 python -m pip install -U execweave
 ```
 
-Текущая версия — **v0.7.2**.
+Текущая версия — **v0.7.5**.
 
 Для разработки:
 
@@ -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.5 — изоляция conversation по agent по умолчанию и матрица доступности evidence.** При открытии run каждый agent теперь имеет собственную секцию: в неё входят turns, отправленные этим agent, и те, что были адресованы ему, поэтому child сохраняет собственные assignment и ответ, а обмен между siblings не появляется никогда. Field-level availability фиксируется отдельно от conversation completeness, поэтому зашифрованное поле reasoning больше не понижает полностью архивированный transcript. Офлайновый capability probe сообщает по каждому client и surface, что provider действительно раскрывает, и фиксирует нечитаемое, не утверждая причину.
 
 Единый 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.5 объединяет 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.3 → execweave-0.7.5}/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.5**。
 
 开发安装：
 
@@ -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.5 — 默认的 per-agent conversation isolation，以及 evidence availability matrix。** 打开一次 run，现在每个 agent 各有一个独立区块：只包含该 agent 发出的与寄给它的 turn，因此 child 保留自己的 assignment 与 answer，而 sibling 之间的往来完全不会出现。field-level availability 与 conversation completeness 分开记录，因此某个 reasoning 字段被加密，不会把已完整归档的 transcript 一起降级。离线的 capability probe 会按 client 与 surface 报告各 provider 实际暴露了什么，并记录读不到的部分，而不宣称知道原因。
 
 统一 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.5 组合 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.3 → execweave-0.7.5}/README.zh-TW.md

@@ -31,7 +31,7 @@ ExecWeave 是一個 source-available、local-first 的可觀測性專案，會
 python -m pip install -U execweave
 ```
 
-目前正式版本是 **v0.7.2**。
+目前正式版本是 **v0.7.5**。
 
 開發安裝：
 
@@ -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.5 — 預設的 per-agent conversation isolation，以及 evidence availability matrix。** 打開一次 run，現在每個 agent 各有一個獨立區塊：只包含該 agent 送出的與寄給它的 turn，所以 child 保留自己的 assignment 與 answer，而 sibling 之間的往來完全不會出現。field-level availability 與 conversation completeness 分開記錄，因此某個 reasoning 欄位被加密，不會把已完整封存的 transcript 一起降級。離線的 capability probe 會依 client 與 surface 回報各 provider 實際曝露了什麼，並記錄讀不到的部分，而不宣稱知道原因。
 
 統一 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.5 整合 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.5/docs/internal/provider-capability-matrix.md

@@ -0,0 +1,101 @@
+# Provider Capability Matrix (0.7.5)
+
+This document records the evidence contract for the 0.7.5 capability probe. It is an
+internal implementation note, not a release-support claim.
+
+## Scope
+
+The probe is offline. It reads only caller-supplied existing JSON/JSONL artifacts and
+repository source used for the narrow Codex local-decryptor marker audit. It performs no
+network capture, endpoint rewriting, TLS interception, decryption, or provider login.
+
+The machine-readable inventory and matrix are emitted by:
+
+```bash
+python scripts/probe_provider_capability.py --inventory-only
+python scripts/probe_provider_capability.py
+```
+
+A concrete artifact is attached to exactly one inventory combination:
+
+```bash
+python scripts/probe_provider_capability.py \
+  --artifact codex-cli:subscription=tests/fixtures/codex_multi_agent/rollout-main.jsonl
+```
+
+When a client has multiple auth modes or surfaces, the selector must name the ambiguous
+part explicitly. A missing artifact never deletes the row: every required field remains
+in the matrix as `not_observed` with a reason.
+
+## Required inventory
+
+Tier A is release-blocking and contains these clients:
+
+- Codex CLI
+- Claude Code
+- Gemini CLI
+- Cursor Agent
+- OpenCode
+- Ollama
+
+Every combination defined by the inventory probes at least: `system`, `prompt`,
+`messages`, `tool_definitions`, `tool_arguments`, `tool_results`, `assistant_output`,
+`reasoning`, and `usage`.
+
+Tier B is environment-dependent and currently covers Cursor autocomplete/Tab plus local
+LM Studio, llama.cpp, and vLLM surfaces. Untested Tier B rows remain explicit rather than
+being silently omitted.
+
+## Evidence boundaries
+
+Conversation completeness remains owned by `agent_topology.py` and is not changed by
+this stage. Field-level availability is defined separately in
+`evidence_availability.py`. Therefore this is valid:
+
+```text
+conversation_completeness = provider_transcript
+reasoning_availability    = opaque_encrypted
+```
+
+A single unavailable or encrypted field must never downgrade an otherwise archived
+provider transcript.
+
+`available` and `complete_from_surface` have fixed precedence:
+
+- `available`: content is readable, but the probe cannot prove the full surface value was
+  preserved.
+- `complete_from_surface`: the surface observation boundary is known and the complete
+  value supplied by that surface was preserved.
+- If both appear applicable, `complete_from_surface` wins. They are never emitted
+  simultaneously for one field observation.
+
+`complete_from_surface` means complete from the observed integration surface. It does
+not claim visibility into hidden model/provider state.
+
+## Codex encrypted reasoning
+
+The checked-in Codex rollout fixture contains a reasoning item with
+`encrypted_content` beginning with the Fernet-shaped `gAAAAA` prefix. That is direct
+evidence only that an opaque encrypted payload was observed.
+
+The repository source audit looks for a small set of Codex-local decryptor markers. If
+none are observed, the matrix may state:
+
+```text
+availability   = opaque_encrypted
+decryptability = no_local_decryptor_observed
+```
+
+This is an absence observation. It must never be upgraded to `server-side-only`, or to
+`provider_documented_unavailable`, without provider documentation or direct verifiable
+evidence.
+
+## Output semantics
+
+Each matrix row records client, tested client version when directly present in the
+artifact, provider, auth mode, surface, transport mode, field, availability,
+decryptability, evidence source, evidence strength, tier, and notes.
+
+The probe stores paths and classifications, not copied prompt/tool/reasoning content.
+This stage is capability discovery only; it does not add a second full-fidelity storage
+or conversation-ingestion path.

{execweave-0.7.3 → execweave-0.7.5}/pyproject.toml

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

{execweave-0.7.3 → execweave-0.7.5}/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")