devagent-physical-engine 2.1.1__tar.gz → 2.3.0__tar.gz

{devagent_physical_engine-2.1.1/src/devagent_physical_engine.egg-info → devagent_physical_engine-2.3.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: devagent-physical-engine
-Version: 2.1.1
-Summary: Verification-first robotics commissioning control plane with immutable engineering findings, deterministic pre-site readiness, evidence authority, exact-Twin lineage, selective simulation, regression, replay, and FAT reporting.
+Version: 2.3.0
+Summary: Verification-first multi-vendor commissioning control plane with flexible guided customer-file intake, deterministic source/evidence authority, exact-Twin lineage, regression, FAT reporting, and pre-site readiness.
 Author: Tom Ha
 License: All Rights Reserved
 Project-URL: Homepage, https://github.com/tomha85/devagent-physical-engine
@@ -81,7 +81,7 @@ DevAgent turns customer engineering inputs into a bounded, evidence-driven pre-s
 
 <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>
 
-## v2.1 commissioning verification flow
+## v2.3 commissioning verification flow
 
 ```text
 Customer engineering files
@@ -125,7 +125,7 @@ That decision means the declared pre-site engineering scope has complete, curren
 Python 3.11+ is required.
 
 ```bash
-python -m pip install --upgrade devagent-physical-engine==2.1.1
+python -m pip install --upgrade devagent-physical-engine==2.3.0
 ```
 
 Verify the installed package:
@@ -137,7 +137,7 @@ python -c "import devagent_physical_engine as d; print(d.__version__)"
 Expected:
 
 ```text
-2.1.1
+2.3.0
 ```
 
 Run the normal customer workflow:
@@ -171,6 +171,107 @@ Evidence database: ~/.devagent/projects.db
 Results:           <customer-project>/devagent-results/
 ```
 
+## Flexible guided project intake
+
+**You do not need to prepare a special DevAgent project format.** Put the engineering files you already have into one customer project folder and run:
+
+```bash
+devagent verify ./customer-project
+```
+
+That is the normal workflow. `devagent verify` performs guided intake automatically before verification.
+
+If you only want to inspect what DevAgent can use, without running the full verification workflow:
+
+```bash
+devagent intake ./customer-project
+```
+
+### What files should I provide?
+
+Provide whatever is available. More current engineering sources can increase verification coverage, but there is no global mandatory checklist.
+
+Typical inputs may include:
+
+```text
+customer-project/
+├── requirements.xlsx            # optional
+├── PLC/                         # optional Siemens/Rockwell/Schneider exports
+├── Robot/                       # optional ABB/FANUC/KUKA exports
+├── cell.step                    # optional CAD / geometry
+├── FAT_results.xlsx             # optional existing test evidence
+├── calibration/                 # optional TCP / frame / calibration data
+├── drawings.pdf                 # optional engineering documentation
+└── anything_else_the_customer_has/
+```
+
+A project with only requirements can still be reviewed and normalized. A project without PLC, robot, CAD, or existing FAT evidence is still accepted; DevAgent simply limits the verification scope to what the supplied sources can prove.
+
+### Missing files do not become failures
+
+DevAgent keeps these meanings separate:
+
+```text
+authoritative evidence disproves a criterion  -> FAIL
+required evidence is unavailable             -> NOT_TESTED / reduced scope
+evidence belongs to an old project revision  -> STALE
+multiple possible current source revisions   -> NEEDS_CONFIRMATION
+unsupported file                              -> inventoried, not authority
+optional file missing                         -> no intake failure
+```
+
+DevAgent does not invent substitute evidence to make a project pass.
+
+### How source authority is handled
+
+Every raw customer file is hashed and inventoried. DevAgent recognizes common Siemens, Rockwell, Schneider, ABB, FANUC, and KUKA exports together with requirements, CAD/model files, structured engineering data, PDFs, and existing FAT/test evidence.
+
+When one source is unambiguous, DevAgent can use it automatically. Multi-file PLC or robot projects are kept as a bounded source set.
+
+If multiple distinct source sets from the same vendor could represent different revisions, DevAgent **does not guess** using names such as `final`, `latest`, `backup`, or filesystem modification time. The affected source role becomes `NEEDS_CONFIRMATION`; unrelated verification scope can still continue.
+
+For an ambiguous project, an optional `devagent-intake.yaml` can explicitly select the current sources:
+
+```yaml
+authoritative_sources:
+  requirements: requirements_rev_c.xlsx
+
+  plc_project:
+    - PLC/current_controller.L5X
+    - PLC/current_tags.L5X
+
+  robot_project:
+    - Robot/MainModule.mod
+    - Robot/ToolModule.mod
+```
+
+This file is optional. Normal unambiguous projects do not need it.
+
+### What DevAgent creates
+
+The customer source files remain read-only. DevAgent writes its own outputs under `devagent-results/`:
+
+```text
+devagent-results/
+├── SOURCE_MANIFEST.json
+├── INTAKE_READINESS.json
+├── INTAKE_GUIDE.md
+├── SUMMARY.json
+├── PRE_SITE_READINESS.json
+├── FAT_REPORT.html              # when current FAT lineage exists
+└── EVIDENCE.html
+```
+
+`SOURCE_MANIFEST.json` records hashes and source provenance. `INTAKE_READINESS.json` shows which source roles are usable or need confirmation. `INTAKE_GUIDE.md` explains optional files that could strengthen coverage.
+
+If customer files change while verification is running, the run is marked as a stale source snapshot and cannot be promoted as current readiness. Add or replace files when needed, then rerun the same command:
+
+```bash
+devagent verify ./customer-project
+```
+
+See `docs/FLEXIBLE_GUIDED_INTAKE_V23.md` for the full intake authority contract.
+
 ## Commercial commissioning workflow
 
 The normal end-to-end customer path is `devagent verify`. It performs requirement normalization, deterministic mapping, requirement-driven case planning/mapping, verification orchestration, evidence recording, regression, and reporting within the qualified scope.
@@ -500,10 +601,36 @@ export GEMINI_API_KEY="..."
 
 Provider-backed interpretation cannot grant physical truth, site qualification, functional-safety certification, or real-execution authority.
 
+### Commissioning Agent Orchestrator
+
+The default verification path now reconciles deterministic engineering review, change impact, regression, FAT, Evidence Bundle, and immutable pre-site readiness before agent reasoning.
+
+Run the bounded project-aware agent on an existing project:
+
+```bash
+devagent agent commission PROJECT_ID \
+  --provider openai \
+  --model YOUR_MODEL
+```
+
+Or point it at a customer project directory:
+
+```bash
+devagent agent commission ./ACME_CELL \
+  --provider openai \
+  --model YOUR_MODEL
+```
+
+The agent uses immutable multi-context snapshots, reviewer→critic bounded revisions, stale-context abort, full model/provider traces, deterministic recovery recommendations, and opt-in project-scoped advisory memory. It cannot grant PASS/FAIL, readiness, evidence qualification, or real execution authority.
+
+Learning is off by default. `--learn` creates only a memory candidate; explicit human promotion is required before that memory can be reused, and promoted memory remains advisory.
+
+See `docs/COMMISSIONING_AGENT_ORCHESTRATOR_V1.md`.
+
 ## Installed CLIs
 
 ```text
-devagent             one-command verification, interactive report testing, robot support/visualization
+devagent             guided project intake, one-command verification, commissioning agent, interactive report testing, robot support/visualization
 devagent-commercial  project, evidence, findings, FAT, regression, commissioning-readiness workflow
 devagent-physical    deterministic core + ROS/qualification tools
 devagent-physical-ai optional provider-backed engineering front end
@@ -513,7 +640,7 @@ devagent-physical-ai optional provider-backed engineering front end
 
 | Exit | Meaning |
 | ---: | --- |
-| `0` | bounded full verification is release-ready |
+| `0` | deterministic current project state is READY_FOR_PRE_SITE_COMMISSIONING |
 | `10` | customer input or operational contract failure |
 | `30` | more engineering information is required |
 | `31` | requested simulation is blocked/unqualified |
@@ -521,14 +648,23 @@ devagent-physical-ai optional provider-backed engineering front end
 
 # Project status
 
-**v2.1.1 — Production/Stable software workflow; accepted ABB/FANUC/KUKA simulation authority promotion**
+**v2.3.0 — Production/Stable software workflow; Flexible Guided Multi-Vendor Intake + deterministic commissioning authority**
+
+v2.3.0 makes the customer entry workflow flexible without weakening verification authority. Customers can provide the engineering files they already have instead of conforming to one mandatory DevAgent project schema. DevAgent inventories and hashes the raw sources, recognizes supported vendor/file roles, detects exact duplicates and source ambiguity, validates current intake provenance, and exposes which verification capabilities are available before the existing deterministic commissioning workflow continues.
+
+Missing files are allowed. Missing evidence reduces verification scope or remains `NOT_TESTED`; it never becomes a synthetic `FAIL` or an invented PASS. Multiple distinct same-vendor source sets require confirmation instead of being selected from filenames such as `final`, `latest`, or `backup`. Source changes during verification invalidate the current intake snapshot and block readiness until the project is rerun from a stable source state.
 
-v2.1.1 promotes exact ABB IRB1200, FANUC CRX-10iA, and KUKA KR6 R900-2 kinematic/physics/visual simulation authority from the accepted v2.1 evidence. The promotion is bound to immutable report hashes and does not grant measured FAT, hardware-shadow, sim-real, site, safety, or real-execution authority.
+The v2.2 Commissioning Agent Orchestrator remains advisory-only above the deterministic core. Existing ABB/FANUC/KUKA bounded simulation authority remains unchanged and does not grant measured FAT, hardware-shadow, sim-real, site, safety, commissioning-completed, or real-execution authority.
 
 Production-oriented software capabilities include:
 
 ```text
-one-command customer intake
+flexible guided multi-vendor customer intake
+read-only source inventory + SHA256 provenance
+optional source files; partial verification allowed
+deterministic source ambiguity / duplicate handling
+stable inventory + authority fingerprints
+source-mutation detection during verification
 XLSX/CSV/YAML/JSON requirement normalization
 immutable project/Twin lineage
 engineering review + first-class risk findings
@@ -552,9 +688,12 @@ professional FAT report
 Evidence Bundle + replay
 immutable READY / NOT_READY pre-site commissioning decision
 provider-neutral optional AI front end
+bounded project-aware Commissioning Agent Orchestrator
+immutable multi-context agent snapshots + stale-context abort
+opt-in human-promoted advisory engineering memory
 ```
 
-Production/Stable describes the bounded software workflow. The target-proven UR5e claim remains limited to the qualified packaged scope and acceptance environment. v2.1.1 does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, commissioned, or authorized for autonomous real execution.
+Production/Stable describes the bounded software workflow. The target-proven UR5e claim remains limited to the qualified packaged scope and acceptance environment. v2.3.0 does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, commissioned, or authorized for autonomous real execution. Flexible intake changes how customer artifacts enter the workflow; it does not weaken evidence authority. The AI agent remains advisory and cannot grant PASS/FAIL/NOT_TESTED, evidence qualification, pre-site readiness, or real-execution authority.
 
 Current hard authority boundaries remain:
 
@@ -569,6 +708,18 @@ unless separately proven by an appropriate qualified process.
 
 ## Documentation
 
+Flexible Guided Intake:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/FLEXIBLE_GUIDED_INTAKE_V23.md
+
+Commissioning Agent Orchestrator:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/COMMISSIONING_AGENT_ORCHESTRATOR_V1.md
+
+v2.3.0 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V2_3_0.md
+
+v2.2.0 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V2_2_0.md
+
 v2.1.1 release notes:
 https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V2_1_1.md
 

{devagent_physical_engine-2.1.1 → devagent_physical_engine-2.3.0}/README.md

@@ -39,7 +39,7 @@ DevAgent turns customer engineering inputs into a bounded, evidence-driven pre-s
 
 <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>
 
-## v2.1 commissioning verification flow
+## v2.3 commissioning verification flow
 
 ```text
 Customer engineering files
@@ -83,7 +83,7 @@ That decision means the declared pre-site engineering scope has complete, curren
 Python 3.11+ is required.
 
 ```bash
-python -m pip install --upgrade devagent-physical-engine==2.1.1
+python -m pip install --upgrade devagent-physical-engine==2.3.0
 ```
 
 Verify the installed package:
@@ -95,7 +95,7 @@ python -c "import devagent_physical_engine as d; print(d.__version__)"
 Expected:
 
 ```text
-2.1.1
+2.3.0
 ```
 
 Run the normal customer workflow:
@@ -129,6 +129,107 @@ Evidence database: ~/.devagent/projects.db
 Results:           <customer-project>/devagent-results/
 ```
 
+## Flexible guided project intake
+
+**You do not need to prepare a special DevAgent project format.** Put the engineering files you already have into one customer project folder and run:
+
+```bash
+devagent verify ./customer-project
+```
+
+That is the normal workflow. `devagent verify` performs guided intake automatically before verification.
+
+If you only want to inspect what DevAgent can use, without running the full verification workflow:
+
+```bash
+devagent intake ./customer-project
+```
+
+### What files should I provide?
+
+Provide whatever is available. More current engineering sources can increase verification coverage, but there is no global mandatory checklist.
+
+Typical inputs may include:
+
+```text
+customer-project/
+├── requirements.xlsx            # optional
+├── PLC/                         # optional Siemens/Rockwell/Schneider exports
+├── Robot/                       # optional ABB/FANUC/KUKA exports
+├── cell.step                    # optional CAD / geometry
+├── FAT_results.xlsx             # optional existing test evidence
+├── calibration/                 # optional TCP / frame / calibration data
+├── drawings.pdf                 # optional engineering documentation
+└── anything_else_the_customer_has/
+```
+
+A project with only requirements can still be reviewed and normalized. A project without PLC, robot, CAD, or existing FAT evidence is still accepted; DevAgent simply limits the verification scope to what the supplied sources can prove.
+
+### Missing files do not become failures
+
+DevAgent keeps these meanings separate:
+
+```text
+authoritative evidence disproves a criterion  -> FAIL
+required evidence is unavailable             -> NOT_TESTED / reduced scope
+evidence belongs to an old project revision  -> STALE
+multiple possible current source revisions   -> NEEDS_CONFIRMATION
+unsupported file                              -> inventoried, not authority
+optional file missing                         -> no intake failure
+```
+
+DevAgent does not invent substitute evidence to make a project pass.
+
+### How source authority is handled
+
+Every raw customer file is hashed and inventoried. DevAgent recognizes common Siemens, Rockwell, Schneider, ABB, FANUC, and KUKA exports together with requirements, CAD/model files, structured engineering data, PDFs, and existing FAT/test evidence.
+
+When one source is unambiguous, DevAgent can use it automatically. Multi-file PLC or robot projects are kept as a bounded source set.
+
+If multiple distinct source sets from the same vendor could represent different revisions, DevAgent **does not guess** using names such as `final`, `latest`, `backup`, or filesystem modification time. The affected source role becomes `NEEDS_CONFIRMATION`; unrelated verification scope can still continue.
+
+For an ambiguous project, an optional `devagent-intake.yaml` can explicitly select the current sources:
+
+```yaml
+authoritative_sources:
+  requirements: requirements_rev_c.xlsx
+
+  plc_project:
+    - PLC/current_controller.L5X
+    - PLC/current_tags.L5X
+
+  robot_project:
+    - Robot/MainModule.mod
+    - Robot/ToolModule.mod
+```
+
+This file is optional. Normal unambiguous projects do not need it.
+
+### What DevAgent creates
+
+The customer source files remain read-only. DevAgent writes its own outputs under `devagent-results/`:
+
+```text
+devagent-results/
+├── SOURCE_MANIFEST.json
+├── INTAKE_READINESS.json
+├── INTAKE_GUIDE.md
+├── SUMMARY.json
+├── PRE_SITE_READINESS.json
+├── FAT_REPORT.html              # when current FAT lineage exists
+└── EVIDENCE.html
+```
+
+`SOURCE_MANIFEST.json` records hashes and source provenance. `INTAKE_READINESS.json` shows which source roles are usable or need confirmation. `INTAKE_GUIDE.md` explains optional files that could strengthen coverage.
+
+If customer files change while verification is running, the run is marked as a stale source snapshot and cannot be promoted as current readiness. Add or replace files when needed, then rerun the same command:
+
+```bash
+devagent verify ./customer-project
+```
+
+See `docs/FLEXIBLE_GUIDED_INTAKE_V23.md` for the full intake authority contract.
+
 ## Commercial commissioning workflow
 
 The normal end-to-end customer path is `devagent verify`. It performs requirement normalization, deterministic mapping, requirement-driven case planning/mapping, verification orchestration, evidence recording, regression, and reporting within the qualified scope.
@@ -458,10 +559,36 @@ export GEMINI_API_KEY="..."
 
 Provider-backed interpretation cannot grant physical truth, site qualification, functional-safety certification, or real-execution authority.
 
+### Commissioning Agent Orchestrator
+
+The default verification path now reconciles deterministic engineering review, change impact, regression, FAT, Evidence Bundle, and immutable pre-site readiness before agent reasoning.
+
+Run the bounded project-aware agent on an existing project:
+
+```bash
+devagent agent commission PROJECT_ID \
+  --provider openai \
+  --model YOUR_MODEL
+```
+
+Or point it at a customer project directory:
+
+```bash
+devagent agent commission ./ACME_CELL \
+  --provider openai \
+  --model YOUR_MODEL
+```
+
+The agent uses immutable multi-context snapshots, reviewer→critic bounded revisions, stale-context abort, full model/provider traces, deterministic recovery recommendations, and opt-in project-scoped advisory memory. It cannot grant PASS/FAIL, readiness, evidence qualification, or real execution authority.
+
+Learning is off by default. `--learn` creates only a memory candidate; explicit human promotion is required before that memory can be reused, and promoted memory remains advisory.
+
+See `docs/COMMISSIONING_AGENT_ORCHESTRATOR_V1.md`.
+
 ## Installed CLIs
 
 ```text
-devagent             one-command verification, interactive report testing, robot support/visualization
+devagent             guided project intake, one-command verification, commissioning agent, interactive report testing, robot support/visualization
 devagent-commercial  project, evidence, findings, FAT, regression, commissioning-readiness workflow
 devagent-physical    deterministic core + ROS/qualification tools
 devagent-physical-ai optional provider-backed engineering front end
@@ -471,7 +598,7 @@ devagent-physical-ai optional provider-backed engineering front end
 
 | Exit | Meaning |
 | ---: | --- |
-| `0` | bounded full verification is release-ready |
+| `0` | deterministic current project state is READY_FOR_PRE_SITE_COMMISSIONING |
 | `10` | customer input or operational contract failure |
 | `30` | more engineering information is required |
 | `31` | requested simulation is blocked/unqualified |
@@ -479,14 +606,23 @@ devagent-physical-ai optional provider-backed engineering front end
 
 # Project status
 
-**v2.1.1 — Production/Stable software workflow; accepted ABB/FANUC/KUKA simulation authority promotion**
+**v2.3.0 — Production/Stable software workflow; Flexible Guided Multi-Vendor Intake + deterministic commissioning authority**
+
+v2.3.0 makes the customer entry workflow flexible without weakening verification authority. Customers can provide the engineering files they already have instead of conforming to one mandatory DevAgent project schema. DevAgent inventories and hashes the raw sources, recognizes supported vendor/file roles, detects exact duplicates and source ambiguity, validates current intake provenance, and exposes which verification capabilities are available before the existing deterministic commissioning workflow continues.
+
+Missing files are allowed. Missing evidence reduces verification scope or remains `NOT_TESTED`; it never becomes a synthetic `FAIL` or an invented PASS. Multiple distinct same-vendor source sets require confirmation instead of being selected from filenames such as `final`, `latest`, or `backup`. Source changes during verification invalidate the current intake snapshot and block readiness until the project is rerun from a stable source state.
 
-v2.1.1 promotes exact ABB IRB1200, FANUC CRX-10iA, and KUKA KR6 R900-2 kinematic/physics/visual simulation authority from the accepted v2.1 evidence. The promotion is bound to immutable report hashes and does not grant measured FAT, hardware-shadow, sim-real, site, safety, or real-execution authority.
+The v2.2 Commissioning Agent Orchestrator remains advisory-only above the deterministic core. Existing ABB/FANUC/KUKA bounded simulation authority remains unchanged and does not grant measured FAT, hardware-shadow, sim-real, site, safety, commissioning-completed, or real-execution authority.
 
 Production-oriented software capabilities include:
 
 ```text
-one-command customer intake
+flexible guided multi-vendor customer intake
+read-only source inventory + SHA256 provenance
+optional source files; partial verification allowed
+deterministic source ambiguity / duplicate handling
+stable inventory + authority fingerprints
+source-mutation detection during verification
 XLSX/CSV/YAML/JSON requirement normalization
 immutable project/Twin lineage
 engineering review + first-class risk findings
@@ -510,9 +646,12 @@ professional FAT report
 Evidence Bundle + replay
 immutable READY / NOT_READY pre-site commissioning decision
 provider-neutral optional AI front end
+bounded project-aware Commissioning Agent Orchestrator
+immutable multi-context agent snapshots + stale-context abort
+opt-in human-promoted advisory engineering memory
 ```
 
-Production/Stable describes the bounded software workflow. The target-proven UR5e claim remains limited to the qualified packaged scope and acceptance environment. v2.1.1 does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, commissioned, or authorized for autonomous real execution.
+Production/Stable describes the bounded software workflow. The target-proven UR5e claim remains limited to the qualified packaged scope and acceptance environment. v2.3.0 does not claim arbitrary customer cells are physically qualified, site-qualified, functionally safe, commissioned, or authorized for autonomous real execution. Flexible intake changes how customer artifacts enter the workflow; it does not weaken evidence authority. The AI agent remains advisory and cannot grant PASS/FAIL/NOT_TESTED, evidence qualification, pre-site readiness, or real-execution authority.
 
 Current hard authority boundaries remain:
 
@@ -527,6 +666,18 @@ unless separately proven by an appropriate qualified process.
 
 ## Documentation
 
+Flexible Guided Intake:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/FLEXIBLE_GUIDED_INTAKE_V23.md
+
+Commissioning Agent Orchestrator:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/COMMISSIONING_AGENT_ORCHESTRATOR_V1.md
+
+v2.3.0 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V2_3_0.md
+
+v2.2.0 release notes:
+https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V2_2_0.md
+
 v2.1.1 release notes:
 https://github.com/tomha85/devagent-physical-engine/blob/main/docs/RELEASE_NOTES_V2_1_1.md
 

{devagent_physical_engine-2.1.1 → devagent_physical_engine-2.3.0}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "devagent-physical-engine"
-version = "2.1.1"
-description = "Verification-first robotics commissioning control plane with immutable engineering findings, deterministic pre-site readiness, evidence authority, exact-Twin lineage, selective simulation, regression, replay, and FAT reporting."
+version = "2.3.0"
+description = "Verification-first multi-vendor commissioning control plane with flexible guided customer-file intake, deterministic source/evidence authority, exact-Twin lineage, regression, FAT reporting, and pre-site readiness."
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"
 dependencies = ["PyYAML>=6.0,<7"]
@@ -48,7 +48,7 @@ Issues = "https://github.com/tomha85/devagent-physical-engine/issues"
 Sponsor = "https://github.com/sponsors/tomha85"
 
 [project.scripts]
-devagent = "devagent_physical_engine.user_cli_v191:main"
+devagent = "devagent_physical_engine.user_cli_v23: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-2.1.1 → devagent_physical_engine-2.3.0}/src/devagent_physical_engine/__init__.py

@@ -35,6 +35,21 @@ from .commissioning_readiness import (
     CommissioningReadinessStatus,
     PreSiteCommissioningReadinessEvaluator,
 )
+from .commissioning_agent import (
+    COMMISSIONING_AGENT_SCHEMA_VERSION,
+    CommissioningAgentOrchestrator,
+    CommissioningAgentResult,
+    CommissioningContextAssembler,
+    CommissioningContextSnapshot,
+    CommissioningLifecycleCoordinator,
+    CommissioningLifecycleResult,
+    CommissioningReviewAgent,
+    CommissioningReviewCriticAgent,
+    CommissioningReviewCoordinator,
+    CommissioningReviewProposal,
+    EngineeringMemoryStore,
+    EvidenceAwareRecoveryPolicy,
+)
 from .controller_runtime_hotfix_v181 import install_controller_runtime_hotfix_v181
 from .engineering_findings import (
     ENGINEERING_FINDINGS_SCHEMA_VERSION,
@@ -69,7 +84,18 @@ from .one_command import (
     OneCommandError,
 )
 from .one_command_runtime import install_one_command_runtime
-from .one_command_v16 import OneCommandVerifier, SimpleVerifyResult
+from .guided_intake_v23 import (
+    GUIDED_INTAKE_SCHEMA_VERSION,
+    AuthorityGroup,
+    Capability as IntakeCapability,
+    GuidedIntakeError,
+    IntakeAnalysis,
+    SourceRecord,
+    analyze_source,
+    write_intake_reports,
+)
+from .one_command_v22 import CommissioningVerifyResult, SimpleVerifyResult
+from .one_command_v23 import FlexibleVerifyResult, OneCommandVerifier
 from .physical_motion import JointTrajectoryPoint, MotionExecutionMetrics, PhysicalMotionPlan
 from .production_authority import (
     PhysicalEvidenceRecorder,
@@ -191,6 +217,19 @@ __all__ = [
     "COMMISSIONING_READINESS_SCHEMA_VERSION",
     "CommissioningReadinessStatus",
     "PreSiteCommissioningReadinessEvaluator",
+    "COMMISSIONING_AGENT_SCHEMA_VERSION",
+    "CommissioningAgentOrchestrator",
+    "CommissioningAgentResult",
+    "CommissioningContextAssembler",
+    "CommissioningContextSnapshot",
+    "CommissioningLifecycleCoordinator",
+    "CommissioningLifecycleResult",
+    "CommissioningReviewAgent",
+    "CommissioningReviewCriticAgent",
+    "CommissioningReviewCoordinator",
+    "CommissioningReviewProposal",
+    "EngineeringMemoryStore",
+    "EvidenceAwareRecoveryPolicy",
     "CommissioningEvidenceGraphBuilder",
     "CommissioningEvidenceViewer",
     "VerificationScopeAuthority",
@@ -206,6 +245,16 @@ __all__ = [
     "OneCommandError",
     "OneCommandVerifier",
     "SimpleVerifyResult",
+    "CommissioningVerifyResult",
+    "FlexibleVerifyResult",
+    "GUIDED_INTAKE_SCHEMA_VERSION",
+    "GuidedIntakeError",
+    "IntakeAnalysis",
+    "SourceRecord",
+    "AuthorityGroup",
+    "IntakeCapability",
+    "analyze_source",
+    "write_intake_reports",
     "COMMERCIAL_INTELLIGENCE_SCHEMA_VERSION",
     "CommercialIntelligenceRecorder",
     "CriterionProposal",
@@ -249,4 +298,4 @@ install_industrial_motion_v170()
 install_controller_runtime_hotfix_v181()
 install_one_command_runtime()
 
-__version__ = "2.1.1"
+__version__ = "2.3.0"