tidy: align Grpc/Polecat to 6.8 line and fix Swagger title#35
Merged
Conversation
Foundation tidy ahead of transport-activation work. Three surgical changes, no behavior change: - Directory.Packages.props: bump WolverineFx.Grpc and WolverineFx.Polecat 5.38.0 -> 6.8.0, joining the rest of the Wolverine suite already pinned at 6.8.0. Removes a cross-major package island sitting on the gRPC critical path. Both versions verified on nuget.org. Inert at compile time — no .cs references either package yet — and restore/build/test stay green. - src/CritterCab.Dispatch/Program.cs: rename the dev Swagger UI title from the wrong sibling-project name "CritterBids API" to "CritterCab Dispatch API". - docs/skills/DEBT.md: register (not fix) two at-threshold skill-debt rows surfaced by retro 005 — the marker-interface union return type and the event-triggered automation handler shape — grouped under wolverine-handlers (or a possible new wolverine-marten-automation skill). The bundling-rule gap was deliberately not registered: no source names a target skill. Deliberately NOT in scope: full-suite refresh to 6.14, fixing the registered skill debt. Those are separate tidy sessions. Verification: dotnet restore clean (no NU1605/NU1608); dotnet build 0/0; dotnet test 11/11 passing (Docker-backed Testcontainers.PostgreSql).
erikshafer
added a commit
that referenced
this pull request
Jul 10, 2026
* tidy: packages — Critter Stack refresh (WolverineFx 6.8 → 6.17) Bump the WolverineFx family 6.8.0 → 6.17.0 (all nine pinned entries). Only the WolverineFx.* packages are pinned in CPM; Marten, JasperFx, and Weasel flow transitively and resolve to the aligned 6.17 line (Marten 9.14.0, JasperFx 2.24.1, Weasel 9.16.2). Alba is already at latest (8.5.2), unchanged. Minor bump within the 6.x line (the 5→6 / Marten 8→9 migration is already behind us): clean drop-in — restore + `dotnet build CritterCab.slnx` green with zero code changes. Discharges the "full-suite 6.x refresh still owed" item tracked since the Grpc/Polecat island was closed to 6.8 (PR #35). Local test run blocked by a degraded Docker Desktop engine (Testcontainers container start hangs before any app code runs) — deferring the test gate to CI, which exercises the suite in a clean Linux Docker environment. * Add retro for the Critter Stack package refresh Records the WolverineFx 6.8 → 6.17 bump, the build + CI 11/11 verification, and the local-Docker caveat. Indexed in the retrospectives README.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Step 0 foundation tidy ahead of the transport-activation roadmap (Telemetry-first). Three surgical, no-behavior-change items. Full rationale:
docs/planning/2026-06-25-state-of-the-repo-transport-and-critterwatch.md§1.4 + §6 Phase 0.1. Align
WolverineFx.Grpc+.Polecatto the 6.8 lineDirectory.Packages.props: both bumped5.38.0 → 6.8.0, joining the rest of the Wolverine suite (core/Http/Marten/ASB/Kafka/SignalR/RuntimeCompilation already at6.8.0). Removes a cross-major package island sitting directly on the gRPC critical path. Both versions verified on nuget.org. Inert at compile time — no.csfile references either package yet, so restore touches neither.2. Fix the dev Swagger title
src/CritterCab.Dispatch/Program.cs:"CritterBids API"→"CritterCab Dispatch API"(was naming the wrong sibling project in the public showcase's Swagger UI).3. Register (not fix) at-threshold skill debt
docs/skills/DEBT.md: two rows from retro 005 — the marker-interface union return type and the event-triggered automation handler shape — grouped underwolverine-handlers(or a possible newwolverine-marten-automationskill). Registering stops the debt evaporating between sessions; the fix is a futuretidy: skillsPR. The bundling-rule gap was deliberately not registered — neither retro 005 nor the handoff names a target skill, and the file's convention requires one.Out of scope (deliberately)
tidy: skillssession.Verification
dotnet restore— clean, no NU1605/NU1608.dotnet build CritterCab.slnx— 0 warnings, 0 errors.dotnet test— 11/11 passing (1 smoke + 3×5.1 + 4×5.2 + 3×5.3), Docker-backed Testcontainers.PostgreSql.