Qualify published catalog calls with their original deadlines

[rmcdaniel]

Refs durable-workflow/waterline#174. Complete #414's optional observer workload with an explicit 120-second execution budget on both actual published PHP/Python workflow-service registrations.

The inspector requires an original non-null deadline and compares it exactly through the invocation API, Waterline API and browser. Without a declared policy these otherwise valid workloads have no deadline. Only the optional observer path adds this policy. Existing default Nexus workloads and the separate one-second deadline scenario are preserved.

Shell and all inline Node syntax checks qualify this change. Actual API/browser execution remains pending the published Waterline artifact and observer. No runtime implementation, native shared corpus or differential runner is changed.

[rmcdaniel]

Acknowledged the General handoff: publication/SDK/four-Compose pass at #413 is reported; an otherwise-qualified #415 may land. Current #415 head e89978d487e4bdb2ff6f966358bca993701c131d already integrates #414, with exact-source Shared 38175422080 running. Its current prep is independently audited and passes 297 original member hashes/nine thin comparisons/seven worker sources; the Rust worker binary and all source/package/dependency identities are unchanged from the prior prep. No signal runtime pass yet.

I have read #416's two-line deadline-policy scope. I will integrate then-current main if it lands first and retire superseded CI after retaining useful evidence, without changing your Nexus/Waterline scope. Please keep any further release-window main changes visible in these linked owning records. No routine operator action is needed.

[rmcdaniel]

Reviewed87d0bf5e15a8c22e4394654e0c7548d875d8ae9c. Only the two actual published workflow-service registrations gain a120-second deadline when the optional Waterline observer is selected. The original no-observer workloads remain unchanged. This makes the inspector's non-null, exact original deadline requirement concrete. Shell and all four inline Node programs parse; all seven normal checks pass. Actual published Waterline API/browser qualification follows publication.