docs: July 2026 roadmap refresh

[ascerra]

Summary

Restructure the roadmap to reflect the July 1, 2026 team planning session. This replaces the June workstream structure with nine new categories prioritized by team dot-voting.

Key changes:

• At-a-glance table — visual overview at the top showing all categories with priority rank, focus area, and horizon (Now/Next/Later). Requested by the team for people who don't have time to read the full document.
• June 2026 (done) — new section documenting what shipped in June (90+ PRs merged, 150+ issues closed), replacing the stale Foundation section at the top. Covers agent registration (ADR 0058), unified env var delivery (ADR 0055), PR-based scaffold delivery, VitePress docs migration, dispatch hardening, standalone runtime progress, and more.
• Nine July categories — ordered by planning session dot-vote priority:
  1. BYOA (highest priority)
  2. Infrastructure (consolidates June's Agent Capabilities, Upgrades & Versioning, and New Forges)
  3. Observability (new — cost measurement, telemetry, hidden agent failures)
  4. Testing (behavior tests, evals, stage tests)
  5. External Partnerships (combines Docs & Public Alignment with partnership tracking)
  6. JIRA (JIRA-specific workflows, split from broader Agent Data Access)
  7. mint (extract, harden, and operationalize the mint service)
  8. Agent Data Access (data connectors, multi-repo context, credential infrastructure)
  9. Exploration (persistent agent memories, auto-merge — no votes, tracked for future)
• Foundation moved to bottom — historical context preserved but no longer dominates the top of the document
• All example bullets link to issues — no unlinked work items in "Examples of work" sections

Category mapping (June → July):

June	July
BYOA & Customizability	BYOA
Agent Capabilities & Runtime	Infrastructure (merged)
Testing, Staging Infra & Evals	Testing
Upgrades & Versioning	Infrastructure (merged)
Docs & Public Alignment	External Partnerships
New Forges	Infrastructure (merged)
Jira Integration & Refinement	JIRA + Agent Data Access (split)
(new)	Observability
(new)	mint
(new)	Exploration

Context

• Planning session: July 1, 2026 (Miro board + dot-voting)
• Companion PR for workstream-categories.md update in .fullsend repo forthcoming
• Post this PR: advertise in user forum and invite feedback per planning session decision

Test plan

• Verify all issue/PR links resolve correctly
• Confirm at-a-glance table row order matches document section order
• Review June accomplishments for accuracy and completeness
• Docs site renders correctly after merge

Made with Cursor

[qodo-code-review]

PR Summary by Qodo

Refresh roadmap structure and priorities for July 2026 planning

📝 Documentation 🕐 20-40 Minutes

AI Description

• Add an at-a-glance priority table linking to each roadmap category
• Document June 2026 shipped outcomes and reposition Foundation as historical context
• Replace June workstreams with nine July categories ordered by dot-vote priority

Diagram

graph TD
  A["docs/roadmap.md"] --> B["At-a-glance table"] --> C["June 2026 (done)"] --> D["Now: 9 priority categories"] --> E["Next: Exploration + Cross-forge"] --> F["Later: themes"] --> G["Foundation (Apr–May)"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Split roadmap categories into separate files (include/links)

• ➕ Smaller diffs per category change; less merge conflict risk
• ➕ Easier ownership: CODEOWNERS per category area
• ➖ Readers lose single-scroll context unless site tooling supports includes well
• ➖ Requires additional nav/IA decisions for the docs site

2. Model the at-a-glance table as structured data (YAML/JSON) and generate markdown

• ➕ Prevents drift between table order and section order
• ➕ Enables reuse across docs site (e.g., rendered cards, filters)
• ➖ Adds a generation step and tooling/docs complexity
• ➖ Harder to edit directly in GitHub UI for quick updates

Recommendation: The PR’s single-document restructure is appropriate for a roadmap refresh and keeps consumption simple. If the team expects frequent re-ordering or many contributors editing categories in parallel, consider splitting categories into separate files next; if drift between summary/table and sections becomes an issue, move the table to generated content from structured data.

Files changed (1) +142 / -97

Documentation (1) +142 / -97

roadmap.mdRebuild roadmap around July 2026 priorities and add June accomplishments +142/-97

Rebuild roadmap around July 2026 priorities and add June accomplishments

• Reorders the roadmap to start with a new at-a-glance priority table and a June 2026 accomplishments section. Replaces the previous June workstream layout with nine July categories ordered by dot-vote priority, adds/relocates several Next/Later subsections, and moves the Foundation context to the bottom while ensuring examples link to tracked issues/PRs.

docs/roadmap.md

[github-actions]

Site preview

Preview: https://44081ab0-site.fullsend-ai.workers.dev

Commit: 2a3d0a5ad8266736708a00e15f7e2be0a3c188de

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:23 PM UTC · Completed 3:37 PM UTC
Commit: 2a3d0a5 · View workflow run →

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Review

Findings

Medium

• [internal consistency] docs/roadmap.md — PRs feat(config): add agent registration schema (ADR 0058 Phase 1) #2768, feat(run): add runtime agent resolution from config (ADR 0058 Phase 3) #2769, and feat(cli): add fullsend agent subcommand (ADR 0058 Phase 2) #2770 are listed as delivered work in the "June 2026 (done)" section ("Agent registration and BYOA foundations — ADR 0058 landed in three phases") and simultaneously as forward-looking work under the "BYOA" Now section ("Agent registration schema and CLI subcommand"). Listing completed PRs as examples of work that "could move this forward" implies they are not yet done, contradicting the June summary. Consider removing the three PRs from the BYOA section or rewording to clarify these are foundational work that landed in June and will be extended.

• [stale reference] docs/problems/platform-nativeness.md:134 — References "Phase 4 (domain specificity in the roadmap)" and links to ../roadmap.md. The restructured roadmap removes all phase-based terminology and has no "Phase 4" or "domain specificity" section. Readers following this link will find no matching content. Update the reference to point to the appropriate roadmap section or remove the phase terminology.

---

Labels: PR modifies only docs/roadmap.md — a user-facing documentation restructure.

[dhshah13]

Is GitLab integration still a priority? Or is it going to be in next month?

[ascerra]

Is GitLab integration still a priority? Or is it going to be in next month?

It is currently scoped as "next" here

So yes, its not being deferred to "later" but we did identify a lot of work that takes priority over it. Next month is a good estimate IMO.

[ggallen]

Is GitLab integration still a priority? Or is it going to be in next month?

@dhshah13, the ADR is up for review in #2583. Please review it and either add comments or approve.

As soon as this is merged I plan to start implementing around my other tasks, so I am hoping to make good progress on it this month. You approval would help get the ADR completed.

[dhshah13]

@ggallen I'll finish the review today and post my comments.