Track atomic source recovery under the Screenplay semantic model

[woksin]

Purpose

Cross-repository index for source-to-Screenplay recovery and realization under the Screenplay executable-model architecture.

Screenplay is the portable semantic authority. Generation recovers evidence and proposes portable meaning. Critter Stack owns Marten/Wolverine source evidence only. Framework details remain realization/provenance unless they establish portable behavior.

Completed foundation

• Generation 0.8.0 deterministic, typed fail-closed composition.
• Critter Stack 0.19.0 bounded Marten/Wolverine/Vogen evidence.
• CLI 2.15.2 explicit offline provider workflow and installed-tool verification.
• Generation Add pinned canonical Critter Stack acceptance fixtures #5, CLI #87, and broad Critter Complete Marten document and projection analysis #3/Complete Wolverine workflow and middleware analysis #4/Complete the supported Preview entry path #17 closed.
• Screenplay architecture rejects Saga syntax and technical runtime vocabulary as language backlog.

Active dependency order

1. Generation Fix Wolverine return consequence classification #21 — stable source identity/display policy and host adoption.
2. Critter Complete bounded authored Wolverine saga and correlation evidence #50 / draft PR Add bounded Wolverine saga evidence #49 — bounded Saga characterization as report-only evidence; no Saga lowering.
3. Screenplay #135/#136 — executable semantic model and execution plan boundary.
4. Generation Support configured Marten projection lifecycles #18 — authored-source helpers.
5. Generation Discover direct Wolverine bus consequences #23 — descriptors, probes, frozen admission and dispositions.
6. Generation Record the v0.3.0 release status #19 — granular facts and derivation aligned with the semantic model.
7. Generation Update handover for CLI provenance release #20 — neutral validation semantics.
8. Generation Compose Vogen concepts into Critter Stack generation #25 — neutral executable specification facts.
9. Generation Document Vogen concept discovery architecture #26 — shared source-structure/module placement.
10. Critter Expose atomic Marten, Wolverine, and integration adapters #44 — atomic Marten, Wolverine and integration adapters.
11. CLI #95 — static atomic roster and selection-only profiles.
12. Arc #2601/#2600 — neutral shadow export and parity.
13. Generation Discover pure Wolverine automations #24 — deterministic realization/provenance report.

Product-gated residual

• Critter Recognize bounded Marten query entry points outside Wolverine HTTP handlers #51 — non-Wolverine Marten query entry points, only with a pinned product fixture.

Transport topology and broad upstream API enumeration are not active roadmap work.

Invariants

• Adapters emit immutable neutral facts/evidence/diagnostics, never Screenplay syntax/text.
• Authored source originates semantics; generated source only corroborates.
• Technical Document/Handler/Endpoint/Message/Saga observations do not automatically become model nodes.
• Vogen remains an independent cross-cutting adapter and executes at most once.
• One fixed snapshot, one derivation phase, one resolution, one Screenplay semantic construction.
• Unsupported, ambiguous, or conflicting meaning fails closed.
• Every fact receives purpose/disposition and appears in deterministic realization reporting.

Closure

Close this index after all active work is represented in its owning repository issues and the next released source-recovery stack consumes the Screenplay executable semantic model through atomic adapters. Do not use this issue as a substitute for implementation acceptance criteria.

[woksin]

Composition architecture is now explicitly tracked in Cratis/Screenplay.Generation#5: small external-adapter surface, independent AdapterContributions, one deterministic resolver/lowerer/printer/verifier pipeline, AST-free neutral contracts, authored-source helpers in Generation.DotNet, convenient ecosystem facades over the same seam, and no plugin protocol until a real non-.NET adapter proves it. Concept validation, Vogen, and remaining Critter Stack agents have been steered to preserve this contract.

[woksin]

Trusted publishing is now operational. All Generation 0.1-0.5 (including Vogen 0.2-0.5) and Critter Stack 0.1-0.11 versions are visible on nuget.org; Generation#2 and CritterStack#1 are closed. Parallel migration work is active: Generation package validation (#3), Critter Stack current Generation dependency + package validation (#7), and CLI normal NuGet restore/current adapter packages (cli#87).

[woksin]

Roadmap checkpoint after v0.15.0

Completed since the issue body was written:

• Screenplay.Generation v0.7.0: neutral concept representation/attributes/validation, authored Vogen discovery and validation hooks, package validation, trusted publication.
• Critter Stack v0.15.0: current Generation packages, package validation, compiled-query linking, EventProjection document operations, multi-stream identity/fan-out, projection/daemon/subscription metadata, and default Vogen composition with a seventh canonical fixture. Issue Compose Vogen concepts into Critter Stack generation #25 is closed.
• CLI v2.13.0: published Generation 0.6.1 + Critter Stack 0.13.1, package/assembly/capability provenance, canonical support reporting, ordinary NuGet restore, and removal of bootstrap/temporary resolution.

Current dependency order:

1. Verify Generation v0.7.0 and Critter Stack v0.15.0 distribution/clean-consumer assets.
2. Update CLI to Generation 0.7.0 + Critter Stack 0.15.0 and include Vogen composition in the admitted release evidence.
3. Finish deterministic external-adapter/host contract: Generation Add pinned canonical Critter Stack acceptance fixtures #5 + CLI #87.
4. Continue remaining Marten Complete Marten document and projection analysis #3 and Wolverine Complete Wolverine workflow and middleware analysis #4 in bounded source-reviewed increments.
5. Add only measured Screenplay language capabilities under Define and govern Screenplay portable executable semantics Screenplay#128.
6. Manually unlist the historical mispublished versions tracked in Generation Finalize current implementation handover #13 and Critter Stack Unlist mispublished historical package versions #37; OIDC publish credentials cannot delete/unlist.

Invariant remains unchanged: adapters emit independent immutable facts/evidence/diagnostics; one deterministic resolver/lowerer/printer/compiler pipeline owns composition and output.

[woksin]

Continuation documents refreshed in #41: the active checkpoint/resume order now starts from Generation v0.7.0, Critter Stack v0.15.0, and CLI v2.13.0; obsolete publishing-bootstrap instructions are retained only as historical context.

[woksin]

Operational verification for v0.15.0 completed from isolated exact-tag clones/scratch caches.

• Remote lightweight tag, GitHub release target, publish run 32601181165, NuGet repository metadata, and exact-tag checkout all resolve to a0df0c22f112b98b353ca6a84072761de119c7ba.
• Trusted publish passed: NuGet/login@v1 exchanged the GitHub OIDC token; NuGet package and symbols push both returned Created / Your package was pushed.
• nuget.org Cratis.CritterStack.Screenplay 0.15.0: SHA-256 632cf3510ce3418c60567e9dc83e0d3da88fe1732e924ba6d96e3b95a31748ad; catalog SHA-512 matched; repository signature verified.
• Package metadata has direct 0.7.0 dependencies on Generation, Contracts, DotNet, and the separate DotNet.Vogen adapter for net8/net9/net10. Package contains only the Critter Stack DLL/PDB per TFM; no Vogen runtime/source-generator DLL is embedded. Clean nuget.org consumer resolved all four Generation packages at 0.7.0, no Vogen/* runtime package, and passed the public-facade smoke assertions.
• Byte-identical package installed to ~/.nuget/cratis-local.
• Exact-tag package-validation sentinel passed: 352/352 Debug specs; Release 0 warnings/errors; sentinel pack and clean local-package consumer passed.
• All seven pinned canonical fixtures passed expectations and two-run byte determinism. Vogen source SHA-256 remained f63c311d6a9d05437fbfea3ffde95a8ccba91bc76b7b3acd3a64da1fbcc5e287; the six existing fixtures also remained deterministic.

Discrepancy: GitHub release v0.15.0 currently has zero assets (.../releases/download/v0.15.0/Cratis.CritterStack.Screenplay.0.15.0.nupkg returns 404), so release-asset equality with the verified nuget.org nupkg cannot be established. The NuGet publication itself is healthy and provenance-consistent.

No #3/#4 status comments added: v0.15.0 is Vogen composition/non-regression work and does not complete additional Marten or Wolverine scope.

[woksin]

v0.15.0 release-asset discrepancy remediated operationally: downloaded the repository-signed public nupkg and public symbol package, verified the nupkg NuGet.org repository signature and SHA-256 632cf3510ce3418c60567e9dc83e0d3da88fe1732e924ba6d96e3b95a31748ad, then attached both exact public packages to the GitHub release. Symbol package SHA-256: a6e519661decfaacd29e505062aede69e284617a5b8f417ac258a3e2cae9c044. No source or workflow changes were made.

[woksin]

Generation v0.7.0 operational verification passed: tag/release/NuGet/assembly/PDB provenance matches commit d9ff40966b637b25126160629d567719ce218a01; all four public packages are repository-signed and match GitHub assets; 205 exact-tag specs and warning-free all-TFM sentinel package validation passed; empty-cache core/Vogen consumers passed without Vogen runtime/source-generator leakage. Full hashes/evidence are recorded on Cratis/Screenplay.Generation#5.

[woksin]

Independent architecture review verdict: evolve, do not rewrite. Keep neutral contributions, deterministic conflict-visible resolution, one lowerer/printer/compiler path, authored-source authority, and CLI workspace ownership. Before adding another adapter family, replace long-term one-complete-provider/hidden-facade composition with a compile-time atomic adapter roster plus selection-only profiles; make Vogen/validation/value-object adapters independent; split Marten/Wolverine/integration identities; add per-adapter admission/provenance, contribution integrity/freezing, granular type-use facts, and fixed-snapshot central derivation lineage. Arc remains legacy until neutral parity. Tracked in Cratis/Screenplay.Generation#17. Existing bounded Marten/Wolverine correctness work continues because it does not add a new adapter mechanism.

[woksin]

Cross-repository operational evidence for CLI v2.15.0; canonical copy: Cratis/cli#87 (comment)

v2.15.0 exact release operational verification — 2026-08-23

Operational verification ran from isolated /tmp paths. No repository source, workflow, formula, or lock file was edited.

Release, publish, signature, and package

• v2.15.0 is a lightweight tag resolving exactly to b17cd3aafa9f022b9f32952fe3927ef412b2f1e2; the non-draft/non-prerelease release targets the same SHA.
• That merge commit has a valid GitHub repository signature (verified: true, reason: valid, verified at 2026-08-22T23:29:44Z). Repository MIT license bytes at the tag SHA-256 to 62c54759acae9b8722a44a0e3115a505d85422304f8a2e5678f32818bfcc4306.
• Publish run 32605369497 is green at that SHA: release, NuGet, all four native builds/uploads, and Homebrew publication passed. NuGet/login@v1 reports a successful OIDC-token exchange; package and symbol pushes both returned Created / Your package was pushed.
• NuGet catalog publication is 2026-08-22T23:31:02.107Z. Public Cratis.Cli.2.15.0.nupkg SHA-256 is d0f204085f9d5689bccf230748da75d08e1ac237d0c3b69afd04e54100398511; computed SHA-512 jn7hZU7/oBPFI+KagpmvdNfOn+xrreiyKsvT4GlM2PWm5CMMZrAuYJXMjDFcREDrQUjMeCRCstvlA+5tcxb5sg== equals the catalog hash.
• dotnet nuget verify --all passed the NuGet.org repository signature, certificate SHA-256 1F4B311D9ACC115C8DC8018B5A49E00FCE6DA8E2855F9F014CA6F34570BC482D.
• Nuspec/catalog metadata is Cratis.Cli 2.15.0, DotnetTool, MIT, description Command-line tool for managing and exploring Chronicle event stores, repository type git, commit b17cd3aafa9f022b9f32952fe3927ef412b2f1e2.
• A nuget.org-only isolated dotnet tool install Cratis.Cli --version 2.15.0 succeeded outside a repository. --version was exactly 7 stdout bytes (2.15.0\n) and 0 stderr bytes.
• Installed .deps.json graph contains exactly:
  • Cratis.CritterStack.Screenplay/0.15.0
  • Cratis.Screenplay.Generation/0.7.1
  • Cratis.Screenplay.Generation.Contracts/0.7.1
  • Cratis.Screenplay.Generation.DotNet/0.7.1
  • Cratis.Screenplay.Generation.DotNet.Vogen/0.7.1
• Cratis.Screenplay.Generation.DotNet.Vogen.dll is the only Vogen-named installed tool file/graph entry. No target Vogen package, runtime DLL, or source-generator DLL leaked into the installed CLI.

NuGet initially indexed 2.15.0 inconsistently across CDN endpoints: the first package retrieval succeeded but a following metadata endpoint transiently returned 404. All flat-container/registration endpoints then returned 200, and signature/install/execution verification passed on retry.

Native assets and Homebrew

Each archive contains exactly one 0755 executable named cratis; architecture and archive/formula SHA-256 are exact:

RID	Archive SHA-256	Executable SHA-256	Detected architecture
linux-arm64	d7f4dbfd505483063444e0a3adec0aa853cfa20b983d9a74a776fd172fbc3a72	6731840a5664d4075d08ac232ff6a1a327d9386254b6b1313333c3d9d7458500	ELF aarch64
linux-x64	e9c241fca47361cb4ab97f0c3abaf9f52c87c22596109dfb238009aa0d3f2862	f61fdf40fa5365685e9e763cd64f847f1d15d60826d79cf2d705bb8f9e4f9c87	ELF x86-64
osx-arm64	83fc3b9ec0ce64cde22bb95f2fed87b6313f9e70053bd1faba78a115809c976a	f7b5f582b84c20765286e8f68c699af262ab31b2ee2ef6103a354529641120a1	Mach-O arm64
osx-x64	36bc839df7cae84eff4e533ae7e290fe32cc82fed1f60da85e6ebe4b507d8c92	415e544e85861f17f2c26db1ded837fdc2b1ea65fc01e998a6aa0dd97f174ad2	Mach-O x86_64

Host native --version was exactly 2.15.0\n, empty stderr. The host archive executable and installed Homebrew executable were byte-identical (f7b5f582...). Trusted tap commit is 51dda0755b15f5e00e7db5cf42ea2bce342efc7d (Update cratis to 2.15.0; bot commit itself is unsigned). Installed and remote formulas are byte-identical, formula SHA-256 5d8b2603d5bf4b2113ec2f507c9076fdc942da9bba7616aec987e30f883bfd1c; all four formula hashes equal downloaded archives. Homebrew refreshed, upgraded 2.14.0 -> 2.15.0, linked 2.15.0, and brew test cratis/cratis/cratis passed. Formula metadata still has no license field, while repository/NuGet metadata is MIT.

Installed CLI source generation

Immutable sources were restored first:

• Arc v22.0.0: fcf6b0c0648e1bf7af8a09cc42f4c6a91c16fc7c
• JasperFx/CritterStackSamples: 2c94389bcb5face1070d0409ef284973e8aaceea
• JasperFx/CritterStackHelpDesk: b67659dd7ca6d8ff07e7b9dad20affc4a37b6062
• Critter-owned IncidentService/VogenConcepts: Cratis/Screenplay.CritterStack@a0df0c22f112b98b353ca6a84072761de119c7ba

The canonical workflow's exact disposable Marten 9.20.1 dependency completion was applied only to the scratch TripBuildingService clone. The seven Critter/Marten targets built successfully; known upstream warnings remain for Reports (NU1903), TripBuildingService (NU1902), net7 HelpDesk (NETSDK1138 plus existing source warnings), and Vogen-generated comparison operators (MA0097).

Every row below generated twice with the isolated dotnet tool, compared byte-for-byte equal, ended in exactly one LF with no CRLF/NUL, and validated with exit 0. All generation/validation streams were ANSI-free JSON.

Fixture	Provider	Support dimensions	Lines	SHA-256	Gen diag	Validation warnings
Arc expanded exact-source consumer	arc 22.0.0	Arc contract	74	082deba9e5a301dcf2bfa94c4be7d7d5854f72cb0736954c81cc37d19d375eb7	2W/2I	0
BankAccountES	critter-stack 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	160	de8e43c42c2c937f66a9d1d85eb53615e0f63fed912bfb10df8d77e9a6b8fe76	6W/13I	0
CqrsMinimalApi	critter-stack 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	68	894e38e0f64b2df4cb18b7a3402d2aa33e28abb7ee9251f150fd53df3f8ade9c	7I	0
Reports	critter-stack 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	12	d3df7f2aaa96bff36610cf71b73aaaeb524ed032b506327c8ca854c6e2839012	3I	0
MartenWithProjectAspire	marten 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	122	7236e2372e13c250db66314bc32219da3bd8c9294eabd16aa35fe906e5a26820	7W/3I	4
IncidentService	critter-stack 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	133	f8c2ef98a2b81216b426aff05f10392386eda0f699313da54286b76483074d43	5W/7I	7
CritterStackHelpDesk	critter-stack 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	106	cbd73a3dc4dcc7390b4c9cbb5bba826d52932de5bf7dfc40c0a9c1abe748b26c	6W/5I	6
VogenConcepts	critter-stack 0.15.0	Canonical / Recognized / RequiresHumanReview / LossReported	47	cf2cd8d53b880a2029ef745a57ad11ed59dd8fc65494979f9afb5fac391a16c1	5W/1I	0

The six pre-Vogen fixture hashes are unchanged from v2.13/v2.14 operational evidence.

VogenConcepts evidence

• Target provenance reports Marten 9.29.0, Vogen package 8.0.7, WolverineFx 6.29.2, and vogen.value-object.
• Exact target compile asset is lib/net10.0/Vogen.SharedTypes.dll, assembly/informational version 8.0.7.0 / 8.0.7+6d3b5f463ebe83032d6d8c184f367f27b1285439, SHA-256 049807b1ed3e493c9b7a5a1bd050c17f093e3a805691281067a7e5ded0ae599a.
• Generated source contains exactly four authored concepts (OrderKey, CorrelationId, CustomerCode, NormalizedCode), all with Validate; CustomerCode preserves Customer codes cannot be blank; ReferralCode is CustomerCode?; only OrderKey is the Marten identity, while CorrelationId remains an ordinary concept property.
• Four VOG0002 normalization losses and one VOG0003 named-instance loss produce LossReported without changing Canonical/Recognized/RequiresHumanReview.
• Every origin is authored Concepts.cs or Ordering.cs; no obj/generated, .g.cs, or .generated.cs origin occurs.

Explicit --provider marten facade characterization

Against IncidentService, explicit --provider marten exited 0 but produced byte-identical output to auto-selected critter-stack (f8c2ef98...). Provenance label/support changed to marten 0.15.0 / SourceReviewed, but still reported all WolverineFx 6.29.1 packages, Wolverine 6.29.1.0 and Wolverine.Marten assemblies, seven wolverine.* capabilities, and ten WOLVERINE diagnostics. This is the known current facade limitation: explicit Marten selection does not isolate Marten-only interpretation because both facades delegate to the same complete generator. This evidence does not imply a fix.

Discrepancies

1. Exact Arc v22.0.0 repository TestApps/Chronicle restores but currently fails its own Debug build at the tag (50 missing Arc/Chronicle API errors and existing analyzer warnings), and direct provider recognition consequently fails. To preserve exact source bytes while completing CLI regression, an isolated scratch consumer linked the exact authored fixture files and pinned published Arc/Chronicle/Testing packages at 22.0.0; it built with zero warnings/errors and produced the 74-line row above.
2. Arc machine provenance reports provider/TFM but empty packages, assemblies, and capabilities even though its selected project.assets.json contains Arc 22.0.0 and Chronicle 16.35.3 packages and compilation references. This conflicts with the current reference-doc claim that Arc reports those dimensions.
3. Vogen package and capability provenance is correct, and the exact target assembly is independently verified as Vogen.SharedTypes 8.0.7.0, but CLI machine provenance omits that assembly. The current assembly allowlist asks for Vogen, while Vogen 8.0.7's compile assembly is Vogen.SharedTypes; therefore the requested target Vogen assembly provenance is not end-to-end complete in the CLI payload.
4. Homebrew formula omits a license declaration although repository and NuGet metadata are MIT.
5. Initial NuGet CDN propagation was briefly inconsistent, then converged and all verification passed.

Scratch clones, generated files, downloaded packages/assets, isolated tool/cache, and evidence files will be removed after this evidence is cross-posted. Homebrew 2.15.0 remains installed.

[woksin]

Critter Stack v0.16.0 exact-release operational verification

Operational verification was performed from detached exact-tag worktrees, immutable sample checkouts, and isolated package caches. No repository source or workflow was edited.

Release and trusted publication

• v0.16.0 is a lightweight tag at signed merge commit b2e0fbc397df1e4cd967794fa6ff2596c0d21393 (verified: true, GitHub reason valid). The non-draft/non-prerelease release, publish checkout, NuGet catalog repository metadata, nuspec repository metadata, all packaged assembly informational versions, and SourceLink resolve to that exact SHA.
• Publish run 32605964554 passed. NuGet/login@v1 reports Successfully exchanged OIDC token for NuGet API key; package and symbol pushes both returned Created and Your package was pushed.
• NuGet catalog publication: 2026-08-22T23:44:26.853Z.

Public packages

• Cratis.CritterStack.Screenplay.0.16.0.nupkg
  • size 392248
  • SHA-256 1cea1d89692cbeaa5a884d1368acf0910002ea731c04dad1d1be68d3f87ce6d8
  • SHA-512/catalog hash GAS1GpqbpiRuicCoal0hg5JjP91PgAI4+mklATLD/N4Pvnnk/LBB/7o6SXP3XmR2Vob6ZQN2g7hv7VBn8BJJzQ== — exact match
  • NuGet.org repository signature verified; certificate SHA-256 1F4B311D9ACC115C8DC8018B5A49E00FCE6DA8E2855F9F014CA6F34570BC482D
• Cratis.CritterStack.Screenplay.0.16.0.snupkg
  • size 92974
  • SHA-256 aae43c89bccee5de7014689f3eb54717c73f4e362f9f82c059208a2d87d99bc6
• The nuspec contains net8.0, net9.0, and net10.0 groups, each with direct dependencies on Generation, Contracts, DotNet, and DotNet.Vogen 0.7.0, plus Microsoft.CodeAnalysis.CSharp 5.9.0. Package payload contains only the Critter Stack DLL/PDB per TFM; no Vogen runtime/source-generator assembly is embedded.
• Every DLL is assembly/file version 0.16.0.0, informational version 0.16.0+b2e0fbc397df1e4cd967794fa6ff2596c0d21393, with its correct net8/net9/net10 target framework.
• SourceLink JSON/checksum testing passed for every nupkg/snupkg PDB and targets raw GitHub content at the exact commit.
• A nuget.org-only empty-cache consumer restored and executed the exact public package. It resolved the four Generation packages at 0.7.0, passed every public-facade smoke assertion, and contained no Vogen/* runtime package.
• The nupkg is installed byte-identically at ~/.nuget/cratis-local/Cratis.CritterStack.Screenplay.0.16.0.nupkg.

Exact-tag build, specs, and package validation

• Debug specs: 416/416 passed, 0 failed/skipped.
• Release sentinel 9999.0.0: net8.0/net9.0/net10.0 build passed with 0 warnings / 0 errors.
• Sentinel pack/package API validation passed and created both nupkg/snupkg.
• Isolated sentinel local-package consumer restore/run passed.

Canonical compatibility

Exact pins were restored: adapter b2e0fbc397df1e4cd967794fa6ff2596c0d21393, CritterStackSamples 2c94389bcb5face1070d0409ef284973e8aaceea, HelpDesk b67659dd7ca6d8ff07e7b9dad20affc4a37b6062. The canonical workflow's exact disposable Marten 9.20.1 dependency completion was applied only to the scratch TripBuildingService checkout.

All seven fixtures were built before any generation. Known pinned upstream fixture warnings remained as documented; the adapter sentinel itself was warning-free. Every fixture passed expectations twice and both outputs were byte-identical:

Fixture	Lines	Generated SHA-256
BankAccountES	160	136ed011cc8de806d81cb98f017d2ee288b045fea72bd98f358347c8c583112e
CqrsMinimalApi	68	73b32b42a4f9e960ac3d60a6d2155ec5f27de0bacb210a531b56bec5da0ca13f
Reports	12	dd429ea98b665d8c485141ca06f77198e38186daa45917e5492375760a7e2620
MartenWithProjectAspire	122	06b77a1bb5b7b243e6167081891dd33d1c52e67a3ad2ace4f2b1071151a08958
IncidentService	133	78d8201b1b4dc2ec0097e0748bda7d37bf01ebf99a4803c35652bbc8c4d0b1ba
VogenConcepts	47	f63c311d6a9d05437fbfea3ffde95a8ccba91bc76b7b3acd3a64da1fbcc5e287
Helpdesk	106	c6b9c6f5727b3664a47a3efac3be02cfa7234c6c8bb72a1fcf14884bc09a82c3

The six pre-Vogen generated outputs above are byte-identical to an independently built exact v0.15.0 generator baseline. VogenConcepts retained source SHA-256 f63c311d..., four concepts, one domain event, MARTEN0011|OrderRegistered, and MARTEN0012|LegacyStorageEvent -> CurrentStorageEvent without originating configuration-only event types.

Release assets and discrepancies

The GitHub release initially had zero assets. This was remediated operationally by downloading the exact public NuGet packages, verifying them, and attaching those exact files. GitHub now reports:

• nupkg digest sha256:1cea1d89692cbeaa5a884d1368acf0910002ea731c04dad1d1be68d3f87ce6d8
• snupkg digest sha256:aae43c89bccee5de7014689f3eb54717c73f4e362f9f82c059208a2d87d99bc6

Both release downloads return 200, have the expected sizes, and compare byte-for-byte equal to the public NuGet files. NuGet V3/catalog and symbol CDN endpoints briefly propagated at different times immediately after publish, then converged; all final endpoint, signature, catalog, consumer, and release-download checks passed. No unresolved release discrepancy remains.

[woksin]

Cross-adapter learnings have been recorded in owning repositories: Generation #18 (authored-source and bounded Roslyn helpers), #19 (granular type-use facts/central derivation), #20 (neutral validation contracts), Critter #44 (atomic Marten/Wolverine/integration identities), CLI #95 (selection-only profiles/atomic roster), Arc #2600 (neutral export with legacy parity), and Screenplay #128 (measured language gaps). These are coordinated by Generation #17 and do not block bounded correctness work for existing Marten/Wolverine adapters.

[woksin]

v0.17.0 exact-release operational verification

Operational verification ran from isolated exact-tag/scratch checkouts and package caches. No repository source or workflow was edited.

• Lightweight tag, non-draft/non-prerelease GitHub release, signed merge commit, publish checkout, nuspec repository metadata, NuGet catalog repository metadata, assembly informational versions, and every nupkg/snupkg SourceLink map resolve to 078f5f81d349dd7a2f047b2cbeb92fa981560946. GitHub reports the merge signature verified: true, reason valid.
• Publish run 32607388624 passed at that SHA. NuGet/login@v1 reports Successfully exchanged OIDC token for NuGet API key; package and symbol pushes both returned Created / Your package was pushed.
• Public signed nupkg: 441667 bytes, SHA-256 a78bbf1ea6ff6fb495a40fac856e03583fd32f267b2487fac3ac802bffbf623d, SHA-512/catalog hash TTJ8Eh2AgjAQs32v/Pq3eEdFubP/Uh07OEA7QsngBqSrJVRIdSmr/noMqHYayxm8hEISEF0Q5TKYceyU/MxkVA==. NuGet catalog publication is 2026-08-23T00:16:50.757Z, listed, and repository signature verification passed with certificate SHA-256 1F4B311D9ACC115C8DC8018B5A49E00FCE6DA8E2855F9F014CA6F34570BC482D.
• Public snupkg: 103546 bytes, SHA-256 a48cd7ff55ff4b7c096e2571ca620e98c262e301b4e4b6fdf6a264bccc158bee.
• The package has exact net8.0/net9.0/net10.0 groups. Every DLL is assembly/file version 0.17.0.0, informational version 0.17.0+078f5f81d349dd7a2f047b2cbeb92fa981560946, with the correct TFM. Each group directly depends on Generation, Contracts, DotNet, and DotNet.Vogen 0.7.0, plus Microsoft.CodeAnalysis.CSharp 5.9.0. Payload is only the Critter Stack DLL/PDB for each TFM; no Vogen runtime/source-generator payload is embedded. SourceLink checksum tests passed for every nupkg and snupkg PDB against raw GitHub content at the exact commit.
• Exact-tag Debug suite: 482/482 passed, 0 failed/skipped. The targeted current/legacy stream family separately passed 66/66 assertions: current JasperFx.Events.IEventStream<T> and legacy Marten.Events.Aggregation.IEventStream<T>, receiver-bound AppendOne/AppendMany, same/different-model multi-stream identities, metadata-only loaded streams, commandless HTTP identity/version binding, legacy WriteAggregate, parameter-specific version/concurrency loss, generated/unrelated exclusions, and saga-return boundaries.
• Sentinel 9999.0.0 Release build passed net8/net9/net10 with 0 warnings / 0 errors; pack + package API validation created nupkg/snupkg; isolated sentinel local-package consumer passed. A separate empty-cache nuget.org consumer restored and executed 0.17.0, resolved the four Generation packages at 0.7.0, and had no Vogen/* runtime package.
• All seven canonical fixtures were built before generation. Each passed expectations twice and each output pair was byte-identical. The six non-Vogen outputs were also regenerated with the exact v0.16.0 generator and compared byte-for-byte identical:
  • BankAccountES, 160 lines: 136ed011cc8de806d81cb98f017d2ee288b045fea72bd98f358347c8c583112e
  • CqrsMinimalApi, 68: 73b32b42a4f9e960ac3d60a6d2155ec5f27de0bacb210a531b56bec5da0ca13f
  • Reports, 12: dd429ea98b665d8c485141ca06f77198e38186daa45917e5492375760a7e2620
  • MartenWithProjectAspire, 122: 06b77a1bb5b7b243e6167081891dd33d1c52e67a3ad2ace4f2b1071151a08958
  • IncidentService, 133: 78d8201b1b4dc2ec0097e0748bda7d37bf01ebf99a4803c35652bbc8c4d0b1ba
  • Helpdesk, 106: c6b9c6f5727b3664a47a3efac3be02cfa7234c6c8bb72a1fcf14884bc09a82c3
• VogenConcepts is 66 lines with exact source SHA-256 f90382df6046e122f36be4f1c083b1e4e8fafb8f32ee5f03f18d75b3dac52e1e. Canonical graph expectations prove exactly two Appends relationships from TransferBetweenOrders to Order, distinct sourceOrder/destinationOrder bindings without global identifiers, OrderDebited/OrderCredited, and parameter-specific WOLVERINE0012 diagnostics for source and destination. Existing MARTEN0011|OrderRegistered and MARTEN0012|LegacyStorageEvent -> CurrentStorageEvent behavior remains intact.
• The exact public nupkg is installed byte-identically at ~/.nuget/cratis-local/Cratis.CritterStack.Screenplay.0.17.0.nupkg.
• The GitHub release initially had zero assets. This was remediated operationally by attaching the exact verified public nupkg/snupkg. GitHub asset digests are sha256:a78bbf1e... and sha256:a48cd7ff...; fresh release downloads compare byte-for-byte equal to the public packages.

Known immutable upstream fixture warnings remained for Reports, MartenWithProjectAspire, and net7 HelpDesk as documented in COMPATIBILITY.md; the release sentinel itself was warning-free. NuGet flat-container/catalog indexing briefly lagged the successful publish, then converged. No unresolved release discrepancy remains.