[JSdotNet]

Summary

The roadmap did not follow its owner from one PC to another. Tasks sync, but the plan lives only in the local roadmap_plan row of backlog.db, and nothing in sync reads it. ADR 0005 had left open whether the plan should replicate at all. This PR records the decision the owner made on 2026-09-29 as local ADR 0018. The code that implements it comes in a follow-up PR.

• The plan replicates as one whole roadmap-plan document on the existing /tasks feed, the same way captures ride it (ADR 0009). The plan JSON goes in ContentMd unchanged. The newest updated_at wins.
• The pace replicates too, as a second planning-pace document. Keeping it separate means a pace change on one PC and a plan edit on another don't overwrite each other.
• The sync service, its routes and its containers do not change, so this works against the service deployed today.
• A device that has never saved a plan or pace sends nothing, so it never overwrites another device's.

Changes

• .devbook/arc42/adr/0018-roadmap-plan-and-pace-ride-the-task-feed.md: new ADR, accepted 2026-09-29. It includes a Verification section with 9 test cases for the implementing change.
• ADR 0005: its roadmap-plan open question is answered here (dated amendment).
• ADR 0013: ruling 4 no longer keeps the pace per-device (dated amendment).
• 08-crosscutting-concepts.md, 09-architecture-decisions.md, adr/README.md: index entries and the Storage and Sync section.
• .devbook/domain/roadmap/context.md: the pace now follows its owner across paired devices; the working week stays local.
• .devbook/domain/roadmap/features.md: new Syncing the plan between devices chapter, with the sub-feature Carrying the pace with the person.

Testing

Documentation only; there is nothing to run.

• node .devbook/_tools/devbook-meta/build.mjs --check: 0 errors.
• node tools/devbook/check-metadata.mjs: 0 blocking. The 339 advisories were all there before this change.

Related

There is no issue; the user reported it in a session. This PR refs local ADR 0005, ADR 0009, ADR 0011 and ADR 0013.

Checklist

• Scope is focused and excludes unrelated changes
• Documentation or instruction files were updated when governance or behavior changed
• Running Aspire instances for this checkout were stopped before PR creation (none were started)
• Follow-up work is captured when the implementation is intentionally partial (the implementing flow-code run follows on this branch's successor)
• Issues this PR closes are linked with a closing keyword, or there are none

🤖 Generated with Claude Code