Loading src/tests/ecoc26-hyr-agentic-optical/README.md +11 −10 Changes for src/tests/ecoc26-hyr-agentic-optical/README.md: 11 added lines, 10 removed lines. Original line number Diff line number Diff line Loading @@ -89,10 +89,10 @@ Offline regressions are in `src/agentic/tests/test_local_optical.py`. - Prompt eight (service/path inspection) exposed a wrapper passing `scope` to a neighbor-query function without that argument. The function now honors local/remote/all scope; a regression covers the actual model-facing wrapper. All 24 Agentic tests pass, and the fixed image is deployed locally. - The full Anthropic post-fix conversation, including bidirectional creation and teardown, remains pending. Earlier deterministic MCP lifecycle tests are not a substitute for that conversation test. Regression coverage exercises this wrapper and its scope handling. - Validate the complete conversation, including bidirectional creation and teardown, with the provider selected for the demo. Deterministic MCP lifecycle tests do not substitute for that conversation test. - Removed the interrupted replay's test service through TFS-API and verified the service inventory was empty. Replay transcripts are local temporary files `/tmp/ecoc-live-prompts.json` and `/tmp/ecoc-live-prompts.log`; Loading Loading @@ -124,9 +124,10 @@ Observed request times were 6.84 s for unidirectional creation, 8.60 s for its deletion, 10.41 s for bidirectional creation, and 13.37 s for deleting both directions. These are single-run functional checks, not performance results. Controller caveat: after baseline teardown, Context still reported occupied slots on the removed service's links while Optical Controller deletion logs reported those slots as available. Subsequent provisioning succeeded, but that does not validate Context spectrum synchronization. Investigate that controller behavior separately before demonstrating authoritative spectrum release. No controller-spectrum fix is included in these Agentic changes. ## Spectrum Validation Compare the released slots in Context with Optical Controller's spectrum state after teardown, following the checks in `src/opticalcontroller/README.md`. Successful subsequent provisioning or an empty service inventory alone does not prove spectrum synchronization. Preserve allocations belonging to other services, and reconcile stale occupancy from earlier deployments separately. Loading
src/tests/ecoc26-hyr-agentic-optical/README.md +11 −10 Changes for src/tests/ecoc26-hyr-agentic-optical/README.md: 11 added lines, 10 removed lines. Original line number Diff line number Diff line Loading @@ -89,10 +89,10 @@ Offline regressions are in `src/agentic/tests/test_local_optical.py`. - Prompt eight (service/path inspection) exposed a wrapper passing `scope` to a neighbor-query function without that argument. The function now honors local/remote/all scope; a regression covers the actual model-facing wrapper. All 24 Agentic tests pass, and the fixed image is deployed locally. - The full Anthropic post-fix conversation, including bidirectional creation and teardown, remains pending. Earlier deterministic MCP lifecycle tests are not a substitute for that conversation test. Regression coverage exercises this wrapper and its scope handling. - Validate the complete conversation, including bidirectional creation and teardown, with the provider selected for the demo. Deterministic MCP lifecycle tests do not substitute for that conversation test. - Removed the interrupted replay's test service through TFS-API and verified the service inventory was empty. Replay transcripts are local temporary files `/tmp/ecoc-live-prompts.json` and `/tmp/ecoc-live-prompts.log`; Loading Loading @@ -124,9 +124,10 @@ Observed request times were 6.84 s for unidirectional creation, 8.60 s for its deletion, 10.41 s for bidirectional creation, and 13.37 s for deleting both directions. These are single-run functional checks, not performance results. Controller caveat: after baseline teardown, Context still reported occupied slots on the removed service's links while Optical Controller deletion logs reported those slots as available. Subsequent provisioning succeeded, but that does not validate Context spectrum synchronization. Investigate that controller behavior separately before demonstrating authoritative spectrum release. No controller-spectrum fix is included in these Agentic changes. ## Spectrum Validation Compare the released slots in Context with Optical Controller's spectrum state after teardown, following the checks in `src/opticalcontroller/README.md`. Successful subsequent provisioning or an empty service inventory alone does not prove spectrum synchronization. Preserve allocations belonging to other services, and reconcile stale occupancy from earlier deployments separately.