DevS69 SDETKit

From noisy CI evidence to deterministic ship / no-ship decisions.

DevS69 SDETKit is a release-confidence CLI for deterministic ship/no-ship decisions with machine-readable evidence.

Primary outcome: know if a change is ready to ship. Runtime requirement: Python 3.10+.

Canonical first path: python -m sdetkit gate fast -> python -m sdetkit gate release -> python -m sdetkit doctor.

Start here

python -m venv .venv
source .venv/bin/activate
python -m pip install -U pip
python -m pip install sdetkit==1.0.3

python -m sdetkit gate fast --format json --stable-json --out build/gate-fast.json
python -m sdetkit gate release --format json --out build/release-preflight.json
python -m sdetkit doctor --format json --out build/doctor.json

Generated first-run artifacts:

build/
├── gate-fast.json
├── release-preflight.json
└── doctor.json

Why SDETKit?

Most quality tools stop at a failed check. SDETKit connects the evidence into an operator decision:

• Decide: produce deterministic SHIP / NO-SHIP evidence.
• Diagnose: extract the first meaningful failure instead of repeating the loudest wrapper error.
• Prove: recommend exact verification commands and preserve machine-readable artifacts.
• Protect: keep investigation and remediation review-first unless an explicit guarded policy allows more.

From failure to next action

input: FAILED tests/test_release_contract.py::test_wheel_smoke
classification: test
affected_file: tests/test_release_contract.py
next_command: python -m pytest -q tests/test_release_contract.py -o addopts=
authority: review-first; no repository mutation or merge authorization

Start with docs/first-failure-triage.md and docs/investigation-operator-guide.md.

Public launch proof

See the committed public launch proof for a realistic saved pytest failure reduced to its first failing node, affected file, focused proof command, and review-first decision. The same proof includes a fixture-based Python, JavaScript/TypeScript, and Go adoption profile generated without installing target dependencies, executing target code, mutating the target, or authorizing a merge.

The proof is tied to an immutable source commit and is explicitly marked main-only until the qualified 1.2.0 release.

Decision contract

Secondary lanes cover review, investigation, quality, maintenance, and CI automation once the primary gate decision is stable. Investigation/reporting/planning lanes are diagnostic-only by default; repository mutation requires explicit guarded policy and PR-only remediation controls.

What SDETKit gives teams

• Deterministic decisions: every release-confidence run ends in an auditable SHIP / NO-SHIP signal.
• Evidence-first artifacts: JSON and Markdown outputs can be reviewed by humans, bots, and CI.
• Diagnostic investigation: sdetkit investigate explains failures and recommends proof commands without mutating the repository.
• Guarded automation path: remediation and PR automation are explicit opt-in lanes, not the default behavior.
• One workflow everywhere: use the same core commands locally, in CI, and during operator handoff.

Product proof

SDETKit is backed by committed live-adoption proof.

• Evidence: docs/artifacts/live-adoption/product-proof-post-1072/
• Decision: SHIP with known STRICT_FINDINGS
• Blocking failures: 0
• Known strict finding: legacy-noargs compatibility behavior only
• Proof page: docs/live-adoption-product-proof.md

For this repository, make first-proof emits FIRST_PROOF_DECISION=SHIP|NO-SHIP and writes the consolidated bundle under build/first-proof/.

Release channel

The install command above uses the latest published package, sdetkit==1.0.3. The repository main branch contains additional diagnostic, verification, benchmark, trajectory, multi-ecosystem, CI-provider, and mixed-workspace capabilities that remain main-only until the qualified 1.2.0 release. See the current product delta before treating repository documentation as installed-wheel proof.

Documentation map

• Start in 5 minutes: docs/start-here-5-minutes.md
• Operator essentials: docs/operator-essentials.md
• Investigation operator guide: docs/investigation-operator-guide.md
• Adaptive diagnosis: docs/adaptive-diagnosis.md
• Public launch proof: docs/public-launch-proof.md
• Artifact reference: docs/artifact-reference.md
• Recommended CI flow: docs/recommended-ci-flow.md
• CLI reference: docs/cli.md
• Contributor guide: CONTRIBUTING.md

Advanced lanes live in docs

Historical and transition-era references (secondary) remain outside the first-time path.

• External repository adoption: docs/adoption.md
• Portfolio readiness and reporting: docs/portfolio-readiness.md
• Operations handbook: docs/operations-handbook.md
• Remediation cookbook: docs/remediation-cookbook.md
• Release process: docs/project/release-process.md

Top-tier reporting sample pipeline

Run make top-tier-reporting; see docs/portfolio-reporting-recipe.md and docs/kpi-schema.md.

Upgrade next (intent router)

Run make upgrade-next; see docs/upgrade-next-commands.md.

Real workflow operations

See docs/real-workflow-operations.md. Common aliases: make ops-daily, make ops-daily-fast, make ops-weekly, make ops-premerge, make ops-premerge-fast, make ops-premerge-next, make ops-premerge-next-fast, make ops-followup, make ops-now, make ops-now-lite, make ops-next.

Repository layout

Project policies

• Docs map: docs/docs-map.md
• Security: SECURITY.md
• Quality playbook: docs/project/quality-playbook.md
• Release notes: CHANGELOG.md