docs: add ROADMAP.md - #8
Merged
Merged
Conversation
Snapshot of what's likely, what's maybe, what's explicitly out of scope. Captures the queue we accumulated during the v0.3 audit cycle and the v0.3.7 -> v0.4.0 CI / docs sweep without overpromising. Likely (v0.4.x) Dependabot config, CodeQL workflow, coverage upload, issue triage labels. All single-PR scope, low risk. Maybe (v0.5.x) Claude Code hooks bundle, slash-command skills pack, `agent-inbox install` CLI subcommand, PyPI publish, reply-thread visualization in the UI, live updates via Wails events. Out of scope Cross-host coordination, multi-tenant auth, mobile companion, general-purpose message queue. Calling these out so contributors don't propose them and so users have a clear "this is a different project" answer when their need crosses the line. Not dated. Snapshots intent, not commitments. Items in Likely move without a roadmap update; Maybe items get an issue first.
Patton's release-readiness pass on v0.4.0 caught two stale spots from
the brief expansion:
Line 54 (file-tree comment) said "Reference 6-agent set (operator
+ 5 roles)" — pre-expansion count. Updated to "Reference 7-role
bundle (operator + 6 collaborators)".
Lines 340-342 had the old pointer paragraph claiming six agents
and listing the pre-expansion set, four lines after the new
seven-role pointer at 329-334. The old paragraph never got
removed when v0.4.0's pointer landed. Deleted entirely; the new
pointer at 329-334 supersedes.
Doc-only, no code, no version bump. Folding into PR #8 (the ROADMAP
PR, also doc-only).
Bundles two doc-only changes for a focused release tag:
- ROADMAP.md: snapshot of likely / maybe / out-of-scope work
- README.md: removed stale 6-agent pointer paragraph (Patton's
release-readiness pass) + updated file-tree comment to reflect
the v0.4.0 brief expansion
No code, no tests changed. Bumping rather than amending v0.4.0
because the cleanup is small but real — first-time README readers
were hitting two contradictory paragraphs about brief count.
This is the tag the first public release announcement will point at.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snapshot of likely / maybe / out-of-scope work. Single doc file, no code. Catches the queue from the v0.3 → v0.4 cycle in writing so we don't lose it.