Correct EventModeling dependency provenance and qualify its kernel image pairing #674

Activity

1. woksin

   self-assigned this

   on Nov 2, 2026
2. cratis-direct

   added the

   Task

   issue type on Nov 2, 2026
3. woksin commented on Nov 2, 2026

   

   woksin

   on Nov 2, 2026

   CollaboratorAuthor

   More actions

   Implementation design (rev 1)

   Base: f3234f8 (main, 2026-11-02)
   Status: proposed
   Size / release intent: S · patch
   Reviewed: independent Claude reviewer — README/central/image discrepancies confirmed; no runtime-failure claim

   Problem and root cause

   FromMartenAndWolverine README duplicates stale9.45/6.45 versions instead of central9.49/6.49. ArcRuntimeView similarly describes22.50.4/19.31.10 while central selects22.156.4/19.115.3; its server really remains19.31.10-development.

   Approach

   Make package provenance truthful and make the server pairing explicit. Prefer links to central declarations over duplicated version literals. Do not infer incompatible behavior merely from different version numbers.

   Steps

   1. Drift-check both READMEs, central props, project references and image.
   2. Correct package statements, separating application, tool and server versions.
   3. Either align the server image to a verified compatible release and prove its walkthrough, or explicitly document the retained pairing as unqualified until evidence exists.
   4. Keep intentionally pinned CLI/Screenplay tools unless a separately justified migration is required.

   Files to touch

   EventModeling/FromMartenAndWolverine/README.md, EventModeling/ArcRuntimeView/README.md; ArcRuntimeView Compose only if intentionally qualifying a new image.

   Public API, compatibility, migration

   No intended API change. Any image change is a separate compatibility-affecting part of the same issue, not an incidental prose edit.

   Performance

   None for documentation. Use bounded acceptance waits if image changes.

   Specs to add (red first)

   Check documented provenance against central declarations. An image change requires the relevant startup/event-model walkthrough, not only compilation.

   Gate (exact commands from the repo's CI)

   Documentation-only correction: static comparison to props/project/image and catalog validation yarn samples:validate where applicable. If image/runtime behavior changes, existing build gates include:

   dotnet restore Samples.slnx
   dotnet build Samples.slnx --configuration Debug --no-restore
   dotnet restore Samples.slnx -p:Configuration=Release
   dotnet build Samples.slnx --configuration Release --no-restore -p:CratisProxiesOutputPath=

   These commands do not alone prove the walkthrough against the image; add bounded targeted acceptance when changing the pair. No commands executed for this design.

   Done when

   • Both READMEs accurately distinguish package/tool/server provenance.
   • Server pairing is qualified or explicitly labeled unqualified, not silently assumed.
   • No dependency downgrade or unjustified tool upgrade accompanies prose repair.

   Risks and open questions

   Image publication and runtime compatibility remain unverified; do not label the existing pair broken without reproduction.

   Out of scope

   Generated Shop refresh, broad dependency updates and historical delivery issues.