sdetkit 1.0.3__tar.gz

sdetkit-1.0.3/LICENSE

@@ -0,0 +1,160 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright
+owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities
+that control, are controlled by, or are under common control with that entity.
+For the purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by
+contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including
+but not limited to software source code, documentation source, and configuration
+files.
+
+"Object" form shall mean any form resulting from mechanical transformation or
+translation of a Source form, including but not limited to compiled object code,
+generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made
+available under the License, as indicated by a copyright notice that is included
+in or attached to the work.
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that
+is based on (or derived from) the Work and for which the editorial revisions,
+annotations, elaborations, or other modifications represent, as a whole, an
+original work of authorship. For the purposes of this License, Derivative Works
+shall not include works that remain separable from, or merely link (or bind by
+name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version
+of the Work and any modifications or additions to that Work or Derivative Works
+thereof, that is intentionally submitted to Licensor for inclusion in the Work
+by the copyright owner or by an individual or Legal Entity authorized to submit
+on behalf of the copyright owner. For the purposes of this definition,
+"submitted" means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems, and
+issue tracking systems that are managed by, or on behalf of, the Licensor for
+the purpose of discussing and improving the Work, but excluding communication
+that is conspicuously marked or otherwise designated in writing by the copyright
+owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
+of whom a Contribution has been received by Licensor and subsequently
+incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License,
+each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,
+no-charge, royalty-free, irrevocable (except as stated in this section) patent
+license to make, have made, use, offer to sell, sell, import, and otherwise
+transfer the Work, where such license applies only to those patent claims
+licensable by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s) with the Work
+to which such Contribution(s) was submitted. If You institute patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Work or a Contribution incorporated within the Work constitutes
+direct or contributory patent infringement, then any patent licenses granted to
+You under this License for that Work shall terminate as of the date such
+litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy of
+this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that You
+changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any part
+of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then
+any Derivative Works that You distribute must include a readable copy of the
+attribution notices contained within such NOTICE file, excluding those notices
+that do not pertain to any part of the Derivative Works, in at least one of the
+following places: within a NOTICE text file distributed as part of the
+Derivative Works; within the Source form or documentation, if provided along with
+the Derivative Works; or, within a display generated by the Derivative Works, if
+and wherever such third-party notices normally appear. The contents of the
+NOTICE file are for informational purposes only and do not modify the License.
+
+You may add Your own attribution notices within Derivative Works that You
+distribute, alongside or as an addendum to the NOTICE text from the Work,
+provided that such additional attribution notices cannot be construed as
+modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a whole,
+provided Your use, reproduction, and distribution of the Work otherwise complies
+with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein shall
+supersede or modify the terms of any separate license agreement you may have
+executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any warranties
+or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tort (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to in
+writing, shall any Contributor be liable to You for damages, including any
+direct, indirect, special, incidental, or consequential damages of any character
+arising as a result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill, work stoppage,
+computer failure or malfunction, or any and all other commercial damages or
+losses), even if such Contributor has been advised of the possibility of such
+damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or
+Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations
+and/or rights consistent with this License. However, in accepting such
+obligations, You may act only on Your own behalf and on Your sole responsibility,
+not on behalf of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability incurred by, or
+claims asserted against, such Contributor by reason of your accepting any such
+warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

sdetkit-1.0.3/MANIFEST.in

@@ -0,0 +1 @@
+include src/sdetkit/public_command_surface.json

sdetkit-1.0.3/PKG-INFO

@@ -0,0 +1,314 @@
+Metadata-Version: 2.4
+Name: sdetkit
+Version: 1.0.3
+Summary: Operator-grade release confidence and test intelligence platform: deterministic gates, evidence, integration assurance, and failure forensics.
+Author: DevS69 contributors
+Maintainer: DevS69 maintainers
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/sherif69-sa/DevS69-sdetkit
+Project-URL: Repository, https://github.com/sherif69-sa/DevS69-sdetkit
+Project-URL: Documentation, https://sherif69-sa.github.io/DevS69-sdetkit/
+Project-URL: Issues, https://github.com/sherif69-sa/DevS69-sdetkit/issues
+Project-URL: Releases, https://github.com/sherif69-sa/DevS69-sdetkit/releases
+Project-URL: Changelog, https://github.com/sherif69-sa/DevS69-sdetkit/blob/main/CHANGELOG.md
+Project-URL: Release Process, https://github.com/sherif69-sa/DevS69-sdetkit/blob/main/RELEASE.md
+Project-URL: Trust and Support Policy, https://github.com/sherif69-sa/DevS69-sdetkit/blob/main/docs/versioning-and-support.md
+Keywords: sdet,testing,qa,automation,cli,devtools,quality-gates
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Utilities
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx<1,>=0.28.1
+Provides-Extra: dev
+Requires-Dist: build==1.4.3; extra == "dev"
+Requires-Dist: mypy==1.20.1; extra == "dev"
+Requires-Dist: pre-commit==4.5.1; extra == "dev"
+Requires-Dist: ruff==0.15.11; extra == "dev"
+Requires-Dist: twine==6.2.0; extra == "dev"
+Provides-Extra: test
+Requires-Dist: hypothesis; extra == "test"
+Requires-Dist: PyYAML; extra == "test"
+Requires-Dist: pytest; extra == "test"
+Requires-Dist: pytest-asyncio; extra == "test"
+Requires-Dist: pytest-cov; extra == "test"
+Requires-Dist: pytest-xdist[psutil]; extra == "test"
+Provides-Extra: docs
+Requires-Dist: mkdocs==1.6.1; extra == "docs"
+Requires-Dist: mkdocs-material==9.7.6; extra == "docs"
+Provides-Extra: packaging
+Requires-Dist: build==1.4.3; extra == "packaging"
+Requires-Dist: check-wheel-contents==0.6.3; extra == "packaging"
+Requires-Dist: twine==6.2.0; extra == "packaging"
+Provides-Extra: telegram
+Requires-Dist: python-telegram-bot<23,>=22.7; extra == "telegram"
+Provides-Extra: whatsapp
+Requires-Dist: twilio<10,>=9.10.4; extra == "whatsapp"
+Dynamic: license-file
+
+# DevS69 SDETKit
+
+DevS69 SDETKit is a release-confidence CLI: it gives engineering teams deterministic ship/no-ship decisions with machine-readable evidence, using one repeatable command path from local to CI.
+
+**Primary outcome:** know if a change is ready to ship.
+
+**Canonical first path:** `python -m sdetkit gate fast` → `python -m sdetkit gate release` → `python -m sdetkit doctor`.
+
+## Product promise (30-second view)
+
+SDETKit's primary user outcome is **shipping readiness confidence**: a team can decide go/no-go from explicit JSON evidence instead of ad hoc interpretation.
+
+In plain terms: one clear product identity, one primary outcome, one canonical first path.
+
+The primary path is always:
+
+`python -m sdetkit gate fast` → `python -m sdetkit gate release` → `python -m sdetkit doctor`
+
+Everything else (umbrella kits, utilities, historical/transition-era lanes) stays available, but is intentionally secondary to first-time adoption.
+
+## Canonical first proof lane (start here)
+
+Run this exact command path first in a brand-new repository (not this repo):
+
+```bash
+mkdir my-repo && cd my-repo
+git init
+python -m pip install "git+https://github.com/sherif69-sa/DevS69-sdetkit.git"
+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
+```
+
+Expected first artifacts:
+
+```text
+build/
+├── gate-fast.json
+└── release-preflight.json
+```
+
+Inspect order:
+1. `build/release-preflight.json` (`ok`, `failed_steps`, `profile`)
+2. If `failed_steps` includes `gate_fast`, open `build/gate-fast.json` (`ok`, `failed_steps`, `profile`)
+3. Use raw logs only after artifact triage
+
+What success means:
+- `release-preflight.json` has `ok: true`
+- `gate-fast.json` has `ok: true`
+
+What failure means:
+- `ok: false` and/or non-empty `failed_steps` gives the first deterministic remediation target.
+- A non-zero exit code with JSON artifacts present is still a trustworthy first run: inspect `failed_steps` instead of treating it as a hidden crash.
+
+External first-run contract proof (automated):
+
+```bash
+python -m pytest -q tests/test_external_first_run_contract.py
+```
+
+This acceptance test creates a truly fresh temporary repo, installs SDETKit into a clean virtual environment, executes the canonical commands, and verifies artifact contracts.
+
+```text
+$ cd examples/adoption/real-repo
+$ python -m sdetkit gate fast
+exit 2  -> build/gate-fast.json: ok=false (fixture triage)
+$ python -m sdetkit gate release
+exit 2  -> build/release-preflight.json: ok=false (fixture triage)
+$ python -m sdetkit doctor
+exit 0  -> build/doctor.json: ok=true
+```
+
+Real fixture-oriented canonical flow; any failing gate result shown here is expected triage for the adoption fixture, not a product failure.
+
+Context: [`docs/real-repo-adoption.md`](docs/real-repo-adoption.md)
+
+## Canonical local-to-CI journey
+
+## Top-tier reporting sample pipeline
+
+Run the end-to-end seeded reporting flow (portfolio scorecard -> KPI snapshot -> contract checks -> bundle promotion):
+
+```bash
+make top-tier-reporting
+```
+
+Optional date/window overrides:
+
+```bash
+make top-tier-reporting DATE_TAG=2026-04-17 WINDOW_START=2026-04-11 WINDOW_END=2026-04-17 GENERATED_AT=2026-04-17T10:00:00Z
+```
+
+Primary artifacts produced under `docs/artifacts/`:
+
+- `portfolio-scorecard-sample-<date>.json`
+- `kpi-weekly-from-portfolio-<date>.json`
+- `kpi-weekly-contract-check-<date>.json`
+- `top-tier-contract-check-<date>.json`
+- `top-tier-bundle-manifest-<date>.json`
+- `top-tier-bundle-manifest-check-<date>.json`
+
+See: [`docs/portfolio-reporting-recipe.md`](docs/portfolio-reporting-recipe.md) and [`docs/kpi-schema.md`](docs/kpi-schema.md).
+
+## Production-readiness snapshot (investor/leadership brief)
+
+Generate a deterministic readiness scorecard that summarizes governance, CI, quality, and release evidence surfaces.
+The scorecard is content-aware (checks policy keywords and CI steps), so it is useful for real production triage:
+
+```bash
+python -m sdetkit readiness . --format text
+python -m sdetkit readiness . --format json
+```
+
+Use this output in due-diligence decks, internal operating reviews, or go-to-production checkpoint meetings.
+For repo targets, `sdetkit review` also publishes this snapshot into the review adaptive database (`adaptive_database.readiness_snapshot`).
+Readiness output includes pass/miss scorecards and achievement tiers so reviewers can track quality progression over time.
+Remediation recommendations are adaptive from scan evidence (lane/priority/rationale), not fixed static text.
+The readiness snapshot also tracks test scenario capacity against a 250-scenario target for scale readiness planning.
+For top-tier decisions, use `top_tier_ready` and `operational_tier` from readiness JSON.
+Review adaptive database also includes large-scale analytics blocks (`quality_matrix`, `findings_analytics`, `action_analytics`, `scalability_posture`) to power richer dashboards.
+For near-term launch operations, use `adaptive_database.release_readiness_contract` (`gate_decision`, blockers, next_24h_actions, next_72h_actions).
+`sdetkit review` now also emits a standalone `adaptive-database.json` artifact for direct dashboard ingestion.
+It also emits `release-readiness.json` and `release-readiness.md` for final launch call workflows.
+Release readiness contract now includes `contract_id`, `generated_at_utc`, and `next_review_due_at_utc` for traceable handoffs.
+It also includes a `trend` block so each run can compare decision/blocker movement vs the previous review.
+`release_readiness_contract` now includes `risk_score`, `risk_band`, and `sla_review_hours` for release-room prioritization.
+It also includes `blocker_catalog` for structured blocker triage (id/kind/severity/priority/next_action).
+Blocker catalog now includes `owner_team` and per-blocker `response_sla_hours` for clear routing.
+`release_readiness_contract.owner_summary` aggregates blocker workload by team for standup planning.
+`release_readiness_contract.recommendation_engine` now provides structured now/next/watchlist + owner-route recommendations.
+Review emits `recommendation-backlog.json` with scored recommendation backlog (`priority_index`) for execution sequencing.
+`release_readiness_contract.agent_orchestration` now suggests which specialist agents/playbooks to run based on current blockers and risk.
+Agent entries include `engine_signals` so orchestration decisions stay aligned with adaptive review outcomes.
+Review also emits `review-contract-check.json` with machine-readable reviewer contract consistency checks.
+
+
+- Canonical first proof: [`docs/blank-repo-to-value-60-seconds.md`](docs/blank-repo-to-value-60-seconds.md)
+- Canonical real-repo fixture proof: [`docs/real-repo-adoption.md`](docs/real-repo-adoption.md)
+- Canonical CI rollout path: [`docs/recommended-ci-flow.md`](docs/recommended-ci-flow.md)
+- Canonical artifact decoder: [`docs/ci-artifact-walkthrough.md`](docs/ci-artifact-walkthrough.md)
+
+## Review command format quick guide (operator adoption)
+
+Use `sdetkit review` when you need one front-door decision pass over doctor/inspect/compare/project/history.
+
+- Use `--format json` when you need the **full review payload** (deep debugging, custom analytics, or internal tooling that consumes all sections).
+- Use `--format operator-json` when you need the **stable operator-facing integration contract** for CI jobs, dashboards, and operator automations.
+- For operator integrations, prefer `operator-json` as the long-lived parsing surface.
+
+Short deterministic examples:
+
+```bash
+python -m sdetkit review . --no-workspace --format json
+python -m sdetkit review . --no-workspace --format operator-json
+```
+
+Practical machine-consumption examples:
+
+```bash
+# Full payload: inspect status + top-level counts for deeper triage scripts
+python -m sdetkit review . --no-workspace --format json | jq '{status, severity, findings: (.top_matters | length)}'
+
+# Stable operator contract: gate on operator-facing situation/actions fields
+python -m sdetkit review . --no-workspace --format operator-json | jq '{status: .situation.status, severity: .situation.severity, now_actions: (.actions.now | length)}'
+```
+
+## Who this is for / not for
+
+**Best fit**
+- Teams that want deterministic release decisions instead of ad hoc interpretation.
+- Engineers who need machine-readable evidence for PR/release review.
+- Repos standardizing the same release checks in local and CI runs.
+
+**Probably not a fit (yet)**
+- Very low-risk repos that do not need structured release evidence.
+- Teams that only want raw tool invocations with fully custom orchestration.
+
+## Start here (canonical first path)
+
+- Install (canonical): [`docs/install.md`](docs/install.md)
+- Container runtime adoption: [`docs/container-runtime.md`](docs/container-runtime.md)
+- Blank repo proof in 60 seconds (recommended first run): [`docs/blank-repo-to-value-60-seconds.md`](docs/blank-repo-to-value-60-seconds.md)
+- Guided run (same canonical path): [`docs/ready-to-use.md`](docs/ready-to-use.md)
+- Release-confidence model (why this product exists): [`docs/release-confidence.md`](docs/release-confidence.md)
+- Root CLI grouping and canonical path view: `python -m sdetkit --help`
+- Machine-readable public command contract: [`src/sdetkit/public_command_surface.json`](src/sdetkit/public_command_surface.json)
+- Stability levels (policy boundary): [`docs/stability-levels.md`](docs/stability-levels.md) — understand what is stable vs advanced vs experimental
+- Before/after evidence behavior: [`docs/before-after-evidence-example.md`](docs/before-after-evidence-example.md)
+- Real evidence artifacts from this repo: [`docs/evidence-showcase.md`](docs/evidence-showcase.md)
+
+## Secondary surfaces (after canonical confidence path)
+
+These remain available and supported after the core release-confidence lane is trusted, but they are intentionally not the front-door recommendation.
+
+### Extended repo lanes
+
+```bash
+make bootstrap
+bash quality.sh ci
+python -m sdetkit kits list
+python -m sdetkit legacy list
+python -m sdetkit legacy <historical-command>
+python -m sdetkit --help --show-hidden
+```
+
+### Repo health snapshot
+
+```bash
+python -m pip install -r requirements-test.txt
+# tests require Python >= 3.11
+PYTHONPATH=src python -m sdetkit.test_bootstrap_contract --strict
+PYTHONPATH=src python -m sdetkit.test_bootstrap_validate --strict
+# optional CI-style evidence outputs:
+./ci.sh quick --artifact-dir .sdetkit/out
+make merge-ready
+PYTHONPATH=src pytest -q
+bash quality.sh cov
+ruff check .
+mutmut results
+```
+
+For a focused preflight playbook (checks, artifact outputs, exit codes), see [`docs/test-bootstrap.md`](docs/test-bootstrap.md).
+
+### Coverage hardening migration (staged)
+
+- **Previous default:** `bash quality.sh cov` used `COV_FAIL_UNDER=80` when unset.
+- **New default (effective now):** `bash quality.sh cov` uses `COV_MODE=standard` (fail-under `85`).
+- **Temporary compatibility override:** `COV_FAIL_UNDER=80 bash quality.sh cov` (or `COV_MODE=legacy bash quality.sh cov`).
+- **Stricter enforcement target:** use `COV_MODE=strict` (fail-under `95`) for merge/release truth lanes by **July 1, 2026**.
+
+### Project layout
+
+```text
+src/sdetkit/   # product code + CLI
+tests/         # automated tests
+docs/          # user and maintainer docs
+examples/      # runnable examples
+scripts/       # repo helper scripts
+.sdetkit/      # local generated outputs
+artifacts/     # generated evidence packs
+```
+
+## Documentation and references
+
+- Docs hub: [`docs/index.md`](docs/index.md)
+- Architecture quick map for contributors: [`ARCHITECTURE.md`](ARCHITECTURE.md)
+- Contributing: [`CONTRIBUTING.md`](CONTRIBUTING.md)
+- Release process: [`RELEASE.md`](RELEASE.md)
+- Git workflow (branch tracking + ahead/behind): [`docs/git-workflow.md`](docs/git-workflow.md)
+- Enterprise readiness audit: [`docs/enterprise-readiness-audit-2026-04.md`](docs/enterprise-readiness-audit-2026-04.md)
+
+### Historical and transition-era references (secondary)
+
+- Compare against ad hoc workflows: [`docs/sdetkit-vs-ad-hoc.md`](docs/sdetkit-vs-ad-hoc.md)
+- Repo hygiene boundaries: [`docs/repo-cleanup-plan.md`](docs/repo-cleanup-plan.md)
+- Ongoing repo status view: [`docs/repo-health-dashboard.md`](docs/repo-health-dashboard.md)
+- Historical archive index: [`docs/archive/index.md`](docs/archive/index.md)