agent-pbx 2.3.0__tar.gz → 2.4.0__tar.gz

{agent_pbx-2.3.0/src/agent_pbx.egg-info → agent_pbx-2.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-pbx
-Version: 2.3.0
+Version: 2.4.0
 Summary: Runtime-grounded control plane for durable Codex Agent and Operator sessions.
 Author: Agent PBX contributors
 License-Expression: Apache-2.0
@@ -109,7 +109,8 @@ origin policy, and versioned product-site contract.
 
 See [the architecture overview](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/architecture.md),
 [the project wiki](https://github.com/m4xx3d0ut/agent-pbx/wiki),
-[the v2.3.0 release notes](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/releases/v2.3.0.md), and
+[the stable v2.4.0 release notes](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/releases/v2.4.0.md),
+[the v2.4 acceptance record](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/acceptance/v2.4-uat.md), and
 [the accepted architecture decisions](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/adr/README.md) for the complete
 control-plane and compatibility boundaries.
 
@@ -630,9 +631,14 @@ only true for a Codex-like target.
 
 A terminal handoff update creates one idempotent completion receipt for the
 exact source root Operator or source fork. The Operators pane keeps semantic
-`State` and `Flow` separate from tmux `Live`; pending results appear as
-`⇠ REVIEW` with an `RCPT` marker. The top banner reports `RECEIPTS N`, and F8
-opens the completion center after pending approvals and before guarded actions.
+`State` and `Flow` separate from tmux `Live`: `State` is the projected PBX
+workflow, `Flow` is its highest-priority durable route or action, `Camp` is the
+active nonterminal campaign count, and `Live` is tmux/runtime liveness. Raw
+Codex activity does not drive `State`, `Flow`, or `Camp`. Selecting an Operator
+shows the projection reason, source, and durable subject identity in Latest
+detail. Pending results appear as `⇠ REVIEW` with an `RCPT` marker. The top
+banner reports `RECEIPTS N`, and F8 opens the completion center after pending
+approvals and before guarded actions.
 Reviewing and acknowledging a receipt stops retry/attention state without
 changing the completed, failed, blocked, or canceled handoff. Nohup recipients
 receive an exact queued command. Report-mode terminal injection requires an
@@ -678,7 +684,16 @@ export AGENT_PBX_OPERATOR_BROKER_MAX_IN_FLIGHT="1"
 `root_operator` is intentionally a local administrator choice; it is not the
 committed default. Requests survive TUI replacement, use a bounded executor
 lease, recover commit evidence from durable action receipts, and fail closed on
-scope, workspace, session, pane, Git parent, or path drift.
+scope, workspace, session, pane, Git parent, or path drift. In root-supervised
+mode, F8 first persists a deterministic request and an
+`awaiting_broker_approval` needs-input report. A succeeded executor result is
+not campaign completion: the root must validate the exact terminal action
+transaction with `pbx_operator_validate_broker_checkpoint`, then acknowledge
+the resulting handoff completion receipt. Assignment and campaign completion
+fail closed while any request, transaction, actionable handoff, or completion
+receipt is outstanding. If recovery is needed after terminal history exists,
+`pbx_operator_create_campaign_successor` creates one idempotent successor
+without reopening or rewriting the predecessor.
 
 The committed default remains manual approval. On a trusted local workstation,
 the approval center's `Trust & approve` action can grant a one-hour,

{agent_pbx-2.3.0 → agent_pbx-2.4.0}/README.md

@@ -71,7 +71,8 @@ origin policy, and versioned product-site contract.
 
 See [the architecture overview](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/architecture.md),
 [the project wiki](https://github.com/m4xx3d0ut/agent-pbx/wiki),
-[the v2.3.0 release notes](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/releases/v2.3.0.md), and
+[the stable v2.4.0 release notes](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/releases/v2.4.0.md),
+[the v2.4 acceptance record](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/acceptance/v2.4-uat.md), and
 [the accepted architecture decisions](https://github.com/m4xx3d0ut/agent-pbx/blob/dev/docs/adr/README.md) for the complete
 control-plane and compatibility boundaries.
 
@@ -592,9 +593,14 @@ only true for a Codex-like target.
 
 A terminal handoff update creates one idempotent completion receipt for the
 exact source root Operator or source fork. The Operators pane keeps semantic
-`State` and `Flow` separate from tmux `Live`; pending results appear as
-`⇠ REVIEW` with an `RCPT` marker. The top banner reports `RECEIPTS N`, and F8
-opens the completion center after pending approvals and before guarded actions.
+`State` and `Flow` separate from tmux `Live`: `State` is the projected PBX
+workflow, `Flow` is its highest-priority durable route or action, `Camp` is the
+active nonterminal campaign count, and `Live` is tmux/runtime liveness. Raw
+Codex activity does not drive `State`, `Flow`, or `Camp`. Selecting an Operator
+shows the projection reason, source, and durable subject identity in Latest
+detail. Pending results appear as `⇠ REVIEW` with an `RCPT` marker. The top
+banner reports `RECEIPTS N`, and F8 opens the completion center after pending
+approvals and before guarded actions.
 Reviewing and acknowledging a receipt stops retry/attention state without
 changing the completed, failed, blocked, or canceled handoff. Nohup recipients
 receive an exact queued command. Report-mode terminal injection requires an
@@ -640,7 +646,16 @@ export AGENT_PBX_OPERATOR_BROKER_MAX_IN_FLIGHT="1"
 `root_operator` is intentionally a local administrator choice; it is not the
 committed default. Requests survive TUI replacement, use a bounded executor
 lease, recover commit evidence from durable action receipts, and fail closed on
-scope, workspace, session, pane, Git parent, or path drift.
+scope, workspace, session, pane, Git parent, or path drift. In root-supervised
+mode, F8 first persists a deterministic request and an
+`awaiting_broker_approval` needs-input report. A succeeded executor result is
+not campaign completion: the root must validate the exact terminal action
+transaction with `pbx_operator_validate_broker_checkpoint`, then acknowledge
+the resulting handoff completion receipt. Assignment and campaign completion
+fail closed while any request, transaction, actionable handoff, or completion
+receipt is outstanding. If recovery is needed after terminal history exists,
+`pbx_operator_create_campaign_successor` creates one idempotent successor
+without reopening or rewriting the predecessor.
 
 The committed default remains manual approval. On a trusted local workstation,
 the approval center's `Trust & approve` action can grant a one-hour,

{agent_pbx-2.3.0 → agent_pbx-2.4.0}/src/agent_pbx/__init__.py

@@ -2,4 +2,4 @@
 
 __all__ = ["__version__"]
 
-__version__ = "2.3.0"
+__version__ = "2.4.0"

{agent_pbx-2.3.0 → agent_pbx-2.4.0}/src/agent_pbx/agent.py

@@ -182,7 +182,13 @@ handoff. The request carries exact paths, expected parent, commit subject,
 campaign, workspace-set, and authority digests. A local Agent PBX TUI executes
 the durable stop, exact commit, and same-session resume. Read the durable result
 with `pbx_operator_get_broker_checkpoint`, inspect its receipt summary, and
-perform the remaining root validation. Edit forks and review forks must not
+validate the exact terminal action transaction with
+`pbx_operator_validate_broker_checkpoint` before assignment or campaign
+completion. The durable request and its `awaiting_broker_approval` needs-input
+report are restart-idempotent. Outstanding handoffs, transactions, requests,
+or unacknowledged completion receipts block completion. Use
+`pbx_operator_create_campaign_successor` for new recovery work after a campaign
+became terminal; terminal history is never reopened. Edit forks and review forks must not
 request, cancel, or impersonate this root workflow.
 
 Operator forks have roles. The default/edit fork may coordinate caller-directed