Skip to content

Misc cleanup - #214

Merged
blehnen merged 1 commit into
masterfrom
cleanup
Jul 23, 2026
Merged

Misc cleanup#214
blehnen merged 1 commit into
masterfrom
cleanup

Conversation

@blehnen

@blehnen blehnen commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • Documentation
    • Refined wording, punctuation, formatting, and structure across coverage, inbox, Jenkins, lessons learned, and outbox guides.
    • Clarified guidance for coverage gates, transaction handling, troubleshooting, and operational procedures.
  • Chores
    • Removed several outdated roadmap, implementation plan, and design specification documents.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Documentation-only updates revise coverage, transactional-pattern, Jenkins, and lessons-learned wording and formatting. Several roadmap, planning, and specification documents were also removed.

Changes

Documentation updates

Layer / File(s) Summary
Coverage guidance revisions
docs/code-coverage.md
Coverage gates, exclusions, badge behavior, totals, and health-check instructions were reworded and reformatted.
Transactional pattern documentation
docs/inbox-pattern.md, docs/outbox-pattern.md
Inbox and outbox transaction guidance received wording, punctuation, and Markdown formatting updates without changing described semantics.
Operational documentation formatting
docs/jenkins-setup.md, docs/lessons-learned.md
Jenkins setup instructions and lessons-learned bullets were reformatted and lightly reworded.
Planning document cleanup
docs/plans/*, docs/superpowers/*
Several roadmap, implementation-plan, and design-specification documents were removed.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

Poem

I’m a rabbit with notes in my burrow so neat,
Coverage and transactions now lightly replete.
Jenkins lines hop, lessons align,
Old plans vanish from the sign.
No code was changed—just docs that shine!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is generic and does not describe the substantial documentation cleanup and file removals in the changeset. Use a specific title that names the main change, such as documentation cleanup and removal of obsolete planning/spec files.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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.

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 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/code-coverage.md`:
- Around line 67-68: Update the Dashboard.Ui coverage planning figure in the
surrounding coverage documentation: with 1,303 lines at 23.6% coverage, state
that reaching approximately 90% requires roughly 1,173 hits, or about +866
additional hits, replacing the incorrect +755 estimate.

In `@docs/inbox-pattern.md`:
- Line 250: Update the SQLite support bullet in the inbox pattern documentation
to replace “Not supported, SQLite.” with “Not supported: SQLite.” while leaving
the remaining explanation unchanged.

In `@docs/jenkins-setup.md`:
- Line 168: Update the Step 3 instruction in the Jenkins setup documentation so
the completion clause has an explicit subject, using “it should complete” or
splitting the clause into two complete sentences while preserving the existing
timing guidance.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b21237a1-9167-4507-a621-2ba2feb9fce1

📥 Commits

Reviewing files that changed from the base of the PR and between fe3909b and dce577b.

📒 Files selected for processing (12)
  • docs/code-coverage.md
  • docs/inbox-pattern.md
  • docs/jenkins-setup.md
  • docs/lessons-learned.md
  • docs/outbox-pattern.md
  • docs/plans/2026-04-22-ROADMAP.md
  • docs/plans/2026-04-22-issue-120-transport-options-cache-refresh.md
  • docs/plans/2026-04-22-issue-121-retry-decorator-shutdown-race.md
  • docs/plans/2026-04-22-issue-129-redis-dashboard-configuration.md
  • docs/plans/2026-05-19-verify-metrics-polling-fix.md
  • docs/superpowers/plans/2026-07-06-aes-message-interceptor.md
  • docs/superpowers/specs/2026-07-06-aes-message-interceptor-design.md
💤 Files with no reviewable changes (7)
  • docs/plans/2026-04-22-ROADMAP.md
  • docs/superpowers/specs/2026-07-06-aes-message-interceptor-design.md
  • docs/plans/2026-04-22-issue-121-retry-decorator-shutdown-race.md
  • docs/plans/2026-04-22-issue-129-redis-dashboard-configuration.md
  • docs/superpowers/plans/2026-07-06-aes-message-interceptor.md
  • docs/plans/2026-04-22-issue-120-transport-options-cache-refresh.md
  • docs/plans/2026-05-19-verify-metrics-polling-fix.md

Comment thread docs/code-coverage.md
Comment on lines +67 to 68
suite. Reaching 90% requires Dashboard.Ui specifically, roughly **+755 hits**, which is
Dashboard.Ui going from 23.6% to ~90%. A cheaper secondary lever is the 867 partial

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Correct the Dashboard.Ui hit estimate.

Given 1,303 lines, 23.6% coverage is approximately 307 hits. Reaching 90% requires about 1,173 hits, or roughly +866 hits, not +755. Please update this planning figure.

🤖 Prompt for 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.

In `@docs/code-coverage.md` around lines 67 - 68, Update the Dashboard.Ui coverage
planning figure in the surrounding coverage documentation: with 1,303 lines at
23.6% coverage, state that reaching approximately 90% requires roughly 1,173
hits, or about +866 additional hits, replacing the incorrect +755 estimate.

Comment thread docs/inbox-pattern.md
`DbTransaction` to expose; the capability interface is never implemented.

- **Not supported SQLite.** SQLite uses single-writer / `BEGIN EXCLUSIVE`-on-write
- **Not supported, SQLite.** SQLite uses single-writer / `BEGIN EXCLUSIVE`-on-write

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix the SQLite bullet punctuation.

“Not supported, SQLite.” is grammatically malformed. Use “Not supported: SQLite.” for clarity.

🤖 Prompt for 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.

In `@docs/inbox-pattern.md` at line 250, Update the SQLite support bullet in the
inbox pattern documentation to replace “Not supported, SQLite.” with “Not
supported: SQLite.” while leaving the remaining explanation unchanged.

Comment thread docs/jenkins-setup.md
1. Go to the `DotNetWorkQueue` job
2. Click **Build Now** (or **Scan Multibranch Pipeline Now** for the first scan)
3. Monitor Stage 1 (Build & Unit Tests) should complete in ~2 min
3. Monitor Stage 1 (Build & Unit Tests); should complete in ~2 min

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Restore a complete sentence in Step 3.

“Monitor Stage 1 …; should complete” leaves the second clause without a subject. Use “it should complete” or split it into two sentences.

🤖 Prompt for 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.

In `@docs/jenkins-setup.md` at line 168, Update the Step 3 instruction in the
Jenkins setup documentation so the completion clause has an explicit subject,
using “it should complete” or splitting the clause into two complete sentences
while preserving the existing timing guidance.

@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Jul 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.50%. Comparing base (ac2b65d) to head (dce577b).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #214      +/-   ##
==========================================
+ Coverage   90.44%   90.50%   +0.06%     
==========================================
  Files        1022     1022              
  Lines       33476    33476              
  Branches     2790     2790              
==========================================
+ Hits        30276    30298      +22     
- Misses       2291     2298       +7     
+ Partials      909      880      -29     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@blehnen
blehnen merged commit f031387 into master Jul 23, 2026
8 checks passed
@blehnen
blehnen deleted the cleanup branch July 23, 2026 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant