You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by da...@apache.org on 2026/08/06 08:07:03 UTC

(causeway) 14/15: CAUSEWAY-3910: update reconciliation ledger for P2

This is an automated email from the ASF dual-hosted git repository.

danhaywood pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/causeway.git

commit 43e42014ab054ffeacbd5be3815010f1707a947a
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Thu Aug 6 08:33:26 2026 +0100

    CAUSEWAY-3910: update reconciliation ledger for P2
---
 openspec/reconciliation/maintenance-branch/ledger.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/openspec/reconciliation/maintenance-branch/ledger.md b/openspec/reconciliation/maintenance-branch/ledger.md
index c4e7a266545..04a3c94f90a 100644
--- a/openspec/reconciliation/maintenance-branch/ledger.md
+++ b/openspec/reconciliation/maintenance-branch/ledger.md
@@ -38,7 +38,7 @@
 | CAUSEWAY-4010, 4039 | M1, M2 | Bookmark-only remapping SPI, execution-copy remapping, atomic result observation, and conditional in-memory listener reconciled | Supersede | Completed by `reconcile-command-replay-mapping` |
 | Later maintenance mapping work | M3 | Persistent mapping contracts, listener, management UI, and Jakarta Persistence adapter reconciled; the removed commandlog JDO adapter is not applicable on Causeway 4 | Supersede | Completed by `reconcile-persistent-replay-mapping` |
 | Maintenance consolidated replayable-command specs | P1 | Replay-useful eligibility, result presence, bookmark participants, actual mappings, object links, identity mementos, layouts, and adjacent navigation reconciled | Supersede | Completed by `reconcile-replayable-command-projection` |
-| Maintenance consolidated manager specs | P2 | Separate export and replay managers exist | Supersede | `reconcile-unified-command-manager` |
+| Maintenance consolidated manager specs | P2 | Unified baseline/limit manager, four review collections, replay-state boundary, primary menu entry, and legacy-manager compatibility shims reconciled | Supersede | Completed by `reconcile-unified-command-manager` |
 | CAUSEWAY-4034 and later maintenance specs | R1 | `RefData` and command replay reference-data SPI absent | Adapt | `reconcile-command-reference-data` |
 | Later maintenance export specs | R2 | Baseline-bounded participant reachability validator absent | Supersede | `reconcile-command-export-reachability` |
 | CAUSEWAY-4010 and later export specs | E1 | Legacy YAML export/import baseline exists | Supersede | `reconcile-command-export-import` |
@@ -56,6 +56,7 @@
 | `reconcile-command-replay-mapping` | D2, M1, M2 | `openspec/specs/command-execution-advisor-policy/spec.md`; `openspec/specs/command-replay-mapping/spec.md` | `openspec/changes/archive/2026-08-04-reconcile-command-replay-mapping/` | Planning `b9412ee98a7`; implementation `6b4ab64d193`; archive `74ba8b40c0a`; focused and affected aggregate Maven tests passed |
 | `reconcile-persistent-replay-mapping` | M3 | `openspec/specs/persistent-command-replay-mapping/spec.md` | `openspec/changes/archive/2026-08-05-reconcile-persistent-replay-mapping/` | Planning `d88eb297388`; implementation `1990363924f`; archive `d95ee405f68`; focused and affected aggregate Maven tests passed |
 | `reconcile-replayable-command-projection` | P1 | `openspec/specs/replayable-command-projection/spec.md` | `openspec/changes/archive/2026-08-06-reconcile-replayable-command-projection/` | Planning `2e65bb795a7`; implementation `4bc1b204484`; archive `30b53793cf2`; focused and full commandlog reactor Maven tests plus IDE inspection passed |
+| `reconcile-unified-command-manager` | P2 | `openspec/specs/unified-command-manager/spec.md`; `openspec/specs/replayable-command-projection/spec.md` | `openspec/changes/archive/2026-08-06-reconcile-unified-command-manager/` | Planning `3ee2f7875cb`; implementation `5b95dd3b4a9`; archive `6811dfc6b1f`; focused commandlog applib and JPA Maven verification plus strict OpenSpec validation passed |
 
 ## Resolved questions
 
@@ -69,13 +70,13 @@
 | Replay mapping policy remains entirely in commandlog applib through a bookmark-only listener SPI and result-remapping service; core runtime services implement only general command-execution advisor policy. | D2, M1, M2 | `reconcile-command-replay-mapping/design.md` in the archived change, `ResultRemappingServiceTest`, and `CommandExecutorInteractionAdvisorTest` |
 | Persistent replay-result mappings use the Causeway 4 commandlog JPA module only; the commandlog JDO adapter was deliberately removed and is not restored. | M3 | `reconcile-persistent-replay-mapping/design.md`, `CommandReplayResultMapping_IntegTest`, and the Causeway 4 commandlog module inventory |
 | Replayable-command participants remain a derived read model; actual bookmarks come through the mapping SPI, result mappings remain gated until replay succeeds, and pending-or-failed imported work bypasses general eligibility. | P1 | `reconcile-replayable-command-projection/design.md`, `ReplayableCommandParticipantTest`, and `CommandManagerEligibilityTest` |
+| The unified manager is the forward path with a baseline/limit memento; both legacy manager logical types and timestamp-only mementos remain loadable compatibility shims, their standard launchers are hidden, and stored bookmarks are not rewritten. | P2 | `reconcile-unified-command-manager/design.md`, `CommandManagerCompatibilityTest`, and `CommandLogMenuTest` |
 
 ## Open questions
 
 | Question | Affected nodes | Resolution point |
 |---|---|---|
 | Can the Causeway 4 Spring context become unavailable during `ServiceRegistryDefault.select()` in metamodel disposal? | CAUSEWAY-4002 | Separate lifecycle investigation before core work is declared complete |
-| How will migration from separate `CommandExportManager` and `CommandReplayManager` view-model mementos be handled? | P2 | Unified-manager design |
 | Which services count as export roots in the Causeway 4 service registry and logical-type model? | R2 | Reachability design |
 | Which persistence operations are required to retimestamp commands safely under JPA and JDO? | W1 | Manager-workflow design |