Roadmap: Devin, Graphify, Board clarity, and Slack session ingress

[jeffhuber]

Near-term delivery roadmap after v1.3.1

Outcome

Deliver four independently releasable capabilities in this order:

1. v1.4.0 — Devin peer support: provider-neutral session lifecycle, hosted and local builder use, private context delivery, recovery, and informational exact-head review.
2. v1.4.1 — Graphify repository context: adopt or defer from a bounded spike, then ship a revision-bound local provider only if it clears the evidence bar.
3. v1.4.2 — Board clarity and session visibility: a work-first local Board backed by provider-neutral session/work/run observations, trustworthy freshness and evidence semantics, and local/hosted qualification.
4. v1.5.0 — Slack session ingress: start and supervise sessions from Slack through the provider-neutral lifecycle, initially using hosted Devin.

The default first-run setup remains Claude + Codex. Devin, Coworker, Graphify, and Slack remain explicit optional selections.

Execution order

• Maintain one feature epic per capability.
• Finish and release Devin v1.4.0 before Graphify or Board release work.
• Release Graphify v1.4.1, or record an explicit evidence-backed defer decision, before Board v1.4.2.
• Deliver Board v1.4.2 through two coordinated tracks: presentation and provider-neutral session/events. Reuse Sessions: provider-neutral remote lifecycle and recovery #906, coordinate the minimum discovery from Sessions: discover the current local brief and lease from a checkout #935, and leave Slack/cloud mappings in Slack: metadata-only Board and CodeMower.com lifecycle telemetry #921.
• Slack contract, OAuth, inbox, interaction, bridge, setup, and documentation work may proceed when their own dependencies are ready. Board readiness gates only Slack's end-to-end canary and final lifecycle/release acceptance in Release: qualify and publish Slack session ingress in v1.5.0 #923.
• Finish and qualify Board v1.4.2 before the Slack v1.5.0 canary/final release gate.

Development is not fully serial: fixture-driven Board presentation and its frozen local observation contract may proceed in separate single-writer tracks while earlier releases finish, but no tag or release may change the order above.

Delivery contract

Every implementation child has exactly one independently reviewable PR, one named Code Mower builder, an independent peer audit against the exact current head, focused tests, normal CI, and the Code Mower gate. P0/P1/P2 findings are fixed before merge. Epics carry live checklists, scorecards, acceptance evidence, release evidence, Board status, and CodeMower.com upload evidence. There is no umbrella implementation PR.

No capability gains tracker-write or merge authority by being selectable. Reviewer promotion remains evidence-based. Paid or externally mutating operations require explicit application, bounded spend, and no automatic uncertain retry.

Privacy and product boundaries

• Repository source, diffs, task prose, Slack messages, Graphify graph data, Coworker content, prompts, transcripts, credentials, raw provider output, and personal paths remain out of public issues and CodeMower.com.
• Cloud reporting remains allowlisted metadata only. Board v1.4.2 adds no cloud fields; paired Slack/hosted schema changes remain Slack: metadata-only Board and CodeMower.com lifecycle telemetry #921.
• Graphify starts local, deterministic, explicit-refresh, and code-only.
• Slack is an ingress/conversation transport, not a participant or orchestrator.
• Board is a local read model, not another workflow engine; opening it never dispatches, retries, mutates provider state, or changes lease authority.
• The selected agent remains the orchestrator; the calling tool is implicit when no override is supplied.

Roadmap scorecard

Capability	Release	Epic	State	Acceptance evidence	Release evidence	Cloud ingestion
Devin peer support	v1.4.0	#901	released	completed epic scorecard and exact Claude + Codex + hosted Devin cold-install campaign	GitHub Release v1.4.0, matching PyPI/GitHub artifacts, local install, and three upgraded Boards	four metadata-only events accepted; zero reports
Graphify context	v1.4.1	#902	bounded delivery	tracked in epic	pending	pending
Board clarity/session visibility	v1.4.2	#945	planned; two tracks	fixtures + local/hosted canaries	blocked by #912/#915	existing fields only
Slack ingress	v1.5.0	#903	contract/ingress underway	private E2E canary blocked by #952	pending	#921

Dependency boundary

• Epic: Board clarity and provider-neutral session visibility for v1.4.2 #945 is blocked by the Devin release Release: publish and qualify Code Mower v1.4.0 with Devin peer support #912 and Graphify release Release: qualify and publish optional Graphify context in v1.4.1 #915 for its v1.4.2 release, while contract/fixture implementation may proceed under its own child dependencies.
• Epic: Board clarity and provider-neutral session visibility for v1.4.2 #945 reuses merged Sessions: provider-neutral remote lifecycle and recovery #906 and coordinates Sessions: discover the current local brief and lease from a checkout #935; neither is duplicated inside the Board epic.
• Slack: metadata-only Board and CodeMower.com lifecycle telemetry #921 owns Slack-specific Board mapping and every new cloud/hosted schema field. Board v1.4.2 provides the provider-neutral local view it consumes.
• Release: publish and qualify Board clarity v1.4.2 #952 is the only Board release dependency for Slack Release: qualify and publish Slack session ingress in v1.5.0 #923. No earlier Slack child becomes blocked merely because Board work is open.

Definition of done

• Each epic satisfies its own acceptance criteria and closes all required child issues.
• Default installation and no-provider operation remain simple and pass fresh-install rehearsal.
• Optional integration setup clearly separates participants from context providers and interaction channels.
• Published artifacts, GitHub release, package-index installation, post-release campaign, local Board, and CodeMower.com metadata ingestion are verified for each release.
• Board v1.4.2 tells the truth about freshness, missing evidence, next actor, head-bound review/gate state, and local versus hosted activity before Slack's final canary relies on it.

Feature epics

• Epic: Devin peer participant and lifecycle support for v1.4.0 #901 — Devin peer support for v1.4.0
• Epic: Graphify local repository context for v1.4.1 #902 — Graphify repository context for v1.4.1
• Epic: Board clarity and provider-neutral session visibility for v1.4.2 #945 — Board clarity and provider-neutral session visibility for v1.4.2
• Epic: Slack session ingress and supervision for v1.5.0 #903 — Slack session ingress for v1.5.0

[jeffhuber]

Execution started

• Local Board: http://127.0.0.1:5332/
• CodeMower.com dashboard: https://codemower.com/dashboard
• Metadata upload evidence: https://github.com/codemower-ai/code-mower/actions/runs/34684055961
• Active Devin work: Devin: capability model and safe reviewer posture #904, Codex builder
• Active Graphify spike: Context: evaluate official Graphify as a local repository provider for v1.4.1 #876, Claude builder
• Slack contract: Slack: freeze command, identity, lifecycle, privacy, and event contracts #916, planned against the stabilized remote-session lifecycle

The dispatcher selected both active issues in dry-run before applying dispatch. Both builder units use isolated lane checkouts and the normal single-writer contract. Raw task/provider/context/graph content is not part of the cloud upload.

[jeffhuber]

A metadata-only hosted Ubuntu v1.3.1 adoption rehearsal produced three nonblocking follow-ups. These are deliberately outside the Devin v1.4.0 critical path:

• Doctor: scope release-campaign auth readiness to campaign intent on headless hosts #953 — scope release-campaign authentication readiness to actual campaign intent, including truthful headless-host guidance (P2)
• Init: make documented --builders selection work from a fresh repository #954 — make the documented init --builders ... cold-start path work consistently (P2)
• Adoption polish: report effective review authority and superseded Devin bridge drift #955 — render effective reviewer authority, flag superseded Devin bridge drift, and reduce posture noise (P3)

Each should ship as an independently reviewed PR after #912. No P0/P1 issue was reported; install, upgrade, Board, lane status, productivity, and session start --host devin all worked.

[jeffhuber]

Roadmap milestone: Devin v1.4.0 released

The first roadmap capability is complete. Devin peer support shipped in Code Mower v1.4.0, with matching package artifacts, local installation, an exact three-provider cold-install campaign, three upgraded Boards, and accepted metadata-only cloud evidence.

This clears the release-order dependency for Graphify and the later Board and Slack work. The roadmap remains open for those capabilities.