eric/distributor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

Add takeover backend regressions and close roadmap

Browse Source
This commit is contained in:
Eric Rakestraw
2026-06-18 15:40:24 +00:00
parent eba65018be
commit 8b0ce4d134
3 changed files with 126 additions and 255 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/roadmap/implementation.md
View File

@@ -1,14 +1,14 @@
# Managed Destination Takeover Implementation Roadmap
This is the active staged implementation plan for
`docs/roadmap/takeover.md`. The feature roadmap defines the target policy and
end-state semantics; this document defines the implementation sequence for an
LLM coding agent to follow stage by stage.
This is the completed staged implementation plan for the takeover feature. The
detailed feature roadmap was removed after implementation; current behavior is
documented outside `docs/roadmap/`. This document records the implementation
sequence used by LLM coding agents stage by stage.
Future behavior must remain under `docs/roadmap/` until each stage is
implemented. Preparatory internal stages should not update user-facing current
docs. Current-behavior docs should be updated when takeover behavior is wired
for operator-facing use.
Future behavior must remain under `docs/roadmap/` until implemented.
Preparatory internal stages should not update user-facing current docs.
Current-behavior docs should be updated when behavior is wired for
operator-facing use.
## Current Baseline
@@ -55,7 +55,8 @@ changing publish behavior.
Source roadmap reference:
- `docs/roadmap/takeover.md`: Configuration, Policy Semantics, Safety Rules.
- Completed takeover feature roadmap: Configuration, Policy Semantics, Safety
Rules.
Implementation scope:
@@ -96,7 +97,7 @@ takeover eligibility without parsing human-readable reason strings.
Source roadmap reference:
- `docs/roadmap/takeover.md`: Policy Semantics, Relationship To Existing
- Completed takeover feature roadmap: Policy Semantics, Relationship To Existing
Policies.
Implementation scope:
@@ -140,7 +141,7 @@ Goal: implement `takeover.mode` for single-owner destination state.
Source roadmap reference:
- `docs/roadmap/takeover.md`: Policy Semantics, Publish Planning, Destination
- Completed takeover feature roadmap: Policy Semantics, Publish Planning, Destination
State Results, Safety Rules.
Implementation scope:
@@ -207,7 +208,7 @@ conflicts.
Source roadmap reference:
- `docs/roadmap/takeover.md`: Policy Semantics, Publish Planning, Destination
- Completed takeover feature roadmap: Policy Semantics, Publish Planning, Destination
State Results, Safety Rules.
Implementation scope:
@@ -262,7 +263,7 @@ feature.
Source roadmap reference:
- `docs/roadmap/takeover.md`: Documentation Impact, Publish Planning,
- Completed takeover feature roadmap: Documentation Impact, Publish Planning,
Relationship To Existing Policies.
Implementation scope:
@@ -313,7 +314,7 @@ after implementation.
Source roadmap reference:
- `docs/roadmap/takeover.md`: Goals, Non-Goals, Safety Rules.
- Completed takeover feature roadmap: Goals, Non-Goals, Safety Rules.
Implementation scope:
@@ -328,9 +329,8 @@ Implementation scope:
- Add tests for archive-style `preserve_relative` destinations using
`takeover.mode: same_source` where strict source identity is desired.
- Run final consistency searches.
- Once behavior and docs are complete, either remove `docs/roadmap/takeover.md`
or reduce it to future-only material according to the documentation policy.
If no future takeover work remains, remove the roadmap file.
- Remove the completed detailed takeover roadmap when no future takeover work
remains.
Tests: