qa-orchestrator 0.1.0__tar.gz

qa_orchestrator-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+build/
+dist/
+*.egg-info/
+.venv/
+venv/
+
+# Walks recorded from a real machine. A Redfish walk carries serial numbers, asset
+# tags and MAC addresses, so a capture is a fleet inventory disclosure. Scenario
+# runs write walks to a temporary directory for exactly this reason; anything
+# landing here was put here deliberately and should be looked at before committing.
+walks/
+*.capture.json

qa_orchestrator-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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
+      (an example is provided in the Appendix below).
+
+      "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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

qa_orchestrator-0.1.0/NOTICE

@@ -0,0 +1,32 @@
+qa-orchestrator
+Copyright 2026 James Sheen
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+this file except in compliance with the License. You may obtain a copy of the
+License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed
+under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
+CONDITIONS OF ANY KIND, either express or implied.
+
+DEPENDENCIES
+
+One at runtime. The scenario format is YAML and the standard library has no
+reader for it; everything else here is stdlib, because this has to run on the
+same bring-up bench the audit tool holds itself to.
+
+    PyYAML                MIT
+
+Two optional, neither of them imported for a verdict:
+
+    bmc-sensor-audit      Apache-2.0   the referee, run as a subprocess and read
+                                       through its exit code and its report --
+                                       see referee.py, and the test that parses
+                                       this package's imports to keep it that way
+    pytest                MIT          tests only; not installed by a plain
+                                       `pip install qa-orchestrator`
+
+Licences read from each distribution's own metadata, not from a list written
+somewhere else and copied.

qa_orchestrator-0.1.0/PKG-INFO

@@ -0,0 +1,171 @@
+Metadata-Version: 2.5
+Name: qa-orchestrator
+Version: 0.1.0
+Summary: Inject faults, drive walks, and check the audit tool reached the verdict it should have.
+Project-URL: Homepage, https://github.com/james-sheen/qa-orchestrator
+Project-URL: Source, https://github.com/james-sheen/qa-orchestrator
+Project-URL: Issues, https://github.com/james-sheen/qa-orchestrator/issues
+Author: James Sheen
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: bmc,certification,fault-injection,openbmc,qa,redfish
+Requires-Python: >=3.10
+Requires-Dist: pyyaml>=6
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Provides-Extra: referee
+Requires-Dist: bmc-sensor-audit[detect]<0.2,>=0.1; extra == 'referee'
+Description-Content-Type: text/markdown
+
+# qa-orchestrator
+
+Inject faults, drive walks, and check the audit tool reached the verdict it should have.
+
+[`bmc-sensor-audit`](https://github.com/james-sheen/bmc-sensor-audit) judges firmware:
+it diffs what an OpenBMC declaration promises against what the machine reports. This
+drives both sides. It perturbs a machine in ways whose correct verdict is known in
+advance — a sensor removed, one switched off, a reading frozen — and checks the tool
+reached it.
+
+## Why this is a separate program
+
+**The audit tool is the judge of the outcome, so it cannot also be the injector.**
+A referee that shipped its own fault injection would be certifying itself: every
+scenario would be written against the behaviour the tool happens to have, and a
+tool that stopped detecting something would quietly stop being asked about it.
+
+So the injector lives outside and consumes only the referee's published surfaces —
+exit codes, the JSON report, the attestation. `referee.py` does not import
+`bmc_sensor_audit`, and a test asserts that by reading the file. If a scenario needs
+something the published surface does not carry, that is a feature request against
+the tool, not a reason to reach past it.
+
+## A scenario
+
+```yaml
+format: qa-scenario/1
+backend: mock
+mode: coverage
+config: fixtures/board.json          # resolved beside this file, not from the cwd
+
+machine:
+  sensors:
+    - {name: Inlet,  reading: 21.0, upper_critical: 80, upper_warning: 70}
+    - {name: Outlet, reading: 27.5, upper_critical: 80, upper_warning: 70}
+
+phases:
+  - walks: 1
+    expect:
+      audit: {exit: 0}
+
+  - action: {remove: Outlet}
+    walks: 1
+    expect:
+      audit:
+        exit: 1
+        finding: "not reported by the machine at all"
+        names: [Outlet]
+        not_names: [Inlet]
+      firmware: {Outlet: absent, Inlet: reading}
+```
+
+**Released — 0.1.0**, tagged `v0.1.0`, Apache-2.0, on PyPI as `qa-orchestrator`.
+
+```
+pip install qa-orchestrator
+
+qa-orchestrator check <scenario.yaml>     # parse only; needs no machine
+qa-orchestrator run <scenario.yaml>
+```
+
+The two worked scenarios are named with a placeholder above rather than by
+filename, because a wheel carries only what lives under the package directory: a
+`pip install` gives you the command and not the examples. They ship in this
+repository and in the sdist, under `scenarios/`. From a clone,
+`pip install -e .` puts the same script on the path and the scenarios beside it.
+
+**`audit` and `firmware` are different claims and both are worth making.** *The
+sensor is gone* and *the tool noticed it is gone* are separate facts. A scenario
+that could only express the second could never tell a broken injector from a blind
+referee — the run would be green either way.
+
+**`not_names` is half of every detection claim.** Naming the frozen sensor shows
+the tool found something; showing the sensor beside it was *not* named is what
+makes that evidence of detection rather than of a check that flags everything.
+
+## The format refuses what it cannot run
+
+A phase with no walks, an `expect` block that sets nothing, an action verb this
+build does not implement, a `drive` with fewer values than walks, `exit_code` where
+`exit` was meant — all rejected at parse time with the phase named. Each of them
+would otherwise produce a run that executed, reported clean, and tested nothing,
+which is indistinguishable from a real pass at the exit code.
+
+## Three tiers, and one of them says so
+
+| Backend | What it is | State |
+|---|---|---|
+| `mock` | the audit tool's own `MockBMC`, in process | working; needs no hardware |
+| `qemu` | attaches to a running instance, injects over QMP | wire format tested, integration not |
+| `testbed` | relay boards and real fans | **not implemented, and refuses** |
+
+The tiers exist so one scenario runs at increasing cost and realism without being
+rewritten. That only holds if a tier which cannot do something refuses instead of
+approximating it. `testbed` raises at construction and its refusal lists what a
+real implementation needs — a specification, not an apology. A stub that accepted
+injections and did nothing would report that real fans were pulled having touched
+nothing, and every phase after it would judge an unperturbed machine and pass.
+
+`qemu` attaches to an already-running instance whose QMP socket the scenario names.
+**It does not boot one.** Owning the boot recipe — image build id, machine type, FRU
+provisioning — is real work that is not done here, and claiming it would be worse
+than not having it. The QMP conversation is tested against a fake socket, so the
+greeting, handshake, framing and error path are covered; no real QEMU has run it.
+
+## Exit codes
+
+The same three-valued contract the audit tool uses, because this sits in the same
+pipeline and a fourth vocabulary at this layer is one more thing for a gate to get
+wrong:
+
+| | |
+|---|---|
+| `0` | every expectation held |
+| `1` | a verdict disagreed with the scenario |
+| `2` | the run could not be completed |
+
+**`2` never reads as clean.** A scenario that could not reach its backend has judged
+nothing. Could-not-complete outranks disagreement, because a run that stopped early
+has not evaluated the phases it never reached.
+
+A run also reports how many phases asserted anything. A scenario of phases that
+assert nothing is green and worthless, and the exit code cannot tell that from a
+real pass — so it is said in words instead.
+
+## The acceptance scenario
+
+`scenarios/stuck-at.yaml` reproduces the experiment the audit tool already ships: a
+sensor driven to a new value before each of twelve walks, then left alone for
+sixteen. The engine is silent while everything moves and names exactly the frozen
+sensor once one freezes, with a control sensor still moving beside it.
+
+That experiment is the acceptance test for this harness, because its outcome is
+already known. **If the orchestrator cannot express it, the DSL is wrong** — and at
+first it could not: `drive` took one sensor and a phase may carry only one action,
+so there was no way to keep a control moving beside the frozen one. The general
+`drive: {sensors: {...}}` form exists because this file needed it.
+
+Two things it does not show. Freezing a reading through a mock is an experiment, not
+a sensor failing on its own. And the declaration it runs against carries thresholds
+deliberately: a sensor declaring none is excluded from the liveness model entirely,
+so a thresholdless board produces an empty model and a clean run that checked
+nothing.
+
+## Not built yet
+
+- The redundancy scenario against the audit tool's supplemental template.
+- The `qemu` boot recipe; this build attaches to a running instance.
+- The `testbed` tier, which needs a lab.
+
+Apache-2.0.

qa_orchestrator-0.1.0/README.md

@@ -0,0 +1,151 @@
+# qa-orchestrator
+
+Inject faults, drive walks, and check the audit tool reached the verdict it should have.
+
+[`bmc-sensor-audit`](https://github.com/james-sheen/bmc-sensor-audit) judges firmware:
+it diffs what an OpenBMC declaration promises against what the machine reports. This
+drives both sides. It perturbs a machine in ways whose correct verdict is known in
+advance — a sensor removed, one switched off, a reading frozen — and checks the tool
+reached it.
+
+## Why this is a separate program
+
+**The audit tool is the judge of the outcome, so it cannot also be the injector.**
+A referee that shipped its own fault injection would be certifying itself: every
+scenario would be written against the behaviour the tool happens to have, and a
+tool that stopped detecting something would quietly stop being asked about it.
+
+So the injector lives outside and consumes only the referee's published surfaces —
+exit codes, the JSON report, the attestation. `referee.py` does not import
+`bmc_sensor_audit`, and a test asserts that by reading the file. If a scenario needs
+something the published surface does not carry, that is a feature request against
+the tool, not a reason to reach past it.
+
+## A scenario
+
+```yaml
+format: qa-scenario/1
+backend: mock
+mode: coverage
+config: fixtures/board.json          # resolved beside this file, not from the cwd
+
+machine:
+  sensors:
+    - {name: Inlet,  reading: 21.0, upper_critical: 80, upper_warning: 70}
+    - {name: Outlet, reading: 27.5, upper_critical: 80, upper_warning: 70}
+
+phases:
+  - walks: 1
+    expect:
+      audit: {exit: 0}
+
+  - action: {remove: Outlet}
+    walks: 1
+    expect:
+      audit:
+        exit: 1
+        finding: "not reported by the machine at all"
+        names: [Outlet]
+        not_names: [Inlet]
+      firmware: {Outlet: absent, Inlet: reading}
+```
+
+**Released — 0.1.0**, tagged `v0.1.0`, Apache-2.0, on PyPI as `qa-orchestrator`.
+
+```
+pip install qa-orchestrator
+
+qa-orchestrator check <scenario.yaml>     # parse only; needs no machine
+qa-orchestrator run <scenario.yaml>
+```
+
+The two worked scenarios are named with a placeholder above rather than by
+filename, because a wheel carries only what lives under the package directory: a
+`pip install` gives you the command and not the examples. They ship in this
+repository and in the sdist, under `scenarios/`. From a clone,
+`pip install -e .` puts the same script on the path and the scenarios beside it.
+
+**`audit` and `firmware` are different claims and both are worth making.** *The
+sensor is gone* and *the tool noticed it is gone* are separate facts. A scenario
+that could only express the second could never tell a broken injector from a blind
+referee — the run would be green either way.
+
+**`not_names` is half of every detection claim.** Naming the frozen sensor shows
+the tool found something; showing the sensor beside it was *not* named is what
+makes that evidence of detection rather than of a check that flags everything.
+
+## The format refuses what it cannot run
+
+A phase with no walks, an `expect` block that sets nothing, an action verb this
+build does not implement, a `drive` with fewer values than walks, `exit_code` where
+`exit` was meant — all rejected at parse time with the phase named. Each of them
+would otherwise produce a run that executed, reported clean, and tested nothing,
+which is indistinguishable from a real pass at the exit code.
+
+## Three tiers, and one of them says so
+
+| Backend | What it is | State |
+|---|---|---|
+| `mock` | the audit tool's own `MockBMC`, in process | working; needs no hardware |
+| `qemu` | attaches to a running instance, injects over QMP | wire format tested, integration not |
+| `testbed` | relay boards and real fans | **not implemented, and refuses** |
+
+The tiers exist so one scenario runs at increasing cost and realism without being
+rewritten. That only holds if a tier which cannot do something refuses instead of
+approximating it. `testbed` raises at construction and its refusal lists what a
+real implementation needs — a specification, not an apology. A stub that accepted
+injections and did nothing would report that real fans were pulled having touched
+nothing, and every phase after it would judge an unperturbed machine and pass.
+
+`qemu` attaches to an already-running instance whose QMP socket the scenario names.
+**It does not boot one.** Owning the boot recipe — image build id, machine type, FRU
+provisioning — is real work that is not done here, and claiming it would be worse
+than not having it. The QMP conversation is tested against a fake socket, so the
+greeting, handshake, framing and error path are covered; no real QEMU has run it.
+
+## Exit codes
+
+The same three-valued contract the audit tool uses, because this sits in the same
+pipeline and a fourth vocabulary at this layer is one more thing for a gate to get
+wrong:
+
+| | |
+|---|---|
+| `0` | every expectation held |
+| `1` | a verdict disagreed with the scenario |
+| `2` | the run could not be completed |
+
+**`2` never reads as clean.** A scenario that could not reach its backend has judged
+nothing. Could-not-complete outranks disagreement, because a run that stopped early
+has not evaluated the phases it never reached.
+
+A run also reports how many phases asserted anything. A scenario of phases that
+assert nothing is green and worthless, and the exit code cannot tell that from a
+real pass — so it is said in words instead.
+
+## The acceptance scenario
+
+`scenarios/stuck-at.yaml` reproduces the experiment the audit tool already ships: a
+sensor driven to a new value before each of twelve walks, then left alone for
+sixteen. The engine is silent while everything moves and names exactly the frozen
+sensor once one freezes, with a control sensor still moving beside it.
+
+That experiment is the acceptance test for this harness, because its outcome is
+already known. **If the orchestrator cannot express it, the DSL is wrong** — and at
+first it could not: `drive` took one sensor and a phase may carry only one action,
+so there was no way to keep a control moving beside the frozen one. The general
+`drive: {sensors: {...}}` form exists because this file needed it.
+
+Two things it does not show. Freezing a reading through a mock is an experiment, not
+a sensor failing on its own. And the declaration it runs against carries thresholds
+deliberately: a sensor declaring none is excluded from the liveness model entirely,
+so a thresholdless board produces an empty model and a clean run that checked
+nothing.
+
+## Not built yet
+
+- The redundancy scenario against the audit tool's supplemental template.
+- The `qemu` boot recipe; this build attaches to a running instance.
+- The `testbed` tier, which needs a lab.
+
+Apache-2.0.

qa_orchestrator-0.1.0/pyproject.toml

@@ -0,0 +1,55 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "qa-orchestrator"
+dynamic = ["version"]
+description = "Inject faults, drive walks, and check the audit tool reached the verdict it should have."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "James Sheen" }]
+keywords = ["openbmc", "redfish", "bmc", "qa", "fault-injection", "certification"]
+
+# PyYAML only. The scenario format is YAML and there is no standard-library
+# reader for it; everything else here is stdlib on purpose, because this has to
+# run on the same bring-up bench the audit tool holds itself to.
+dependencies = ["pyyaml>=6"]
+
+[project.optional-dependencies]
+# The referee. Invoked as a subprocess, never imported for its verdicts -- see
+# referee.py. Declared as an extra rather than a hard dependency so `check`
+# (parse-only) works with nothing else installed.
+referee = ["bmc-sensor-audit[detect]>=0.1,<0.2"]
+dev = ["pytest>=7"]
+
+[project.scripts]
+qa-orchestrator = "qa_orchestrator.cli:main"
+
+# Metadata is immutable per version, and a page with no way back to the source
+# is the shape a released 0.1.0 gets stuck with. Declared before the first
+# upload rather than after it.
+[project.urls]
+Homepage = "https://github.com/james-sheen/qa-orchestrator"
+Source = "https://github.com/james-sheen/qa-orchestrator"
+Issues = "https://github.com/james-sheen/qa-orchestrator/issues"
+
+[tool.hatch.version]
+path = "src/qa_orchestrator/__init__.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/qa_orchestrator"]
+
+# The two worked scenarios reach the sdist and not the wheel: a wheel carries
+# only what lives under the package directory. The README says where they are
+# rather than showing a command that needs them, because a quickstart an
+# installing reader cannot run is worse than one that names a placeholder.
+[tool.hatch.build.targets.sdist]
+include = ["src/", "tests/", "scenarios/", "README.md", "LICENSE", "NOTICE",
+           "pyproject.toml"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["src"]

qa_orchestrator-0.1.0/scenarios/fixtures/board.json

@@ -0,0 +1,14 @@
+{
+  "_why": "A minimal entity-manager declaration for the acceptance scenario. Thresholds are declared, and that is load-bearing rather than decorative: the model generator excludes a sensor that declares none, so a thresholdless board produces an empty liveness model and a clean run that checked nothing. The mock serves the same numbers, so coverage stays quiet and the scenario is about liveness alone.",
+  "Name": "QA Reference Board",
+  "Exposes": [
+    {"Name": "Inlet", "Type": "TMP75",
+     "Thresholds": [
+       {"Name": "upper critical", "Severity": 1, "Direction": "greater than", "Value": 80},
+       {"Name": "upper warning",  "Severity": 0, "Direction": "greater than", "Value": 70}]},
+    {"Name": "Outlet", "Type": "TMP75",
+     "Thresholds": [
+       {"Name": "upper critical", "Severity": 1, "Direction": "greater than", "Value": 80},
+       {"Name": "upper warning",  "Severity": 0, "Direction": "greater than", "Value": 70}]}
+  ]
+}