Correct browser and Nexus SDK execution coverage

[rmcdaniel]

Change

Update the child-workflow and principal-attribution inventory rows to reflect the connected published Waterline browser coverage already executed by Sample App's child runner. Remove the two stale statements describing it as missing.

Correct the Nexus row after reading the built-in shard. PHP → Python uses the installed PHP SDK client. The scenario labeled Python → PHP invokes from Node HTTP after reflecting Python's caller API, and both cells assign workflow/run IDs without executing those workflow workers. Document the actual remaining SDK caller and workflow recovery cases explicitly.

The executable scope is 45 parent/child desktop/mobile views across five Rust-involving cancellation directions and three access modes. Actual HTTP responses and rendered evidence must match original Server/SDK identity, requester, deadline, delivery, recovery and completed cleanup. Browser time remains outside the cleanup measurement. Other child semantics retain their separate qualification gaps.

Verification

Read the current runner and browser assertions. Sample #194 delivered this case with 45 real PR views and 45 independent main views. Normal repository checks will run. This inventory states executable scope, not a passing result for every release tuple.

Part of #122. Changes only the inventory documentation.

[rmcdaniel]

Reviewed exact head 17abf6bdf49b6ed7af23dd02a3b56306299912c0 against current main bab5b3271ddd15cc676058972647c392472e7dae.

Only three inventory rows change. The child/browser statements match the existing runner, all three access batches and the actual selected-run/rendering assertions. The Nexus correction matches the current invocation code and preserves the distinction between a real PHP SDK client, Node HTTP, Python API reflection and durable caller workflows. Required remaining semantics stay explicit. No code, fixtures, policy, credentials or release metadata changes.

The normal Shared contract tests pass on this exact head. Existing 45-view PR/main qualification links support the browser scope without claiming every future tuple is qualified.

[rmcdaniel]

Merged at d3f2ebb with the exact qualified tree. Shared contract tests pass on PR and main. The completed remote branch is deleted. The inventory now reflects connected browser execution and clearly separates Nexus HTTP/reflection probes from actual SDK caller and workflow execution.