Skip to content

osoji sweep: fix 122 verified documentation and code findings - #202

Merged
debugmcpdev merged 4 commits into
mainfrom
osoji-sweep-20260722
Jul 23, 2026
Merged

osoji sweep: fix 122 verified documentation and code findings#202
debugmcpdev merged 4 commits into
mainfrom
osoji-sweep-20260722

Conversation

@debugmcpdev

Copy link
Copy Markdown
Collaborator

What

An exhaustive osoji audit sweep (232 warning/error findings, every one re-triaged in place with adversarial verification of dismissals) followed by fixes for all 122 verified true positives:

  • Documentation drift (93 findings): API references, architecture guides, setup docs, and READMEs corrected against actual code behavior — adapter counts, tool counts, signatures, interface fields, phantom references removed.
  • Stale comments (19): rewritten to describe what the code does now.
  • Dead code (1) and latent bugs (9): unreachable handler removed; concrete fixes for real failure paths (unguarded parses, dead env-var checks replaced with working equivalents).

Also scopes future osoji audits away from docs/archive/** via .osoji.toml.

Verification

  • Full CI suite: 2,619 passed / 18 skipped, zero failures (pnpm run test:ci).
  • Mechanical closure check (osoji verify, baseline vs post-fix re-audit): 325 findings closed, 0 closed by dismissal, 19 still open, 274 new. The 19 still-open are all info-severity implicit-contract notes, outside this sweep's warning/error scope. The "new" count is dominated by doc analyses that previously failed silently in the audit tooling (now fixed upstream) analyzing those files for the first time, plus proposal churn — they are queue for a future pass, not regressions from these fixes.

Fix authorship: each fix was drafted by a triage agent that read the finding in place, applied by a separate agent, and the whole set gated on the project's own test suite.

🤖 Generated with Claude Code

cynarlab and others added 2 commits July 22, 2026 18:05
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…comments, dead code, latent bugs)

Exhaustive re-triage of a full osoji audit (232 warning/error findings, every
one read in place, false-positive calls adversarially verified). Applied the
122 verified true positives: documentation corrected against actual code
behavior, stale comments rewritten, dead code removed, latent bugs fixed.
Full CI suite green: 2619 passed / 18 skipped.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
debugmcpdev and others added 2 commits July 23, 2026 15:58
… fix ruby version-probe race

Review findings on the sweep:
- adapter-development-guide: the dynamic loader imports the named factory
  export only; the default export is a convenience, not a requirement
  (adapter-loader.ts reads moduleRef[factoryClassName]). Also
  BaseAdapterFactory provides getMetadata()/validate() only, no
  version-compat helpers.
- dependency-injection: adapters receive AdapterDependencies, not
  IProxyProcessLauncher (which ProxyManagerFactory/ProxyManager consume).
- component-design: evaluateExpression's 4th param is timeoutMs.
- comprehensive-mcp-tools e2e: restore the step_out pass/fail expression;
  the simplified form passed whenever message was undefined, which is
  exactly what the server's {success:false, error} envelope produces.
- ruby-utils: resolve version probes on 'close' instead of 'exit' so
  stdio is drained before reading output — 'exit' can fire with pending
  stdout data, making getRdbgVersion return null on loaded CI runners
  (the exact one-test failure on this PR's previous CI run).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codecov

codecov Bot commented Jul 23, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 50.00000% with 2 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
packages/adapter-rust/src/rust-debug-adapter.ts 0.00% 2 Missing ⚠️

📢 Thoughts on this report? Let us know!

@debugmcpdev
debugmcpdev merged commit a399316 into main Jul 23, 2026
9 of 10 checks passed
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.

2 participants