feat(glados): make managed work lifecycle actionable

[BreakTheBeta]

Follows merged permission fix #25.

Managed project leads already use ordinary T3 threads and independent worktrees, but they could not own a mirrored task at an approved remote home. Wake delivery also used an in-memory aggregate signature and a generic revision-based message. A runtime restart or a changed but unrelated portfolio revision could therefore emit another generic manager turn, while a separately delegated child was not durably linked to the queued Pitboss task at all.

This makes the managed lifecycle coherent:

• A local project lead may coordinate a mirrored task only when saved two-sided peer authority names this environment as coordinator and fixes the destination task home. The destination retains provider, permission, workspace, task revision and acceptance authority.
• Local lead ownership survives home reconciliation without rewriting the home revision. Removing the peer from the brief fences the lead immediately.
• Managed assignment persists the attempt/thread before launch, so pending and running writers are not offered as ready work.
• Stopped or failed attempts and submitted results become explicit review obligations; a finished model turn is never treated as accepted evidence.
• Wake obligations use the existing Pitboss effect outbox. Per-message, per-ready-revision and per-attempt keys survive runtime restart and delivery retry. Deterministic command IDs make ambiguous retries idempotent, while decisions and genuinely new readiness still deliver.
• Review keys follow the attempt/state rather than unrelated task revisions. A local ownership epoch makes A→GLaDOS→A handoffs distinct without changing a mirrored task’s home revision.
• Capacity-blocked keys stay pending, successful partial batches receipt only the lines actually sent, and bounded wake/general-effect lanes prevent repeated wake failures from starving worker launches or peer effects.
• Machine-generated wake turns are labelled system / server. Stable role and authority rules remain in injected context; the wake contains only event details and the next management action.
• Web/desktop and mobile show task owner, environment, status, worker workspace and durable thread targets. Mobile also links to the ordinary project-lead thread.

Before:

Review current work and unresolved messages with work_read. Pending user decisions park only their tasks. Continue independent assignments...

After examples:

Managed work changed:
Newly ready · task sync-contract · attempt none · owner project lead platform · task status queued. Next: assign a managed worker or record the condition that blocks assignment.

Managed work changed:
Worker stopped · task sync-contract · attempt assign-2 · owner project lead platform · task status blocked. Next: inspect thread work-assign-2, then record review, rework, or a concrete blocker; do not accept the turn itself as evidence.

Visual evidence from the parent coordinator’s integrated web review:

Before	After

Read-only diagnosis of the current local T3 state found 15 machine-origin generic GLaDOS wakes with distinct pitboss:wake:glados:1:<revision> IDs and one user/web copy. The current snapshot had no unacknowledged Pitboss inbox messages; the queued upstream task had zero managed attempts despite its separately delegated child. This demonstrates actual server emissions and the missing managed linkage. It does not claim every historical message had an identical actionable signature.

Checks:

• vp run test:pitboss:local (14 files, 99 tests)
• vp run test:pitboss:coordination (10 passed, 1 intentionally skipped live-source test)
• server, web and mobile scoped typechecks
• targeted formatting, lint and git diff --check

Remote proof uses two independent in-memory SQLite stores and loopback HTTP peer servers with explicit configuration, shared secret, two-sided proposals, coordinator handoff, fixed home, idempotent delivery, destination-selected model, reconciliation and rebuild. It does not claim a live authorized destination. The parent coordinator supplied the integrated web before/after evidence and confirmed the web production build. No mobile native pass is claimed because the installed dev client predates an unrelated keyboard patch; no dev/browser server was started here.

Implemented with GPT-5 Codex in the T3 Code harness.