[jeremydmiller]

Summary

Bobcat.dll now references no JasperFx and no Wolverine assembly, and nothing in this repository references Wolverine except Bobcat.Ui (a tool, unchanged). This implements the decided design in design/jasperfx-decoupling.md. The design note, its bdd-tools-comparison.md Discussion-log entry and its design/README.md row are part of this PR.

The Critter Stack vocabulary, the audit, the samples and the spec writer move to the Wolverine repo in JasperFx/wolverine#5082. Merge order is in the design note: this PR, then Bobcat rc.2 ships, then wolverine#5082 bumps to it.

Removed (moving to the Wolverine repo):

• src/Bobcat/CritterStack/*, except RecordBuilding (TableRunner calls it, and its namespace is unchanged)
• GeneratedEventModel and SpecIdentityAudit
• The obsolete SpecificationBindings and Bobcat's SpecificationManifestAttribute
• Bobcat.CritterStackScenario.Tests, SpecIdentityAuditTests and ResourceParsingAgreementTests
• Every sample, build/Samples.cs (and its Npgsql reference), and samples.yml
• import-event-model --specs (EmlangSpecWriter, SpecProjectWriter, the spec-file merge) and its flags. The board → stubs + EventModelDefinition import and its additive merge stay.

Added to core:

• Bobcat.Resilience.DispositionKind and [ClearsOnRetry], [ClearsOnRecycle], [ClearsInFreshProcess] and [NeverRecovers], with the same members and Because. ClearsOnRecycle uses ResilienceTags.ParseResources, so there is one parser.
• PreflightResults (Successes, Failures, Succeeded(), Assert() → PreflightException naming every failure)
• ActTrigger, which replaces TriggerKind on [EventModelTrigger] with the same member names
• The publishing bridge:
  • The generator emits a module initializer that calls Bobcat.Monitoring.SpecEventModels.Register(modelName, assemblyName, json). It is emitted only when the compilation has JasperFx.Events and SpecEventModels.
  • SpecEventModelPublisher publishes the registered JSON and keeps The runner never publishes its spec assembly's Event Model half — so the merge #268 enabled has nothing to merge #294's refusal of a model with a different name.
  • EventModelBridgeTests.the_bridge_registers_json_byte_identical_to_the_pin checks the bridge's JSON byte for byte against Fixtures/bridge-event-model.json. That fixture was captured from the pre-change publisher path and committed first (dcf61a5).
• The JasperFx.Core helpers are inlined. Spectre.Console and Microsoft.Extensions.DependencyInjection / Hosting.Abstractions (9.0.0) are now core's own references. JasperFx used to bring them in.
• BobcatAssemblyReferenceTests fails if Bobcat.dll references any JasperFx* or Wolverine* assembly.

Breaking changes (rc.2)

These are also in docs/compatibility.md#migrating-to-rc-2.

1. CritterStackSpec/CritterStackScenario, EventStores, DocumentStores, SpecIdentityAudit, AddContainerChecks and services.EventStore() are now in WolverineFx.Bobcat, under the same namespace.
2. JasperFx.Testing.DispositionKind and the hint attributes become Bobcat.Resilience.*.
3. Preflight.Run returns PreflightResults.
4. [EventModelTrigger(TriggerKind.Http, …)] becomes ActTrigger.Http.
5. SpecificationBindings and Bobcat's SpecificationManifestAttribute are deleted.
6. bobcat import-event-model --specs is gone. Specs come from the Wolverine-side command.
7. A suite that got JasperFx transitively through Bobcat and uses it directly now needs its own reference.

Notes

• Supervisor (Decouple Bobcat.Supervisor from JasperFx (follows the core decoupling) #745 is separate). Supervisor.cs and SupervisorResults.cs drop using JasperFx.Testing;. Type identity forced this, because Disposition.Kind is now Bobcat's enum. Bobcat.Supervisor.csproj never referenced JasperFx directly, so the Supervisor already builds without it. Decouple Bobcat.Supervisor from JasperFx (follows the core decoupling) #745 adds its guard test.
• Test hosts that compile the Event Model (Bobcat.Generators.Tests, Bobcat.Xunit.Samples) reference JasperFx.Events directly, as a consumer does through WolverineFx.Bobcat. The generator tests read the store vocabulary from a compiled stand-in. The generator still recognizes Bobcat.CritterStack.CritterStackScenario/Spec by metadata name.
• Packages. src/Directory.Packages.props drops the Marten, Fisher, Polecat, WolverineFx.Marten/Fisher/RabbitMQ and JasperFx.Events.SourceGenerator pins, along with the alignment header that described them.
• Docs. The VitePress snippets that imported samples/ now inline that code, and their links point at the last commit that had the samples. The docs site builds.

Verification

• dotnet build bobcat.slnx: 0 errors.
• dotnet test --solution bobcat.slnx: 2662 total, 2627 passed, 0 failed, 35 skipped. The skips are the explicit or conditional probe tests and pending specs, all skipped by design.
• ./build.sh Pack at 1.0.0-rc.2.local.1 produces nine packages. The Bobcat nuspec depends only on Spectre.Console and the two Microsoft.Extensions abstractions.

Closes #744

🤖 Generated with Claude Code

https://claude.ai/code/session_01YDKQhnBVcmVLCTkJbVeADk