Reconcile canonical roadmap with merged work and retire superseded Android Auto experiment #39
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Classification
Documentation-only roadmap reconciliation. This expands the original secondary-slot bookkeeping task because the same audit found the canonical roadmap now carries several factual state mismatches.
Problem
docs/roadmap.mdis BookWave's sole sequencing authority, but its current-state preface/committed chain has fallen behind GitHub history:docs/latest-stable-upgrade-plan.md.Separately, BW-AUTO-03 still says to measure Android Auto secondary action slots, even though GitHub #78 already settled that against Media3 1.11.0 and real-device evidence:
SLOT_BACK_SECONDARY/SLOT_FORWARD_SECONDARYare discarded by the legacy conversion before the projected host sees them.Leaving factual prerequisites stale undermines the point of having one canonical roadmap and can send fresh workers toward work that is already complete or no longer blocked.
Scope
Documentation only:
docs/latest-stable-upgrade-plan.mdat an appropriate maintenance position without letting dependency novelty outrank correctness work automatically;docs/android-auto-player-opportunities.mdexplaining why secondary slots failed;Explicitly out of scope
Current-state rule
At implementation time, refresh actual
main, open PRs, recently merged PRs and relevant issue states before editing. Do not trust the snapshots above if GitHub has moved meanwhile.Acceptance
docs/latest-stable-upgrade-plan.mdremains the detailed child plan.Relationships
docs/latest-stable-upgrade-plan.mddocs/android-auto-player-opportunities.md