docs(backlog): extend performance benchmark plan with layered overhead analysis

[piotrzajac]

Summary

• Extends TASK-19 with two new benchmark classes (LibraryOverheadBenchmark, MemberDataShareFixtureBenchmark) and three new acceptance criteria (Update README.md #8–Encapsulate customizations to use the same across all attributes. #10) so the benchmark suite answers three explicit questions: how much overhead does this library add on top of AutoFixture, which pipeline layer is responsible, and which usage patterns warrant guidance or refactoring
• Amends DECISION-23 §2 to reconcile the fixture-only exclusion with the new LibraryOverheadBenchmark design — fixture-only is used as a [Benchmark(Baseline = true)] reference to compute a Ratio column, not as the primary measurement target; decision status remains accepted
• Adds docs/performance-findings.md as an expected output artifact to DECISION-23 Consequences, matching AC Encapsulate customizations to use the same across all attributes. #10

Test plan

• Both backlog files render correctly as Markdown
• DECISION-23 §2 no longer contains contradictory statements about fixture-only scope
• TASK-19 AC Unit tests correction #3 lists all six benchmark classes by name
• TASK-19 ends with a ## Related section referencing the CI follow-on

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated performance benchmarking strategy to measure full attribute pipeline as primary target with new Ratio column for overhead quantification.
  • Extended benchmark scenarios to include additional measurement configurations.
  • Created new performance findings documentation to capture results and guidance.

[coderabbitai]

📝 Walkthrough

Walkthrough

Two backlog planning documents are refined to specify performance benchmarking scope and strategy. Decision-23 establishes the full attribute pipeline as primary measurement with fixture-only as baseline, introducing a ratio column deliverable. Task-19 extends benchmark scenarios to include LibraryOverheadBenchmark with baseline methods and MemberDataShareFixtureBenchmark for ShareFixture comparisons, updating acceptance criteria accordingly.

Changes

Cohort / File(s)

Summary

Performance Benchmarking Planning .backlog/decisions/decision-23 - Performance-benchmark-tooling-and-approach.md, .backlog/tasks/task-19 - Add-performance-benchmarks.md

Refined benchmark scope with full attribute pipeline as primary target and fixture-only as baseline within LibraryOverheadBenchmark. Introduces layered measurement design (A→B and B→C deltas) and new MemberDataShareFixtureBenchmark scenario. Adds acceptance criteria for six benchmark classes per module, baseline behavior configuration, and docs/performance-findings.md report deliverable capturing ratios and refactoring guidance.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• docs(backlog): register 23 historical architectural decisions #336: Modifies the same backlog decision and task entries (decision-23 and task-19) regarding performance benchmarking approach and scope specifications.

Suggested labels

enhancement

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: extending the performance benchmark plan with layered overhead analysis, which matches the PR's core objective.
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.
Description check	✅ Passed	The pull request description is well-structured with a clear summary, detailed explanation of changes, and a comprehensive test plan that validates the amendments to both backlog files.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/task-19-layered-performance-analysis

---

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.}