Scarab Field Lab is the public case library for selected Scarab Diagnostic Suite field tests and public feature pull request records.
Current verified record: 16 merged public open-source contributions across 11 repositories. The accepted contribution set spans developer tooling, container tooling, desktop infrastructure, web frameworks, application platforms, AI infrastructure, and agent systems.
Scarab Diagnostic Suite is proprietary and is not currently distributed as a public installable tool. Public materials describe selected diagnostic field tests and software-drift concepts only.
Scarab does not automate repairs or replace maintainers. It identifies evidence-backed diagnostic findings: boundary failures, repo-truth drift, verification gaps, and repair lanes.
Any repair is performed by maintainers, developers, or authorized agents outside the public Field Lab.
This repository publishes public case records only: public issue and pull request links, specific diagnostic findings, validation notes, claim boundaries, and, when applicable, the public status of a human-reviewed patch or upstream pull request. It does not contain SDS source code, internal diagnostic rules, product internals, private run artifacts, or implementation details.
Scarab Diagnostic Suite is a mechanical diagnostic layer. It inspects repository evidence, compares expected and observed behavior, and records specific findings. It is not an AI coding agent, does not use AI to determine diagnostic truth, and does not submit unattended patches. AI assistance may help after bounded diagnostic evidence exists with patch drafting or summaries, but public submissions remain human reviewed.
- Public issue and pull request links.
- Sanitized diagnostic evidence.
- Whether a case stayed diagnostic-only, became a local repair candidate, or became an upstream PR.
- Public validation summaries.
- Assistance notes where relevant.
- The current field-test index: FIELD_TEST_INDEX.md.
- The current feature PR index: FEATURE_PR_INDEX.md.
This summary is derived from public Field Lab records and live merged pull request status checked on 2026-07-25.
| Repository | Merged contributions | Area | Merged PRs |
|---|---|---|---|
directus/directus |
1 | Application platform | #27899 |
docker/compose |
1 | Container tooling | #13831 |
electron/electron |
1 | Desktop platform | #52238 |
emersion/xdg-desktop-portal-wlr |
1 | Linux desktop infrastructure | #393 |
microsoft/agent-framework |
1 | Agent framework | #7189 |
NVIDIA/NemoClaw |
2 | AI infrastructure | #7254, #7406 |
open-multi-agent/open-multi-agent |
2 | Multi-agent systems | #377, #378 |
OpenAPITools/openapi-generator |
1 | API developer tooling | #24022 |
pnpm/pnpm |
3 | Package management | #12301, #12327, #12841 |
sveltejs/kit |
2 | Web framework | #16268, #16423 |
twentyhq/twenty |
1 | Open-source application platform | #23008 |
Repeat contributions have been accepted in pnpm/pnpm, NVIDIA/NemoClaw,
open-multi-agent/open-multi-agent, and sveltejs/kit. Those records show
work continuing past a first accepted patch: learning local conventions,
responding to review, adding repository-native tests, and keeping the final
claim tied to the target project's own evidence.
Public Field Lab records document a repeatable contribution method without publishing private diagnostic internals:
- Select a real public issue, failure report, or repository drift surface.
- Reproduce, confirm, or narrow the observed behavior when possible.
- Trace the relevant code path and repository ownership boundary.
- Gather public repository evidence and current project conventions.
- Develop a minimal, scoped patch when the evidence supports one.
- Add or update tests for the behavior being changed.
- Run repository-native checks and record what passed or remained unverified.
- Review the final diff for scope, claim limits, and public evidence.
- Respond to maintainer review.
- Record the public outcome after review or merge.
Proprietary diagnostic tooling may support repository analysis, evidence gathering, patch validation, and scope control. Public submissions are still checked against the target repository's code, conventions, tests, maintainer requirements, and final review.
The detailed records remain in the case files. These selected entries show the range of accepted work without replacing the underlying evidence.
| Record | Merged PR | Focus | Public validation or review signal |
|---|---|---|---|
| pnpm #12240 | pnpm/pnpm#12301 | self-upgrade dependency-status handling when no manifest is present. |
Targeted Jest tests, TypeScript build, and package lint passed before merge. |
| NemoClaw #6042 | NVIDIA/NemoClaw#7254 | Empty policy-preset resume contract coverage. | Targeted Vitest and integration tests passed; maintainer approved and merged the test-only contribution. |
| SvelteKit #9785 | sveltejs/kit#16268 | Streamed server-data rejection race handling. | Repository checks and focused Playwright regressions passed; maintainer review retargeted and approved the PR. |
| Docker Compose #13613 | docker/compose#13831 | Variable extraction over unresolved Compose config values. | Focused and package Go tests, lint, and diff checks passed before merge. |
| Microsoft Agent Framework #7160 | microsoft/agent-framework#7189 | Python MCP sampling conversion for structured tool-use results. | Public checks and maintainer approvals completed before merge. |
| Open Multi Agent #378 | open-multi-agent/open-multi-agent#378 | Generic process backend for external agents. | Maintainer review identified blockers; follow-up revisions landed before merge. |
- SDS source code, product internals, or internal diagnostic rules.
- Private run artifacts, implementation details, or non-public records.
- Secrets or private correspondence.
- Cloned target repositories or vendored upstream source trees.
- Claims that SDS repaired a project by itself.
Use the Ideas discussion form to suggest a public Field Lab candidate.
Useful suggestions include the public issue link, the suspected boundary, reproduction notes if available, and why the case may be diagnostically interesting. Candidate suggestions are for Field Lab review only; they are not requests for SDS access or product changes.
- Scarab Boundary Contract
- Field Test Method
- Feature PR Index
- AI-Assisted Public Work Policy
- Public Evidence Policy
- Contribution Status
This work is independently researched, implemented, tested, and documented. Sponsorship supports dedicated time for public open-source diagnostics, scoped patch development, regression testing, documentation, and contribution follow-through.
Sponsor-selected work does not guarantee maintainer review, acceptance, merge, release inclusion, or downstream adoption. Maintainers remain the final authority for their own projects.
Sponsor Scarab Systems: github.com/sponsors/scarab-systems
This is Scarab... That is all.