[rmcdaniel]

Interim documentation for the product work in shared #215. Website #302 is superseded by that advancing replay-safe clock requirement; this PR does not deliver or replace it.

Explain released Python 2.6.1's persisted run-start clock, durable waits/deadlines, elapsed-time measurement and sequence-based ordering. Distinguish embedded PHP's event-advancing clock from PHP service-mode/Rust APIs. The final product semantics and replay-compatible migration remain acceptance of #215.

Normally installed Python 2.6.1 passes the new timer example and seven focused constructed-history controls in each of two independent replay processes. Loaded module bytes match the immutable release. This is replay/source evidence, not a live Server timing comparison. Published Core 2.7.2 source was also checked.

All seven website translations and their individually reviewed source hashes are complete. Focused example/anchor/review checks pass. The verified example matches SDK-Python #169. Only the Python guide, its translations and their review keys change; no runtime, package, protocol or version changes.

General retains exact-source integration, rendering and publication acceptance. Publishing this current-behavior clarification must not close shared #215.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Current-main integration checkpoint: head 4db8194f55e1bb8afa6158f2e20cec2b444f190e, tree e28a3537e7c6466423eb20d15f9732d4cae3e56f, incorporating main f54f349db35070aba22b8968b94c566a4118eeb5. The final diff remains exactly the Python guide, seven translations and their seven review keys. The merged locale UI and translation-checker corrections are preserved.

Focused Node24 verification passes all six translation-gate controls, the complete 102-guide inventory/review/code-block checks, and exact equality of the verified clock example across English, all seven translations and SDK-Python #169. The read-only tool container is removed; no dependencies or runtime fixtures were created.

Fresh Sonar workflow 39396889780 and the app check pass; the public issue API reports zero unresolved PR issues. Other normal checks are still queued, so this is not final whole-PR acceptance. SDK-Python #169 retains its separate all-passing checks at 321819ecd1db91b753d0517a448787baaeb5683e.

This documents released behavior only. Shared #215 remains open for the advancing replay-safe clock and its compatibility requirements; publishing these docs does not complete that feature or reopen Website #302 as a documentation-only substitute.

[rmcdaniel]

Published acceptance for this interim released-behavior documentation is verified.

• Merge 240947a, whole tree e28a3537e7c6466423eb20d15f9732d4cae3e56f, exactly the reviewed candidate tree. Remote docs/python-workflow-clock-contract head is retired.
• All 7 exact-main checks PASS, including normal documentation qualification 39404723754 and build/publish 39404723695. The actual Pages run 39407740654 also passes build/deploy/report.
• Published static commit 0c6d0d0 records deploy: 240947a31bb2df0699a5b46506a09e4274806ac8.
• At 10:41:22 UTC, all 8 public Python-guide routes return HTTP 200 with the correct HTML language, the translated time/SDK-difference headings, both stable section anchors and WaitWithoutClockLoop. This is actual HTTP/content acceptance, not a new browser-layout claim.
• The separate SDK portal publication receipt verifies exact merged source 412a10fa, live portal audit/example and all 15 fresh-main checks PASS.

The published behavior remains a fixed Python run-start clock. .github #215 is still OPEN for the actual advancing-clock feature; Website #302 is superseded, not a delivered feature.

Main has subsequently advanced through separate PR #309 at 343b7b8. Its combined deployment is still pending; none of the above passes is transferred to that newer source. The next publication check will preserve both guides.

The small read-only Node24 HTTP reader auto-retired immediately at 10:41:22 UTC; it had no writable source/dependency/raw mounts. Earlier task resources remain retired; no application runtime, paid host or new workflow qualification was started.