Slack: connect authorized tasks to a qualified Code Mower supervisor

[jeffhuber]

Part of Slack epic #903 and roadmap #900; revision 3, supervised bounded execution.

Problem

The merged Slack contract assumes a registered runner, but registration alone does not demonstrate a working, qualified orchestrator. session start prepares state and instructions; it is not a universal process launcher. Selecting hosted Devin as the execution transport cannot satisfy a missing qualified supervisor by promoting Devin to orchestrator.

Scope / PR mapping

One OSS PR: implement the maintained adapter between a privately authorized Slack task and an explicitly configured, qualified Code Mower supervisor runtime. Freeze the versioned admission/claim/status/result contract used by hosted #919/#920. Reuse existing session, lifecycle, role-policy, exact work/run binding, and handoff facilities; provide a real supported runtime invocation/connection for the initial qualified Codex or Claude posture. Avoid a universal launcher, implicit provider fallback, or new Slack-owned orchestration engine.

The OSS adapter owns supervisor readiness/claim, orchestration decisions, and bounded builder/review delegation. Hosted #919 owns durable receipts/queues; #920 owns the authenticated hosted bridge and Slack/provider transport. Source files have one owner per PR. Private operational text travels only through authorized private stores/connections; telemetry uses closed metadata.

Acceptance criteria

• A registered, configured, and role-qualified supervisor is actually reachable and able to accept work before a hosted builder create is permitted.
• Tenant/repository/work/run/operation bindings, claim expiry, revocation, and restart are checked at handoff and re-entry; stale or mismatched claims fail closed.
• An absent/unqualified supervisor leaves work waiting or rejected with an actionable reason, never dispatched as Devin orchestration.
• The supervisor owns task scope, bounded spend, explicit recovery decisions, exact PR/head collection, independent eligible review routing, and completion decisions.
• Builder completion, provider exit, review readiness, and merge status remain separate; unsafe or uncertain takeover cannot start a replacement writer.
• A maintained local supervisor path accepts a synthetic authorized task and drives the builder/review interface; fake hosted queue/provider fixtures cover duplicate claim, ambiguous handoff, disconnect/restart, and cancellation.
• Integration contract/version fixtures are consumable by Slack: durable inbox/outbox and start/status/cancel interaction #919/Slack: Devin dispatch, clarification, completion, and cancellation bridge #920; a live hosted completion and cancellation are verified there and in final Release: qualify and publish basic supervised Slack ingress in v1.5.0 #923, not claimed from unit fixtures.
• No supervisor grants new tracker-write/merge authority; existing repository and owner policy remain effective.

Dependencies and target

Implementation follows #975, #962, and #963; reuse merged #916/#917 and #906. Freeze this contract before #919 runtime integration. It has no Graphify or Board release dependency. Required for #920 and the v1.5.0 canary.

Planned builder: Code Mower Codex. Planned independent reviewer: Code Mower Claude, subject to actual contributor exclusion.

Delivery and evidence

One independently reviewable implementation PR in the repository named below; one named Code Mower builder and one writer per branch. Record the PR, exact head, contributing builder lineage, independent eligible reviewer verdict, focused and relevant regression tests, CI, authoritative code-mower/gate, and outcome. Resolve all P0/P1/P2 findings before merge. Re-review every changed head. An implementation provider never acquires orchestration or merge authority by being selectable. Keep source, diffs, prompts, messages, private context, identities, provider references, raw output, credentials, and personal paths out of public evidence and cloud reporting.

Planned builder assignments are scheduling proposals, not active sessions. Paid canaries require an explicit campaign-wide cap and stable private bindings; no uncertain automatic retry and no new recovery allowance is implied by this issue.

[jeffhuber]

Work Order: implement the qualified supervisor adapter for Slack

Build #977 from current main at 5272bfe33d5d5fc583ab672352ee86f880ec5701 with one Code Mower Codex writer and one focused PR. Implement exactly the versioned OSS supervisor admission/claim/status/result boundary described in the issue, using the accepted role, lineage, session and lifecycle contracts. A registered runner must be reachable and role-qualified before any hosted-builder create is permitted; stale, mismatched, revoked or restarted claims fail closed.

Exercise the maintained local supervisor path with synthetic authorized work plus duplicate-claim, ambiguous-handoff, disconnect/restart and cancellation fixtures. Keep implementation completion, provider exit, review readiness and merge status separate. Add no Slack-owned orchestration engine, provider fallback, tracker/merge authority, hosted deployment or paid session.

Avoid campaign-authentication ownership assigned to #983. Run focused and relevant tests, privacy/package checks, commit and push a single codex/ branch, open a draft PR closing #977, add builder:codex and request needs-claude-audit. Record the exact head and validation, then stop without merging.

[jeffhuber]

Dispatch dependency reconciliation

The automated dispatcher skipped this issue because it interpreted forward consumer references #919/#920 as unresolved prerequisites. The issue contract is the reverse: #977 freezes the supervisor boundary consumed by #919 and #920. Its actual prerequisites (#975, #962, #963, #916, #917 and #906) are closed.

The roadmap orchestrator therefore authorizes the existing work order for current main and applies dispatched:codex manually. This changes no scope, review requirement or release authority.

[jeffhuber]

Implemented #977 in draft PR #1011, which closes this exact issue.

Head: 32a210ef205c59d424b040423de01f963314aa63. Contributing builder lineage: Code Mower Codex only; one writer on the codex/977-qualified-supervisor branch.

The implementation adds the versioned qualified-supervisor boundary, supported bounded local Codex invocation, exact claims with renewal/revocation/restart checks, existing hosted-builder lifecycle integration, independent exact-head review routing, and cancellation/exit separation. Consumer schema and synthetic fixtures are packaged for #919/#920.

Validation:

• Current-head CI passed: 4,543-test suite across Python 3.12/3.13/3.14, containment on Linux/macOS, Board qualification, workflow validation and installation rehearsals. The Python 3.14 suite reported 12 skips.
• 111 focused/regression tests passed locally, including 36 supervisor tests, with a synthetic private-store fixture harness for the runner sandbox. The unmodified suite passed in CI.
• Seven targeted package/inventory/readiness tests, release-readiness validation, Ruff, privacy scan, package workflow guard, wheel/sdist build, Twine and packaged schema/fixture verification passed.

Remaining: independent eligible Claude audit is requested with needs-claude-audit; the local CLI audit workflow was skipped and no verdict has been produced. Authoritative code-mower/gate is pending. The PR retains builder:codex and remains a draft; no merge or deployment performed. Live hosted completion/cancellation acceptance remains with #919/#920/#923 and is not claimed from these fixtures.