devagent-physical-engine 1.8.9__tar.gz → 1.9.1__tar.gz

{devagent_physical_engine-1.8.9/src/devagent_physical_engine.egg-info → devagent_physical_engine-1.9.1}/PKG-INFO

@@ -1,12 +1,13 @@
 Metadata-Version: 2.4
 Name: devagent-physical-engine
-Version: 1.8.9
-Summary: Verification-first robotics commissioning runtime with exact-Twin evidence, qualified UR5e Gazebo/MoveIt report execution, truthful robot support tiers, selective verification, replay, regression, and FAT reporting.
+Version: 1.9.1
+Summary: Verification-first robotics commissioning runtime with declarative customer report tests, case-centric evidence reuse, qualified UR5e Gazebo/MoveIt execution, exact-Twin lineage, selective verification, regression, replay, and FAT reporting.
 Author: Tom Ha
 License: All Rights Reserved
 Project-URL: Homepage, https://github.com/tomha85/devagent-physical-engine
 Project-URL: Repository, https://github.com/tomha85/devagent-physical-engine
 Project-URL: Issues, https://github.com/tomha85/devagent-physical-engine/issues
+Project-URL: Sponsor, https://github.com/sponsors/tomha85
 Keywords: robotics,industrial-automation,agentic-ai,ros2,gazebo,moveit,pilz,verification,selective-testing,digital-twin,fat-testing,regression,evidence,replay
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
@@ -44,23 +45,56 @@ Dynamic: license-file
 [![PyPI](https://img.shields.io/pypi/v/devagent-physical-engine.svg)](https://pypi.org/project/devagent-physical-engine/)
 [![Python](https://img.shields.io/pypi/pyversions/devagent-physical-engine.svg)](https://pypi.org/project/devagent-physical-engine/)
 [![Status: Production/Stable](https://img.shields.io/badge/status-production%2Fstable-blue.svg)](#project-status)
+[![Sponsor DevAgent Physical Engine](https://img.shields.io/badge/Sponsor-DevAgent%20Physical%20Engine-EA4AAA?logo=githubsponsors&logoColor=white)](https://github.com/sponsors/tomha85)
 
 **Verification-first commissioning engineering for robotics and industrial automation.**
 
-DevAgent turns a customer engineering folder into a bounded verification workflow with immutable Digital Twin lineage, deterministic requirement verdicts, requirement-driven test cases, exact-Twin measured simulation evidence, regression analysis, FAT reporting, replay inspection, and selective retesting.
+> ❤️ **DevAgent Smart Physical Engine is independently developed.** If it saves your team engineering time, consider [sponsoring continued development](https://github.com/sponsors/tomha85).
+
+## Engine in action
+
+<p align="center">
+  <img src="docs/assets/readme/Screenshot%20from%202026-09-02%2015-14-21.png" width="100%" alt="DevAgent Smart Physical Engine exact-Twin UR5e workcell running in Gazebo Harmonic">
+</p>
+
+<p align="center">
+  <b>Exact-Twin simulation in Gazebo Harmonic</b><br>
+  <sub>Real DevAgent engine run with the bounded UR5e workcell, customer-cell entities, physics, and simulation state visible.</sub>
+</p>
+
+<table>
+  <tr>
+    <td width="50%" align="center">
+      <img src="docs/assets/readme/Screenshot%20from%202026-09-02%2015-15-17.png" width="100%" alt="DevAgent Smart Physical Engine robot task execution in Gazebo">
+      <br><b>Robot task execution</b><br>
+      <sub>Gazebo view during the bounded pick–transport–place workflow.</sub>
+    </td>
+    <td width="50%" align="center">
+      <img src="docs/assets/readme/Screenshot%20from%202026-09-02%2015-14-32.png" width="100%" alt="DevAgent Smart Physical Engine MoveIt motion planning scene in RViz">
+      <br><b>MoveIt motion planning</b><br>
+      <sub>RViz planning-scene view used alongside the qualified ROS 2 / MoveIt execution path.</sub>
+    </td>
+  </tr>
+</table>
+
+<p align="center"><sub><b>Real engine screenshots — not product renders.</b> ROS 2 Jazzy · Gazebo Harmonic · MoveIt 2 · Pilz · UR5e exact-Twin verification.</sub></p>
+
+DevAgent turns a customer engineering folder into a bounded verification workflow with immutable Digital Twin lineage, declarative customer report tests, deterministic requirement verdicts, requirement-driven physical cases, exact-Twin measured simulation evidence, regression analysis, FAT reporting, replay inspection, and selective retesting.
 
 ```text
 customer engineering files
     ↓
 intake + SHA-256 inventory
     ↓
-validated Requirement → Criterion mapping
+customer report test IDs + declarative verification contracts
     ↓
 immutable Digital Twin revision
     ↓
 requirement-driven nominal / boundary / fault cases
     ↓
-qualified exact-Twin simulation when supported
+reuse exact qualified case evidence when available
+    ↓
+execute each missing qualified physical case once
     ↓
 measured evidence
     ↓
@@ -76,7 +110,7 @@ regression + FAT report + Evidence Viewer
 Python 3.11+ is required.
 
 ```bash
-python -m pip install --upgrade devagent-physical-engine==1.8.9
+python -m pip install --upgrade devagent-physical-engine==1.9.1
 ```
 
 Verify the installed package:
@@ -88,7 +122,7 @@ python -c "import devagent_physical_engine as d; print(d.__version__)"
 Expected:
 
 ```text
-1.8.9
+1.9.1
 ```
 
 Run the normal customer workflow:
@@ -140,15 +174,15 @@ Results:           <customer-project>/devagent-results/
 DevAgent separates planning, execution, measurement, verdicts, and authority.
 
 ```text
-requirement
+report test / requirement
   ↓
-verification criterion
+declarative verification capability
   ↓
-verification case
+verification case when physical execution is required
   ↓
 exact Twin revision/hash
   ↓
-qualified simulation when available
+qualified evidence reuse or qualified simulation when available
   ↓
 measured evidence
   ↓
@@ -475,6 +509,75 @@ MoveIt DETACH is deterministic. DevAgent removes attachment ownership while the
 
 This qualification is intentionally bounded to the packaged UR5e nominal report-test scope. It does not grant arbitrary customer-cell qualification, site qualification, functional-safety certification, or autonomous real-robot execution authority.
 
+## v1.9.0 dynamic customer report verification
+
+v1.9.0 changes report orchestration from test-name-driven behavior to declarative verification capabilities while preserving the target-proven v1.8.9 physical runtime.
+
+Customer test IDs are opaque. A report row can declare its verification behavior with fields such as:
+
+```text
+test_id
+verification_mode
+metric
+comparator
+target / expected
+evidence_authority
+```
+
+For example, `FAT-CUSTOM-947` can request the physical metric `max_workpiece_tilt_deg <= 3.0` without adding a `TEST-FAT-CUSTOM-947` code branch.
+
+Interactive execution is case-centric:
+
+```text
+devagent> simulate FAT-CUSTOM-947
+  → resolve the exact report contract
+  → resolve Requirement → Mapping → Plan → Case lineage
+  → reuse exact qualified case evidence first
+  → execute the mapped physical case only when evidence is missing
+  → evaluate the requested metric generically
+
+devagent> simulate all
+  → evaluate deterministic report rows without simulation
+  → deduplicate physical case identities
+  → reuse existing qualified measurements
+  → execute each missing unique qualified physical case once
+  → share each measurement across compatible report rows
+```
+
+A requested metric that the qualified adapter does not measure remains `NOT_TESTED`. DevAgent does not fabricate the value and does not repeatedly rerun the robot merely because the metric is unavailable.
+
+The typed physical evidence path now permits bounded finite numeric/boolean customer metrics while retaining stricter semantic consistency validation for known safety metrics. This expands the report schema, not simulator authority: a qualified adapter must actually produce the requested measurement.
+
+Hosted regression includes an arbitrary customer report test using `FAT-CUSTOM-947` and `max_workpiece_tilt_deg`, proving preservation through intake, campaign creation, case mapping, selective simulation, verdict evaluation, and later `simulate all` evidence reuse.
+
+Full release notes: https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_0.md
+
+## v1.9.1 repeatable fresh physical simulation
+
+v1.9.1 makes evidence reuse and operator-requested fresh execution explicit without changing physical authority boundaries.
+
+```text
+devagent> simulate TEST-PERF-001
+  → reuse exact qualified case evidence when available
+  → execute only when the mapped case evidence is missing
+
+devagent> simulate --fresh TEST-PERF-001
+  → force a new execution of the selected unique physical case
+  → append a new immutable measurement artifact
+
+devagent> simulate --fresh all
+  → force every unique mapped physical case once
+  → still deduplicate shared case IDs across report criteria
+```
+
+`rerun TEST-X`, `rerun failed`, `rerun blocked`, `rerun affected`, and `rerun all` use the same fresh-execution contract for physical selectors. Deterministic selectors remain evidence-only and never command Gazebo.
+
+Interactive verification now owns its Gazebo/MoveIt lifecycle. After an executed verification case captures its evidence, that verification-owned stack is closed so the next fresh command starts from a clean runtime instead of competing with a stale simulator in the same ROS domain. Persistent visualization is a separate intent and remains available through `devagent robot visualize`.
+
+The lifecycle change does not relax MoveIt preexecution, canonical start-state compatibility, FollowJointTrajectory result handling, controller-feedback tracking, Twin lineage, site qualification, or real-robot execution locks.
+
+Full release notes: https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_1.md
+
 ## Qualified visual-execution scope
 
 Measured report-test execution remains intentionally narrow:
@@ -482,7 +585,7 @@ Measured report-test execution remains intentionally narrow:
 ```text
 robot:       UR5e
 operation:   load
-case scope:  one nominal mapped physical report case
+case scope:  qualified mapped physical report cases within the packaged authority
 runtime:     Ubuntu 24.04 + ROS 2 Jazzy + Gazebo Harmonic + MoveIt/Pilz
 ```
 
@@ -498,11 +601,15 @@ Use `--interactive`, or `--open` from a real terminal, to keep a bounded prompt:
 status
 tests
 test SELECTOR
-simulate [SELECTOR]
-rerun [SELECTOR]
+simulate SELECTOR
+simulate all
+simulate --fresh SELECTOR
+simulate --fresh all
+rerun SELECTOR
 rerun failed
 rerun blocked
 rerun affected
+rerun all
 replay
 report
 log
@@ -510,20 +617,24 @@ help
 quit
 ```
 
-Selectors can be requirement IDs, test IDs, or bounded groups:
+Selectors can be customer-defined requirement IDs, customer-defined test IDs, or bounded groups:
 
 ```text
-REQ-PERF-001
-TEST-PERF-001
+CUSTOM-REQ-77
+FAT-CUSTOM-947
 failed
 blocked
 affected
 all
 ```
 
-`test SELECTOR` evaluates deterministic/evidence checks without commanding the simulator.
+`test SELECTOR` evaluates the selected criterion from existing qualified evidence without commanding the simulator.
 
-`simulate TEST-X` requests qualified execution of the selected mapped physical report case.
+`simulate TEST-X` executes or reuses only the physical case required by that report row.
+
+`simulate all` creates a report-wide capability execution plan, evaluates deterministic rows directly, deduplicates physical cases, reuses exact qualified evidence first, and executes only missing unique qualified cases.
+
+`simulate --fresh TEST-X` and `rerun TEST-X` explicitly request a new physical execution; fresh report-wide execution still deduplicates physical case IDs.
 
 `replay` reconstructs persisted evidence identity; it never commands Gazebo, MoveIt, a robot, PLC, or safety PLC.
 
@@ -675,20 +786,31 @@ devagent-physical-ai optional provider-backed engineering front end
 
 # Project status
 
-**v1.8.9 — Production/Stable software workflow; target-proven qualified UR5e nominal Pick–Transport–Place report path**
+**v1.9.1 — Production/Stable software workflow; repeatable fresh physical simulation with owned verification lifecycle**
+
+v1.9.1 preserves v1.9.0's declarative customer report verification and case-centric evidence reuse, while adding explicit fresh physical execution and deterministic simulator lifecycle ownership. Normal `simulate` remains evidence-first; `simulate --fresh ...` and physical `rerun ...` force new execution, and report-wide fresh runs still execute each unique mapped case only once.
 
-v1.8.9 is the first release in this line whose exact candidate completed the entire bounded UR5e nominal report lifecycle on the intended workstation: exact Twin readback, five-group Pilz preflight, approach, verified MoveIt GRASP, lift with scoped source-support contact, Gazebo carry, transfer, place, physical release/settle, explicit MoveIt detach/world reassert, retreat, and final verification. The selected target test returned `PASSED` with measured evidence recorded.
+The physical qualification claim remains grounded in the target-proven bounded UR5e nominal report lifecycle. v1.9.1 does not expand that claim to arbitrary customer cells and does not grant site qualification, functional-safety certification, or autonomous real-robot execution authority.
 
 Production-oriented software capabilities include:
 
 ```text
 one-command customer intake
-XLSX requirement normalization
+XLSX/CSV/YAML/JSON requirement normalization
+opaque customer-defined report test IDs
+declarative verification mode / metric / comparator / target / evidence authority
+generic finite numeric/boolean physical metrics with bounded validation
 validated Requirement → Criterion mapping
 optional provider-backed advisory criterion proposals
 requirement-driven nominal / boundary / fault case generation
 immutable project/Twin lineage
 exact Requirement → Mapping → Verification Plan → Case provenance
+case-centric qualified evidence reuse
+explicit fresh physical execution
+verification-owned simulator lifecycle cleanup
+report-wide physical-case deduplication
+mixed deterministic + physical `simulate all` orchestration
+truthful NOT_TESTED for unavailable/unsupported evidence
 truthful robot support tiers
 qualified UR5e report-test visual execution contract
 direct UR5e controller-manager/action readiness binding
@@ -717,10 +839,16 @@ change impact + regression
 provider-neutral optional AI front end
 ```
 
-Production/Stable describes the bounded software workflow. The target-proven UR5e claim is limited to the qualified packaged nominal report path and exact acceptance environment. It does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, or authorized for autonomous real execution.
+Production/Stable describes the bounded software workflow. The target-proven UR5e claim remains limited to the qualified packaged nominal report path and exact acceptance environment. It does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, or authorized for autonomous real execution.
 
 ## Documentation
 
+v1.9.1 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_1.md
+
+v1.9.0 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_0.md
+
 One-command verification:
 https://github.com/tomha85/devagent-physical-engine/blob/main/docs/ONE_COMMAND_VERIFY_V13.md
 

{devagent_physical_engine-1.8.9 → devagent_physical_engine-1.9.1}/README.md

@@ -3,23 +3,56 @@
 [![PyPI](https://img.shields.io/pypi/v/devagent-physical-engine.svg)](https://pypi.org/project/devagent-physical-engine/)
 [![Python](https://img.shields.io/pypi/pyversions/devagent-physical-engine.svg)](https://pypi.org/project/devagent-physical-engine/)
 [![Status: Production/Stable](https://img.shields.io/badge/status-production%2Fstable-blue.svg)](#project-status)
+[![Sponsor DevAgent Physical Engine](https://img.shields.io/badge/Sponsor-DevAgent%20Physical%20Engine-EA4AAA?logo=githubsponsors&logoColor=white)](https://github.com/sponsors/tomha85)
 
 **Verification-first commissioning engineering for robotics and industrial automation.**
 
-DevAgent turns a customer engineering folder into a bounded verification workflow with immutable Digital Twin lineage, deterministic requirement verdicts, requirement-driven test cases, exact-Twin measured simulation evidence, regression analysis, FAT reporting, replay inspection, and selective retesting.
+> ❤️ **DevAgent Smart Physical Engine is independently developed.** If it saves your team engineering time, consider [sponsoring continued development](https://github.com/sponsors/tomha85).
+
+## Engine in action
+
+<p align="center">
+  <img src="docs/assets/readme/Screenshot%20from%202026-09-02%2015-14-21.png" width="100%" alt="DevAgent Smart Physical Engine exact-Twin UR5e workcell running in Gazebo Harmonic">
+</p>
+
+<p align="center">
+  <b>Exact-Twin simulation in Gazebo Harmonic</b><br>
+  <sub>Real DevAgent engine run with the bounded UR5e workcell, customer-cell entities, physics, and simulation state visible.</sub>
+</p>
+
+<table>
+  <tr>
+    <td width="50%" align="center">
+      <img src="docs/assets/readme/Screenshot%20from%202026-09-02%2015-15-17.png" width="100%" alt="DevAgent Smart Physical Engine robot task execution in Gazebo">
+      <br><b>Robot task execution</b><br>
+      <sub>Gazebo view during the bounded pick–transport–place workflow.</sub>
+    </td>
+    <td width="50%" align="center">
+      <img src="docs/assets/readme/Screenshot%20from%202026-09-02%2015-14-32.png" width="100%" alt="DevAgent Smart Physical Engine MoveIt motion planning scene in RViz">
+      <br><b>MoveIt motion planning</b><br>
+      <sub>RViz planning-scene view used alongside the qualified ROS 2 / MoveIt execution path.</sub>
+    </td>
+  </tr>
+</table>
+
+<p align="center"><sub><b>Real engine screenshots — not product renders.</b> ROS 2 Jazzy · Gazebo Harmonic · MoveIt 2 · Pilz · UR5e exact-Twin verification.</sub></p>
+
+DevAgent turns a customer engineering folder into a bounded verification workflow with immutable Digital Twin lineage, declarative customer report tests, deterministic requirement verdicts, requirement-driven physical cases, exact-Twin measured simulation evidence, regression analysis, FAT reporting, replay inspection, and selective retesting.
 
 ```text
 customer engineering files
     ↓
 intake + SHA-256 inventory
     ↓
-validated Requirement → Criterion mapping
+customer report test IDs + declarative verification contracts
     ↓
 immutable Digital Twin revision
     ↓
 requirement-driven nominal / boundary / fault cases
     ↓
-qualified exact-Twin simulation when supported
+reuse exact qualified case evidence when available
+    ↓
+execute each missing qualified physical case once
     ↓
 measured evidence
     ↓
@@ -35,7 +68,7 @@ regression + FAT report + Evidence Viewer
 Python 3.11+ is required.
 
 ```bash
-python -m pip install --upgrade devagent-physical-engine==1.8.9
+python -m pip install --upgrade devagent-physical-engine==1.9.1
 ```
 
 Verify the installed package:
@@ -47,7 +80,7 @@ python -c "import devagent_physical_engine as d; print(d.__version__)"
 Expected:
 
 ```text
-1.8.9
+1.9.1
 ```
 
 Run the normal customer workflow:
@@ -99,15 +132,15 @@ Results:           <customer-project>/devagent-results/
 DevAgent separates planning, execution, measurement, verdicts, and authority.
 
 ```text
-requirement
+report test / requirement
   ↓
-verification criterion
+declarative verification capability
   ↓
-verification case
+verification case when physical execution is required
   ↓
 exact Twin revision/hash
   ↓
-qualified simulation when available
+qualified evidence reuse or qualified simulation when available
   ↓
 measured evidence
   ↓
@@ -434,6 +467,75 @@ MoveIt DETACH is deterministic. DevAgent removes attachment ownership while the
 
 This qualification is intentionally bounded to the packaged UR5e nominal report-test scope. It does not grant arbitrary customer-cell qualification, site qualification, functional-safety certification, or autonomous real-robot execution authority.
 
+## v1.9.0 dynamic customer report verification
+
+v1.9.0 changes report orchestration from test-name-driven behavior to declarative verification capabilities while preserving the target-proven v1.8.9 physical runtime.
+
+Customer test IDs are opaque. A report row can declare its verification behavior with fields such as:
+
+```text
+test_id
+verification_mode
+metric
+comparator
+target / expected
+evidence_authority
+```
+
+For example, `FAT-CUSTOM-947` can request the physical metric `max_workpiece_tilt_deg <= 3.0` without adding a `TEST-FAT-CUSTOM-947` code branch.
+
+Interactive execution is case-centric:
+
+```text
+devagent> simulate FAT-CUSTOM-947
+  → resolve the exact report contract
+  → resolve Requirement → Mapping → Plan → Case lineage
+  → reuse exact qualified case evidence first
+  → execute the mapped physical case only when evidence is missing
+  → evaluate the requested metric generically
+
+devagent> simulate all
+  → evaluate deterministic report rows without simulation
+  → deduplicate physical case identities
+  → reuse existing qualified measurements
+  → execute each missing unique qualified physical case once
+  → share each measurement across compatible report rows
+```
+
+A requested metric that the qualified adapter does not measure remains `NOT_TESTED`. DevAgent does not fabricate the value and does not repeatedly rerun the robot merely because the metric is unavailable.
+
+The typed physical evidence path now permits bounded finite numeric/boolean customer metrics while retaining stricter semantic consistency validation for known safety metrics. This expands the report schema, not simulator authority: a qualified adapter must actually produce the requested measurement.
+
+Hosted regression includes an arbitrary customer report test using `FAT-CUSTOM-947` and `max_workpiece_tilt_deg`, proving preservation through intake, campaign creation, case mapping, selective simulation, verdict evaluation, and later `simulate all` evidence reuse.
+
+Full release notes: https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_0.md
+
+## v1.9.1 repeatable fresh physical simulation
+
+v1.9.1 makes evidence reuse and operator-requested fresh execution explicit without changing physical authority boundaries.
+
+```text
+devagent> simulate TEST-PERF-001
+  → reuse exact qualified case evidence when available
+  → execute only when the mapped case evidence is missing
+
+devagent> simulate --fresh TEST-PERF-001
+  → force a new execution of the selected unique physical case
+  → append a new immutable measurement artifact
+
+devagent> simulate --fresh all
+  → force every unique mapped physical case once
+  → still deduplicate shared case IDs across report criteria
+```
+
+`rerun TEST-X`, `rerun failed`, `rerun blocked`, `rerun affected`, and `rerun all` use the same fresh-execution contract for physical selectors. Deterministic selectors remain evidence-only and never command Gazebo.
+
+Interactive verification now owns its Gazebo/MoveIt lifecycle. After an executed verification case captures its evidence, that verification-owned stack is closed so the next fresh command starts from a clean runtime instead of competing with a stale simulator in the same ROS domain. Persistent visualization is a separate intent and remains available through `devagent robot visualize`.
+
+The lifecycle change does not relax MoveIt preexecution, canonical start-state compatibility, FollowJointTrajectory result handling, controller-feedback tracking, Twin lineage, site qualification, or real-robot execution locks.
+
+Full release notes: https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_1.md
+
 ## Qualified visual-execution scope
 
 Measured report-test execution remains intentionally narrow:
@@ -441,7 +543,7 @@ Measured report-test execution remains intentionally narrow:
 ```text
 robot:       UR5e
 operation:   load
-case scope:  one nominal mapped physical report case
+case scope:  qualified mapped physical report cases within the packaged authority
 runtime:     Ubuntu 24.04 + ROS 2 Jazzy + Gazebo Harmonic + MoveIt/Pilz
 ```
 
@@ -457,11 +559,15 @@ Use `--interactive`, or `--open` from a real terminal, to keep a bounded prompt:
 status
 tests
 test SELECTOR
-simulate [SELECTOR]
-rerun [SELECTOR]
+simulate SELECTOR
+simulate all
+simulate --fresh SELECTOR
+simulate --fresh all
+rerun SELECTOR
 rerun failed
 rerun blocked
 rerun affected
+rerun all
 replay
 report
 log
@@ -469,20 +575,24 @@ help
 quit
 ```
 
-Selectors can be requirement IDs, test IDs, or bounded groups:
+Selectors can be customer-defined requirement IDs, customer-defined test IDs, or bounded groups:
 
 ```text
-REQ-PERF-001
-TEST-PERF-001
+CUSTOM-REQ-77
+FAT-CUSTOM-947
 failed
 blocked
 affected
 all
 ```
 
-`test SELECTOR` evaluates deterministic/evidence checks without commanding the simulator.
+`test SELECTOR` evaluates the selected criterion from existing qualified evidence without commanding the simulator.
 
-`simulate TEST-X` requests qualified execution of the selected mapped physical report case.
+`simulate TEST-X` executes or reuses only the physical case required by that report row.
+
+`simulate all` creates a report-wide capability execution plan, evaluates deterministic rows directly, deduplicates physical cases, reuses exact qualified evidence first, and executes only missing unique qualified cases.
+
+`simulate --fresh TEST-X` and `rerun TEST-X` explicitly request a new physical execution; fresh report-wide execution still deduplicates physical case IDs.
 
 `replay` reconstructs persisted evidence identity; it never commands Gazebo, MoveIt, a robot, PLC, or safety PLC.
 
@@ -634,20 +744,31 @@ devagent-physical-ai optional provider-backed engineering front end
 
 # Project status
 
-**v1.8.9 — Production/Stable software workflow; target-proven qualified UR5e nominal Pick–Transport–Place report path**
+**v1.9.1 — Production/Stable software workflow; repeatable fresh physical simulation with owned verification lifecycle**
+
+v1.9.1 preserves v1.9.0's declarative customer report verification and case-centric evidence reuse, while adding explicit fresh physical execution and deterministic simulator lifecycle ownership. Normal `simulate` remains evidence-first; `simulate --fresh ...` and physical `rerun ...` force new execution, and report-wide fresh runs still execute each unique mapped case only once.
 
-v1.8.9 is the first release in this line whose exact candidate completed the entire bounded UR5e nominal report lifecycle on the intended workstation: exact Twin readback, five-group Pilz preflight, approach, verified MoveIt GRASP, lift with scoped source-support contact, Gazebo carry, transfer, place, physical release/settle, explicit MoveIt detach/world reassert, retreat, and final verification. The selected target test returned `PASSED` with measured evidence recorded.
+The physical qualification claim remains grounded in the target-proven bounded UR5e nominal report lifecycle. v1.9.1 does not expand that claim to arbitrary customer cells and does not grant site qualification, functional-safety certification, or autonomous real-robot execution authority.
 
 Production-oriented software capabilities include:
 
 ```text
 one-command customer intake
-XLSX requirement normalization
+XLSX/CSV/YAML/JSON requirement normalization
+opaque customer-defined report test IDs
+declarative verification mode / metric / comparator / target / evidence authority
+generic finite numeric/boolean physical metrics with bounded validation
 validated Requirement → Criterion mapping
 optional provider-backed advisory criterion proposals
 requirement-driven nominal / boundary / fault case generation
 immutable project/Twin lineage
 exact Requirement → Mapping → Verification Plan → Case provenance
+case-centric qualified evidence reuse
+explicit fresh physical execution
+verification-owned simulator lifecycle cleanup
+report-wide physical-case deduplication
+mixed deterministic + physical `simulate all` orchestration
+truthful NOT_TESTED for unavailable/unsupported evidence
 truthful robot support tiers
 qualified UR5e report-test visual execution contract
 direct UR5e controller-manager/action readiness binding
@@ -676,10 +797,16 @@ change impact + regression
 provider-neutral optional AI front end
 ```
 
-Production/Stable describes the bounded software workflow. The target-proven UR5e claim is limited to the qualified packaged nominal report path and exact acceptance environment. It does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, or authorized for autonomous real execution.
+Production/Stable describes the bounded software workflow. The target-proven UR5e claim remains limited to the qualified packaged nominal report path and exact acceptance environment. It does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, or authorized for autonomous real execution.
 
 ## Documentation
 
+v1.9.1 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_1.md
+
+v1.9.0 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V1_9_0.md
+
 One-command verification:
 https://github.com/tomha85/devagent-physical-engine/blob/main/docs/ONE_COMMAND_VERIFY_V13.md
 
@@ -712,4 +839,4 @@ Original creator: Tom Ha
 Original project: https://github.com/tomha85/devagent-physical-engine  
 All rights reserved.
 
-See repository `LICENSE`, `NOTICE`, and `COPYRIGHT` for complete ownership and usage terms.
+See repository `LICENSE`, `NOTICE`, and `COPYRIGHT` for complete ownership and usage terms.

{devagent_physical_engine-1.8.9 → devagent_physical_engine-1.9.1}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "devagent-physical-engine"
-version = "1.8.9"
-description = "Verification-first robotics commissioning runtime with exact-Twin evidence, qualified UR5e Gazebo/MoveIt report execution, truthful robot support tiers, selective verification, replay, regression, and FAT reporting."
+version = "1.9.1"
+description = "Verification-first robotics commissioning runtime with declarative customer report tests, case-centric evidence reuse, qualified UR5e Gazebo/MoveIt execution, exact-Twin lineage, selective verification, regression, replay, and FAT reporting."
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"
 dependencies = ["PyYAML>=6.0,<7"]
@@ -45,9 +45,10 @@ dev = [
 Homepage = "https://github.com/tomha85/devagent-physical-engine"
 Repository = "https://github.com/tomha85/devagent-physical-engine"
 Issues = "https://github.com/tomha85/devagent-physical-engine/issues"
+Sponsor = "https://github.com/sponsors/tomha85"
 
 [project.scripts]
-devagent = "devagent_physical_engine.user_cli_v18:main"
+devagent = "devagent_physical_engine.user_cli_v191:main"
 devagent-physical = "devagent_physical_engine.cli:main"
 devagent-physical-ai = "devagent_physical_engine.ai_cli:main"
 devagent-commercial = "devagent_physical_engine.commercial_cli:main"

{devagent_physical_engine-1.8.9 → devagent_physical_engine-1.9.1}/src/devagent_physical_engine/__init__.py

@@ -219,4 +219,4 @@ install_industrial_motion_v170()
 install_controller_runtime_hotfix_v181()
 install_one_command_runtime()
 
-__version__ = "1.8.9"
+__version__ = "1.9.1"