#2865 Tracking: test baseline required before the datastore refactor (commit-log design)

What this is

This issue tracks the test baseline that has to be in place before any code for the datastore refactor lands. The design proposal is design/enablers/datastore-commit-log.md on the datastore-rework branch; it is not merged. Every issue listed here is self-contained and can be picked up by an agent with no other context.

The refactor, in one paragraph.

• Today repositories write files locally and call markDirty, and a sync service (in the S3/GCS extensions) pushes and pulls files, _index shards and _meta.json.
• The refactor moves to a commit log: repositories commit through a unit of work, content becomes immutable chunks, and in team mode the CLI forwards commits to swamp serve.
• It lands on main in phases:
  • Phase 1: a UnitOfWork port with a legacy adapter.
  • Phase 2: use cases own the unit of work.
  • Phase 3: a v3 engine, dormant behind opt-in.
  • Phase 4: solo mode with SQLite + Litestream.
  • Phase 5: serve leader, commit feed, model leases.
  • Phase 6: migrate/claim.
  • Phase 7: default flip.
  • Phase 8: MongoDB.
  • Phase 9: remove v2.
• Phases 1-2 must change no behaviour. These tests are what prove that.

Gate: ready to start Phase 1

Every issue in waves 1-3 below is merged and green in CI. A test that exposes a bug today is committed pinned or ignored, with a link to a filed bug, not left out.

Dependency graph

An issue can start once everything it is blocked by has merged. Within a wave, issues are independent and can run in parallel.

swamp repo (swamp-club)                  swamp-uat
-----------------------                  ---------
#2854 in-memory remote fake              #481 filesystem backend + v2-only tag
  |-> #2855 every changed file marked      |-> #483 CI: backend list on PRs ------+
  |-> #2857 two-repo propagation           |                                      |
  |-> #2859 remote failures                |    #482 helpers                      |
  |-> #2860 use-case marks and pushes      |      |                               |
  |     '-> #2863 pollers (deferred)       +------+-> #484 fix tests that         |
  '-> #2861 conformance suite                     |        can't fail             |
                                                  |-> #485 deletes across clones  |
#2856 fitness ratchets       (independent)        |-> #487 file writers           |
#2858 fs catalog staleness   (independent)        |-> #490 managedConfig          |
#2862 property test          (independent)        '-> #492 every command syncs    |
                                                                                  |
#2864 CI: run swamp-uat suite on swamp PRs  <------- blocked by swamp-uat#483 ----+

Soft link (coordinate, not blocking): swamp-uat#485 on the filesystem backend is expected to hit the stale-catalog bug that swamp-club#2858 characterises. Land #2858 first, or at the same time, so #485 can pin those cases with an ignore pointing at it.

Waves

Critical paths:

• swamp-club#2854 → the five wave-2 swamp issues.
• swamp-uat #481 + #482 → the five wave-2 test issues.
• swamp-uat#481 → #483 → swamp-club#2864.

Every issue: what it is, and what it is blocked by and blocks

In scope now: swamp repo (unit, integration, fitness, conformance)

In scope now: swamp-uat (end-to-end, compiled binary)

Deferred: needed before a later phase, not before Phase 1

Behaviour gaps the audit found (to be pinned by the tests above, not fixed by them)

• Unmarked writes and deletes in unified_data_repository.ts (delete(version) does not mark the latest rewrite or the name dir; advanceLatestMarkers / rollbackVersions) and in the YAML repos' rename and pathsToTry cleanups. See swamp-club#2855.
• swamp model evaluate / workflow evaluate construct evaluated repositories without a mark hook (src/libswamp/models/evaluate.ts:146, src/libswamp/workflows/evaluate.ts:174). See swamp-club#2856.
• CLI workflow approve / reject / cancel never push, while serve does. See swamp-club#2860.
• Serve nodes or clones sharing a filesystem datastore never refresh their catalog. See swamp-club#2858.
• Serve pollers treat a void pull result inconsistently (Config invalidates; Access and Runtime do not). See swamp-club#2863.

Each can be filed as its own bug when its test pins it. They are not fixed as part of this baseline.