Epic: Basic supervised Slack ingress for v1.5.0

[jeffhuber]

Canonical completion state — 2026-09-17

This section supersedes the older checklist and sequencing text below where they conflict.

• Slack: freeze command, identity, lifecycle, privacy, and event contracts #916/Slack: app manifest and authenticated bounded ingress envelope #917 authenticated ingress contract
• Slack: connect authorized tasks to a qualified Code Mower supervisor #977 qualified Codex supervisor contract and Supervisor v2: checkpointed clarification and bounded fix operations #1017 supervisor v2 operations
• Slack: durable inbox/outbox and start/status/cancel interaction #919 durable interactions
• Slack: Devin dispatch, clarification, completion, and cancellation bridge #920 public and authorized private bridge implementation; operational canaries remain open
• CodeMower.com: single-workspace Slack OAuth installation and explicit policy binding #918 private admin lifecycle and privacy-log exercise (implementation complete)
• Audit publication: verify repository-dispatch workflow identity correctly #1025 verified audit-publication bootstrap correction
• Slack: minimal opt-in setup, doctor, and runbook for v1.5.0 #922/Slack: explicit private-workspace setup, readiness doctor and runbook #1024 minimal setup, redacted doctor and runbook
• Slack: Devin dispatch, clarification, completion, and cancellation bridge #920 one completion plus one confirmed-cancellation canary against an immutable v1.5 candidate, after explicit numeric cap authorization
• Release: qualify and publish basic supervised Slack ingress in v1.5.0 #923 candidate rehearsals, audit, publication and independent reinstall

#921/#978 and optional #951 are deferred to v1.5.1. #922 does not depend on telemetry or Board/cloud views.

Part of roadmap #900.

Supervised Slack ingress for v1.5.0

Outcome

An authorized Slack user can start, inspect, answer and cancel bounded Code Mower work for an administrator-allowlisted repository. Slack is ingress and conversation transport. A separately qualified configured Codex/Claude supervisor owns orchestration, hosted-builder dispatch, clarification, review, cancellation and recovery. Selecting Devin never promotes it beyond bounded builder work.

Current status

• Slack: freeze command, identity, lifecycle, privacy, and event contracts #916 / Slack: define session ingress and supervision contract #929 — provider-neutral command, identity, lifecycle, privacy and event contract
• Slack: app manifest and authenticated bounded ingress envelope #917 / Slack: authenticate and durably receive bounded ingress #933 — authenticated bounded ingress, replay rejection and durable receipt-before-ack boundary
• CodeMower.com: single-workspace Slack OAuth installation and explicit policy binding #918 — hosted OAuth installation binding and policy store
• Slack: connect authorized tasks to a qualified Code Mower supervisor #977 — OSS qualified supervisor adapter and admission/runtime contract
• Slack: durable inbox/outbox and start/status/cancel interaction #919 — durable inbox/outbox and start/status/cancel/answer interactions
• Slack: Devin dispatch, clarification, completion, and cancellation bridge #920 — supervised hosted-builder bridge
• v1.5.1: Slack telemetry contract and OSS Board/cloud emitters #921 — frozen OSS telemetry contract, emitters and shared fixtures
• v1.5.1: CodeMower.com Slack telemetry, aggregation, and fresh views #978 — hosted telemetry validation, ingest, aggregation and fresh views
• Slack: minimal opt-in setup, doctor, and runbook for v1.5.0 #922 — optional setup, doctor, readiness and operating guidance
• Campaign: support isolated Codex authentication on headless Linux #983 — isolated headless Codex campaign authentication
• Release: qualify and publish basic supervised Slack ingress in v1.5.0 #923 — end-to-end qualification, deployment, publication and final evidence

#918, #977 and #983 can proceed in parallel where repositories and source ownership are independent. #919 consumes #918/#977; #920 follows #919; #921 freezes the cross-repository telemetry contract before #978 implements it; #922 follows both telemetry sides; #923 converges the release.

Safety and privacy

Authorize immutable Slack enterprise/team/app/user identities rather than display names or email. Persist a durable receipt before acknowledging. Deduplicate commands, modals, events, provider creates, answers and outbound messages. Reconcile uncertain paid creates without blind retries. Keep task prose, answers, Slack identities, response URLs, provider references, tokens and raw records out of public evidence, Board projections and cloud aggregates.

Every implementation PR uses one named writer, independent exact-head review, zero unresolved P0/P1/P2 findings, relevant tests, privacy/package checks, normal CI and authoritative gate. Hosted and OSS changes remain separately reviewable.

---

Owner-approved v1.5.0 boundary (2026-09-17)

An authorized user in one private Slack workspace can start, inspect, answer, and cancel bounded Code Mower work for an administrator-allowlisted repository. A separately qualified configured Codex or Claude supervisor owns scope, dispatch, clarification, recovery, review, cancellation, and completion. Hosted Devin remains a bounded builder.

v1.5.0 supports one workspace; immutable user, channel, and repository bindings; private start/status/answer/completion/cancel interactions; one qualified supervisor/provider route; and fail-closed authorization. Slack Connect, public posting, rich status UX, arbitrary provider selection, Slack-specific cloud telemetry, and hosted analytics move to v1.5.1.

Required remaining children are #1022, #918's private administration exercise, #920's completion and cancellation canaries, minimal #922, and #923 release convergence. #921 and #978 remain open as v1.5.1 work and no longer block #922 or #923. Optional #951 Board observation is also deferred to v1.5.1.

[jeffhuber]

S1 started

Remote-session contract #906 is merged, so contract-first issue #916 is now active with a named Code Mower Codex builder.

Scope remains schema, validation, fixtures, and documentation only. Slack is modeled as ingress/conversation transport with no participant, reviewer, or merge authority. Substantial worker code remains sequenced after the Devin v1.4.0 release boundary.

[jeffhuber]

Progress after S1

• S1 Slack: freeze command, identity, lifecycle, privacy, and event contracts #916 merged through PR Slack: define session ingress and supervision contract #929 at exact head 0cce26b35618b31521aac4f92fce5dc0915e0be2 after Code Mower Claude PASS and green Python 3.12/3.13/3.14, package, privacy, and Code Mower gate checks.
• Metadata-only cloud upload after the merge: https://github.com/codemower-ai/code-mower/actions/runs/34688726963
• S2 Slack: app manifest and authenticated bounded ingress envelope #917 is active with a Code Mower Codex builder. It is limited to the app manifest, authenticated bounded ingress envelope, replay rejection, URL verification, durable receipt-before-ack contract, and offline fixtures. It does not dispatch provider work.

Substantial Slack worker/runtime code remains sequenced after the Devin v1.4.0 release boundary.

[jeffhuber]

S2 complete

• S1 Slack: freeze command, identity, lifecycle, privacy, and event contracts #916 / PR Slack: define session ingress and supervision contract #929 merged: provider-neutral Slack command, identity, lifecycle, privacy, and event contract.
• S2 Slack: app manifest and authenticated bounded ingress envelope #917 merged through PR Slack: authenticate and durably receive bounded ingress #933 at exact head e8d37b3946bc6b00e19ccf2274d3a98a4c17736f, merge fffe7641626a3df2b0642357fa05ab00164f4729.
• Builder: Code Mower Codex. Independent exact-head reviewer: Code Mower Claude PASS.
• Validation: 26 focused Slack tests, Python 3.12/3.13/3.14 CI, repository Ruff, privacy, package, Gitar, and code-mower/gate passed.
• Metadata-only cloud upload: https://github.com/codemower-ai/code-mower/actions/runs/34691060563

S2 adds the bounded authenticated receipt-before-ack boundary and minimal manifest without dispatching provider work. Workspace-scoped Enterprise Grid and Slack Connect identities are carried to private policy resolution; true organization-wide installs remain denied. Task text, Slack IDs, payloads, response URLs, tokens, secrets, and receipt content are excluded from Board/cloud/public evidence.

S3 #918 remains the next hosted OAuth/policy step. Substantial Slack worker/runtime delivery stays sequenced after the Devin v1.4.0 release boundary.

[jeffhuber]

v1.5 prerequisite progress:

• Campaign: support isolated Codex authentication on headless Linux #983 merged via PR Campaign: support isolated Codex authentication on headless Linux #1010: isolated headless Codex campaign authentication.
• Slack: connect authorized tasks to a qualified Code Mower supervisor #977 merged via PR Slack: add qualified Code Mower supervisor adapter #1011: qualified supervisor contract and bounded local Codex adapter. Exact-head Claude review passed with zero P0/P1/P2; CI and authoritative gate passed.
• CodeMower.com: single-workspace Slack OAuth installation and explicit policy binding #918's existing authorized private implementation was recovered rather than duplicated. Its required refresh exposed public runner defect Lane runner: support dotted repository slugs in lineage writer IDs #1012 before source mutation; that fix is now in a separate Code Mower lane. Slack: durable inbox/outbox and start/status/cancel interaction #919 remains correctly blocked on CodeMower.com: single-workspace Slack OAuth installation and explicit policy binding #918 while Lane runner: support dotted repository slugs in lineage writer IDs #1012 is resolved.

[jeffhuber]

S4 durable interactions complete; S5 bridge queued

Public #919 is complete through the authorized private implementation. Code Mower Claude was the sole builder; Code Mower Codex independently audited the exact final head and reported zero P0/P1/P2. The implementation merged only after 2,007 unit tests, lint/typecheck/build, 24/24 PostgreSQL interaction subtests on both schema paths, full CI and the authoritative gate passed.

The accepted boundary provides durable receipt/task/outbox state, start/status/cancel/answer interactions, stable deduplication, requester-private defaults, recipient revalidation, uncertain-delivery reconciliation, end-to-end attempt deadlines, restart recovery, and concurrency-safe retention of outstanding replies. It remains disabled; no deployment, live Slack mutation, provider create, paid session, or canary occurred.

#920 is now prepared as the next private implementation unit with Code Mower Codex assigned as builder and Code Mower Claude as independent reviewer. Live completion/cancellation canaries remain separately capped owner-authorized work under #923; the implementation lane uses fake transports and cannot spend provider credits.

[jeffhuber]

Code Mower Codex is the sole builder/writer for this unit. Draft PR: #1024

Current head: 1dd92ace0c64ebb9c12aa2513a188c5aaa75fc67.

Implemented the reduced OSS scope: separate explicit manifest preparation, redacted read-only Slack readiness, and private-workspace installation/operation/upgrade/removal guidance. Default Claude + Codex setup is unchanged. The private host supplies authenticated readiness observations through an explicitly selected bounded probe; offline snapshots cannot establish live readiness.

Validation so far: 45 focused Slack tests, repository Ruff, privacy scan, package workflow guard, all 22 release-readiness checks, wheel/sdist build, Twine, and packaged Slack resource verification passed. Broader checks and GitHub CI are in progress. Independent exact-head Claude review is requested with needs-claude-audit; review and code-mower/gate are not yet claimed passed.

No deployment, credentials, live Slack/provider operation or cloud upload occurred. All probe fixtures are synthetic. Remaining: complete validation, independent review/fix rounds and final gate evidence. Live hosted adapter configuration and capped acceptance remain operator/#923 work.

[jeffhuber]

Codex delivery: #922

Implemented and pushed one draft PR: #1024 (closes #922).

Head: 942f1b37d7e1d3f1b404af792e7c41e3ace361f2. Named builder and sole source writer: Code Mower Codex, branch codex/922-slack-operator-setup.

The reduced OSS scope includes explicit interactive/scripted hosted manifest preparation, separate redacted readiness checks, and the private start/status/answer/cancel plus install/upgrade/disable/rollback/uninstall runbook. Default Claude + Codex setup remains unchanged. Live readiness requires the explicitly configured trusted private host probe; offline snapshots cannot pass.

Validation:

• Exact-head CI passed: Python 3.12/3.13/3.14, Linux/macOS containment, Board qualification, package validation and installation rehearsals. Python 3.14 ran 4,795 tests with 12 skips.
• Locally, 45 focused Slack tests, 221 doctor regressions, and six extraction/registry/inventory regressions passed. Ruff, privacy, workflow guard, compile, all 22 release-readiness checks, final wheel/sdist build, Twine, installed-wheel smoke and extracted-package Slack/resource verification passed.
• The attempted local full suite was not green because initial dependency gaps and sandbox private-store restrictions invalidated that run. CI provides the clean full-suite result. The first CI run's registry/inventory omissions were corrected on this same branch.

Remaining: independent audit and gate. The trusted Claude audit workflow failed without publishing a verdict; metadata commands reported a missing code_mower module. The local wrapper also lacks its required token input. needs-claude-audit was re-requested after pushing; needs-owner remains on the PR and issue, and code-mower/gate is pending.

Owner actions:

1. Repair the trusted audit runner/workflow Python/import setup and inspect its private wrapper failure locally.
2. Complete qualified Claude review and verified publication against the exact head above.
3. Return any P0/P1/P2 findings to Codex for same-branch fixes and fresh review; keep the PR draft until review and the authoritative gate pass.

Outcome: implementation delivered for review; owner action required for audit infrastructure. .code-mower/lane-outcome.json records owner_action. No merge, release, deployment, credential change, live Slack/hosted Devin canary or Code Mower cloud upload was performed. Upload evidence is not claimed for the reduced scope; only safe public PR/head, validation and workflow-status metadata is recorded here. Live acceptance remains #923 work.

[jeffhuber]

Roadmap mapping update: #1027 is the single release-prep PR boundary for the immutable 1.5.0 candidate and its fresh-install, explicit Slack opt-in, v1.4.2 upgrade, disable/uninstall, rollback, package-inventory, and release-text rehearsals. It follows #1025/#1024, feeds #918 private acceptance and #920 capped canaries, and leaves tag/package publication to #923 after those gates pass.