docs: record marten 9 / wolverine 6 upgrade in decision log and roadmap

[leehopper]

Summary

Captures the #125 Critter Stack upgrade (Marten 9.2.1 / Wolverine 6.1.0) for future reference — the rationale and deferred levers that aren't derivable from the code:

• DEC-071 (decision log) — why we kept EventAppendMode.Rich over Marten 9's new QuickAppend default, the WolverineFx.RuntimeCompilation dev/test requirement (Wolverine 6 pulled Roslyn out of core), and the partial-projection source-generator change. Builds on DEC-048/049/067.
• ROADMAP — the stale "Marten 9 upgrade" deferred item is marked shipped (PR chore(deps): upgrade marten 8->9 and wolverine 5->6 (critter stack) #125), with the two deferred levers folded in: QuickAppend adoption (pending Rich-dependency validation) and Marten.PgVector for the LLM/coaching layer.
• Research artifact R-076 (batch-27a-critter-stack-9-6-migration.md) — consolidated, source-cited migration map (breaking changes, default flips, value unlocked), registered in the research queue.

Docs-only; no code changes.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated roadmap to reflect completion of the Marten 9.2.1 and Wolverine 6.1.0 infrastructure upgrade shipped on May 30, 2026
  • Added detailed migration documentation including decision rationale, breaking changes requiring code modifications, new behavioral defaults, and comprehensive verification procedures to guide teams upgrading to the latest infrastructure stack

[coderabbitai]

Warning

Review limit reached

@leehopper, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 33 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ed464f2d-a8ae-4537-bc63-a62abb8d9228

📥 Commits

Reviewing files that changed from the base of the PR and between 8ce2d5c and e9548a8.

📒 Files selected for processing (1)

• docs/research/artifacts/batch-27a-critter-stack-9-6-migration.md

📝 Walkthrough

Walkthrough

This pull request documents the completed Critter Stack 2026 upgrade, which updates Marten from 8.37.1 to 9.2.1 and Wolverine from 5.39.3 to 6.1.0. Changes include a formal decision record (DEC-071), a detailed migration guide covering breaking changes and behavioral shifts, and tracking updates reflecting the shipped status across the roadmap and research queue.

Changes

Critter Stack 2026 Upgrade Documentation

Layer / File(s)	Summary
DEC-071 Upgrade Decision & Rationale docs/decisions/decision-log.md	Formalizes the Critter Stack 2026 upgrade to Marten 9.2.1 / Wolverine 6.1.0, documenting version changes, the choice to keep EventAppendMode.Rich, the requirement for WolverineFx.RuntimeCompilation in dev/test with TypeLoadMode.Auto, the convention that SingleStreamProjection subclasses must be partial, and verification that envelope wiring and schema-version helpers remain unchanged.
Migration Guide: Changes, Defaults, and Verification docs/research/artifacts/batch-27a-critter-stack-9-6-migration.md	Provides comprehensive migration documentation detailing breaking changes (attribute relocations, namespace moves, projection requirements), unchanged APIs and behaviors, behavioral default shifts (append mode, identity map, async tracking, DI defaults), upgrade benefits, build/test verification outcomes, and sources.
Project Tracking: Roadmap and Research Queue Updates ROADMAP.md, docs/research/research-queue.md	Updates ROADMAP.md to mark the infrastructure upgrade as shipped on 2026-05-30 (DEC-071, PR #125) with a two-item deferred-levers list. Adds research-queue.md Batch 27 entry documenting R-076 migration scope, breaking changes, and default shifts.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: documenting the Marten 9 and Wolverine 6 upgrade in decision log and roadmap.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/research/artifacts/batch-27a-critter-stack-9-6-migration.md`:
- Around line 90-92: The document claims Wolverine "6.2.2" fixes are "directly
useful now" while the shipped version in this artifact is "6.1.0"; either update
the shipped version to 6.2.2 if that version is actually included in the repo,
or rephrase the sentence to present the 6.2.2 fixes as "post-upgrade" or
"future-upgrade value" (e.g., "useful after upgrading to 6.2.2") so the text
matches the actual shipped set; locate the string "Wolverine 6.1. EF-outbox..."
/ the clause containing "6.2.2" and change wording accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7205d03b-3204-4507-af7b-e3caf6420920

📥 Commits

Reviewing files that changed from the base of the PR and between 5867681 and 8ce2d5c.

📒 Files selected for processing (4)

• ROADMAP.md
• docs/decisions/decision-log.md
• docs/research/artifacts/batch-27a-critter-stack-9-6-migration.md
• docs/research/research-queue.md