fix(checks): recover inconclusive probe handling - #203
christian-byrne wants to merge 6 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughThe gates now validate dependency-cruiser reports and stateless-check prerequisites before evaluation. Invalid inputs, missing files, spawn errors, and signal termination return exit code 2. Tests cover inconclusive results and preserve exit code 1 for genuine failures. ChangesGate validation
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The gate changes preserve distinct outcomes for invalid evidence, failed checks, and successful checks, with focused coverage described for each path. No actionable merge risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
|
Harness recovery: source findings preserved with attribution. No historical approval transfers. Full context for agent readersThis packet accounts for 10 source inline records for standalone harness recovery. Frontend relocation remains deferred. Original threads and every original routing destination remain intact. scripts/check-import-graph.mjsCodeRabbit finding, 2026-09-03T15:50:18Z: fixed-and-reverified at replacement commit. Required summary fields and malformed rows are validated before access; coordinator's 23 focused tests pass, including malformed evidence exit 2.
scripts/check-stateless.mjsCodeRabbit finding, 2026-09-03T15:50:18Z: fixed-and-reverified at replacement commit. Missing executable/file, spawn errors and signal termination exit 2; real lint/probe findings exit 1 and clean evidence exits 0. Coordinator executed these focused cases.
test/check-import-graph.test.tsCodeRabbit finding, 2026-09-03T15:50:19Z: fixed-and-reverified at replacement commit. NodeJS.ProcessEnv now models optional environment values; complete typecheck passes. The earlier annotation also compiled, so this is a type-model correction, not a reproduced compiler failure. No human decision needed.
.agents/checks/import-graph.mdCodeRabbit finding, 2026-09-04T18:54:46Z: superseded-with-reason at replacement commit. The frontend pnpm instruction applies to its workspace, not standalone CMP. CMP tracks package-lock.json and its existing import-graph profile uses npm ci/npm run check:imports. Preserve npm here and preserve the original frontend finding; no package-manager choice is reopened.
Coordinator read all 34 selected complete bodies and verified identities, authors, dates, body equality, anchors and original destinations. Bounded refresh found no edits or new replies. Three further threads (nine records) remain explicitly unadjudicated; this is not whole-parent closure. Complete private source bodies and immutable ledger remain unchanged. For the check-script replacement, 23 focused tests and complete typechecks passed on the published head; the preceding runtime-identical head passed 1,027 full tests. For the portable harness replacement, no new tests ran in this pass. Fresh hosted review and consumer verification remain separate. Glossary: CMP = comfy-multi-player; disposition = treatment at this replacement only; inconclusive = missing or malformed evidence, never a passing check. |
Full context for agent readers
The bounded refresh found no new replies or body edits in this source thread. Original author/date/body, reply relationships, original/current commit anchors and all other destination routes remain preserved. This pass inspected committed source, not a new test run. After integrating the subsequently merged standalone governance change, reconfirm stateless precondition/probe tests, complete types, substantive exact-head review and hosted checks. No source thread is being resolved and no historical approval or QA result transfers. CMP means standalone comfy-multi-player. QA means quality assurance and test evidence. |
|
@coderabbitai review Review the standalone harness recovery at the current head. The source-review carryover remains below; frontend relocation stays deferred. |
|
✅ Action performedReview finished.
|
Human owner: christian-byrne
Full context for agent readers
Recovery scope
Recovers import-graph and stateless-probe fixes from the preserved frontend migration parent, directly onto standalone comfy-multi-player main. Frontend relocation remains deferred. The private parent map identifies these source portions as H036, H040 and H066 (source hunk identifiers).
At published head, malformed dependency-cruiser summaries, negative work counts, malformed violation rows, missing Vitest/probe, spawn failure and signal termination exit 2 (inconclusive). Genuine findings and failing probes remain failures. Tests execute actual scripts in isolated fixtures. The forward merge preserves standalone main's fixture-root governance and this replacement's missing-probe protections together. No runtime dependency was added.
Verification
Normally integrated standalone governance main, preserving both histories without conflicts or corrective source changes. Node 22.22.2; existing identical-lockfile dependencies reused without installation. The integrated head passes 1,037 tests across 80 files, 29 focused tests, complete types/build and all structural package gates, including all six remotely verified source pins. Coordinator independently reran the 29 focused tests and complete typechecks. Lint has zero errors and existing warnings. New-head hosted checks and substantive fresh review remain separate. No new mutation-score or consumer-testing claim.
Review continuity
The additional three-record carryover packet also remains preserved. Its standalone npm remediation was rechecked after integration; frontend-specific obligations remain separate.
Original authors, replies, source anchors, branches and review records stay intact; no historical approval transfers. Other portable-harness findings belong to the separate replacement, not this script slice. No operation semantics, exports, dependencies, widget catalog or release version changed. No package publication, deployment or source retirement.
Glossary: CMP = comfy-multi-player; inconclusive = unavailable or malformed evidence, never a passing check.
Summary by CodeRabbit
Bug Fixes
Tests