runtime: ship provider runtime 5.0.3 in agent-collab 7.0.1

.claude-plugin/marketplace.base.json

@@ -9,7 +9,7 @@
   "plugins": [],
   "metadata": {
     "description": "Agent collaboration plugin marketplace",
-    "version": "7.0.0",
+    "version": "7.0.1",
     "repository": "https://github.com/sumitake/agent-collab"
   }
 }

.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "agent-collab",
       "description": "Unified collaboration package with semantic actions, source-grounded context, empirical project estimation, and a verified plugin-relative direct native runtime.",
-      "version": "7.0.0",
+      "version": "7.0.1",
       "author": {
         "name": "John Osumi"
       },
@@ -34,7 +34,7 @@
   ],
   "metadata": {
     "description": "Agent collaboration plugin marketplace",
-    "version": "7.0.0",
+    "version": "7.0.1",
     "repository": "https://github.com/sumitake/agent-collab"
   }
 }

README.md

@@ -5,7 +5,7 @@ compatible hosts. Version 7 keeps the closed semantic coordinator and
 co-packaged direct native runtime while adding provider-neutral quality and
 effort profiles, current-portfolio routing, and truthful advisory degradation.
 
-This public repository's current source is **agent-collab** (v7.0.0).
+This public repository's current source is **agent-collab** (v7.0.1).
 
 Current published release: **7.0.0** ([`v7.0.0`](https://github.com/sumitake/agent-collab/releases/tag/v7.0.0)).
 It carries signed provider runtime `5.0.0`, a schema-4 manifest with runtime
@@ -21,6 +21,24 @@ machine-operational contract for the repository source. The dated
 records the completed publication and keeps repository, tag, release,
 installation, and readiness claims separate.
 
+## What's new - v7.0.1
+
+- **Liveness follows admitted progress.** Wire schema 10 signs one timeout mode
+  per logical action. Repository architecture, review, frontend review,
+  governance, and both code-generation actions use a finite inactivity lease
+  only after supervised provider start; other actions retain a total deadline.
+  Content-free runtime progress renews the lease, while prose and ordinary
+  output do not.
+- **Sealed-artifact review authority.** Review and governance accept a valid
+  structured final against the exact sealed source and canonical tracked
+  artifact paths even when carrier tool telemetry is absent, noisy, or denied.
+  Provider terminal failures, source-seal changes, escaped paths, invalid
+  finals, and cleanup failures remain hard failures.
+- **One paired runtime generation.** Signed provider runtime `5.0.3` carries
+  the source-containment reset and admitted-progress corrections together under
+  wire digest
+  `05aaa8a128f69502bb8bd4a38a5eda0716268ac95524e41cc07ba091b8162be8`.
+
 ## What's new - v7.0.0
 
 - **Exact repository binding.** Every repository request now carries both its
@@ -140,7 +158,7 @@ The public source expects:
 - manifest schema 4;
 - runtime protocol 4;
 - native manifest contract 4;
-- provider runtime version `5.0.0`;
+- provider runtime version `5.0.3`;
 - one top-level closed `wire_contract` plus canonical
   `wire_contract_sha256`, bound into each artifact record; and
 - no action-membership mirror in artifact entries.

changelog.d/2026-09-01-001-runtime-5.0.3.md

@@ -0,0 +1,13 @@
+- Ship one paired signed provider runtime 5.0.3 generation with wire schema 10,
+  preserving exact-head source seals, structured-final validation, canonical
+  tracked artifact paths, deterministic cleanup, and the one-process/no-replay
+  lifecycle.
+- Treat absent, noisy, denied, and outside-support carrier tool telemetry as
+  diagnostic for repository review and governance; provider terminal failures,
+  source changes, escaped paths, invalid finals, and cleanup failures remain
+  hard failures, while context and private-patch evidence stay strict.
+- Admit `architecture.repository` review-diff transport and signed
+  admitted-progress inactivity without adding a broker, sandbox helper,
+  provider fingerprint gate, retry, or fallback path.
+- Advance the public client, schema, dual-architecture runtime mirrors, and
+  regression suite together as agent-collab 7.0.1.

plugins/agent-collab/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-collab",
-  "version": "7.0.0",
+  "version": "7.0.1",
   "description": "Unified collaboration package with semantic agent actions, source-grounded context, and a verified plugin-relative direct native runtime.",
   "author": {
     "name": "John Osumi"

plugins/agent-collab/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-collab",
-  "version": "7.0.0",
+  "version": "7.0.1",
   "description": "Unified collaboration package with semantic agent actions, source-grounded context, and a verified plugin-relative direct native runtime.",
   "author": {
     "name": "John Osumi"

plugins/agent-collab/README.md

@@ -5,7 +5,7 @@ boundary and one co-packaged native runtime. Public callers choose a logical
 action and source; they never choose a provider route, transport action, model,
 binary, socket, lane, or lifecycle command.
 
-Current repository source: **7.0.0**
+Current repository source: **7.0.1**
 
 Current published release: **7.0.0**
 ([`v7.0.0`](https://github.com/sumitake/agent-collab/releases/tag/v7.0.0)); it
@@ -15,6 +15,14 @@ transport actions, and 19 valid action/source pairs. One post-restart Codex
 installation has been verified against this release. That is host-specific
 evidence and does not claim all-host installation, activation, or readiness.
 
+The unreleased 7.0.1 source pairs signed provider runtime `5.0.3` with wire
+schema 10. The descriptor signs each logical action's timeout mode, so
+repository architecture, review, frontend review, governance, and both
+code-generation actions use admitted-progress inactivity after supervised
+provider start. Review and governance authority comes from the exact sealed
+source, valid structured final, canonical tracked artifact paths, and cleanup;
+carrier tool telemetry remains diagnostic and contributes no path authority.
+
 Version 7.0.0 binds every repository request to its canonical root and exact
 expected head, rejects real TTY input before runtime loading, and derives
 replay-safe recovery from closed typed failure traces. A proven pre-inference
@@ -131,11 +139,13 @@ The canonical request contains exactly these common fields:
   target unless a future signed descriptor explicitly admits it.
 - The coordinator observes the current host family and adds `author_lineage`
   internally. A caller-supplied lineage is rejected.
-- `timeout_ms` is 1–600000. It is the enforced total deadline for every action
-  except `codegen.repository` and `frontend_codegen.repository`; after their
-  signed runtime reports supervised provider start, it becomes the maximum
-  admitted-progress inactivity interval. A value over the cap is rejected with
-  an actionable `timeout_ms_over_cap` error naming the `max`, not silently
+- `timeout_ms` is 1–600000. It is the enforced total deadline unless the signed
+  descriptor selects `admitted_progress_inactivity`. For
+  `architecture.repository`, `codegen.repository`, `frontend_codegen.repository`,
+  `frontend_review.repository`, `governance.repository`, and
+  `review.repository`, it becomes the maximum inactivity interval only after
+  supervised provider start. A value over the cap is rejected with an
+  actionable `timeout_ms_over_cap` error naming the `max`, not silently
   clamped.
 - `prompt` is non-empty UTF-8, bounded to 1 MiB.
 - Every repository action adds exactly one canonical absolute `repo_root` and
@@ -182,14 +192,15 @@ returns every logical action in one zero-inference snapshot:
 
 ## Direct runtime boundary
 
-The workspace build emits one schema-4 manifest with wire schema 8, runtime
-protocol 4, native contract 4, and provider runtime `5.0.0`. Schema 8 retains
-the schema-7 logical agents, model lineages, action-compatible targets, and
-effort floors while requiring every repository source to carry its exact
-nonzero expected head. Request-bound occupied lineages and evidence anchors
-remain closed and runtime-adjudicated. The wire revision records compatible
-descriptor evolution; runtime protocol 4 remains the executable compatibility
-boundary. The manifest carries one
+The workspace build emits one schema-4 manifest with wire schema 10, runtime
+protocol 4, native contract 4, and provider runtime `5.0.3`. Schema 10 retains
+the schema-9 signed timeout modes, exact repository-head binding, logical
+agents, model lineages, action-compatible targets, and effort floors while
+admitting repository architecture progress under the same inactivity contract.
+Request-bound occupied lineages and evidence anchors remain closed and
+runtime-adjudicated. The wire revision records compatible descriptor evolution;
+runtime protocol 4 remains the executable compatibility boundary. The manifest
+carries one
 top-level closed `wire_contract` and its canonical `wire_contract_sha256`.
 That descriptor is the only source for:
 
@@ -206,14 +217,15 @@ That descriptor is the only source for:
 Artifact entries contain bundle membership and signing identity only. They do
 not mirror action membership.
 
-The repository runtime 5.0.0 build preserves the action-scoped Claude edge and
+The repository runtime 5.0.3 build preserves the action-scoped Claude edge and
 the closed protocol-4 authority model. Gemini remains the subscription-preferred
 repository and governance route when eligible; Agy versions below 1.1.20 fail
 closed before inference. Grok runs with request-private provider state and the
-sealed repository as its only project context. Code-generation actions use the
-public timeout as an admitted-progress inactivity lease after supervised
-provider start; ordinary actions retain a fixed total deadline. Provider-started
-or uncertain terminal outcomes never authorize replay or fallback invocation.
+sealed repository as its only project context. Actions marked
+`admitted_progress_inactivity` by the signed descriptor use the public timeout
+as an inactivity lease after supervised provider start; other actions retain a
+fixed total deadline. Provider-started or uncertain terminal outcomes never
+authorize replay or fallback invocation.
 
 Claude uses the official structured CLI only for document-intent requests. The
 route is read-only, source-bound to documents, and cost-last after Gemini and
@@ -233,11 +245,11 @@ For each accepted request the public client:
 4. Rechecks entrypoint identity immediately before spawning.
 5. Starts the fixed entrypoint as a new process group with bounded stdin,
    stdout, and stderr.
-6. Applies the shared deadline (or, for codegen after supervised provider start,
-   the admitted-progress inactivity lease), explicitly sends TERM, then KILL if
-   needed, and reaps the group. Only the runtime's fixed content-free progress
-   mark renews that lease; raw output and progress-channel EOF do not. Cleanup
-   after a lost lease uses its own short bounded reserve.
+6. Applies the shared deadline or the descriptor-admitted inactivity lease
+   after supervised provider start, explicitly sends TERM, then KILL if needed,
+   and reaps the group. Only the runtime's fixed content-free progress mark
+   renews that lease; raw output and progress-channel EOF do not. Cleanup after
+   a lost lease uses its own short bounded reserve.
 7. Validates the exact success, ungrounded advisory, or failure response
    against the descriptor.