Repository navigation
P0: Redesign the Rust SDK documentation using One Identity #216
Description
Priority: P0, explicitly requested for the redesign. Accountable repository agent: sdk-rust. General coordinates the shared identity and cross-repository delivery.
The current product presents different identities across its sites. Implement the supplied redesign so users retain one product identity while moving between the main documentation, Python, Rust, PHP, Cloud and status surfaces.
Design authority
- One Identity redesign.
- Supplied eight-page
Durable Workflow — One IdentityPDF, SHA2565a71d08636a1e2714e8dd4b6561ce0a619453c842de4de647cc3e345f7706e50. - This repository's exact reference:
Rust.dc.html, SHA256fc59d03d129615d069437f00c3314637bc0d85ad124417ff2aa617233de42a68. The verified original export and shared identity export are being handed to the assigned agent through the existing private artifact channel; do not put private storage/workspace details into public source.
Scope and acceptance
Repository acceptance:
- Implement the Rust hero with published-version/runtime/toolchain facts, API-primary and SDK-guide actions.
- Implement the three-step toolchain / cargo add / authoring-surface section with the existing runnable typed, local-activity and bounded-sticky examples.
- Implement the Self-hosted Server / Managed Cloud runtime ownership cards and the shared documentation/reference chrome, replacing the DW square and independent language palette.
- Preserve generated Rust API/docs links, current published crate/toolchain compatibility, install commands and no-account self-hosting. Design work is independent of the held#191/Replay refuses a condition chain whose orphaned duplicate open later times out (sdk-php#283 shape, pre-existing) #192 installed operations; it neither retries their blocked review nor admits lifecycle/runtime work.
Implement the supplied One Durable Workflow redesign faithfully in this repository's existing site components. The exported HTML is a visual specification; its support.js and bundled React runtime are reference-viewer files, not production dependencies.
Shared acceptance:
- Use the unchanged canonical flowchart SVG, original colors/proportions, and
Durable Workflow / <surface>lockup. Surface names are lowercase JetBrains Mono in Durable Green; dark mode uses Mint and the logo's Paper chip (8px radius, 4px padding). Remove the competing DW/generic marks. - Apply the same light-default, dark-opt-in palette, Space Grotesk600 headings, Inter400/500/600 text and JetBrains Mono code/labels. Keep code blocks Ink in both themes, 6px/44px actions, 8px bordered cards, the reference spacing/hierarchy, and status-only amber/red/blue.
- Use the common Docs / SDKs / Cloud / Pricing / Status navigation, keyboard-accessible Python/Rust/PHP SDK switcher, current-surface treatment and contextual CTA. Keep the four-column Brand / SDKs / Run / Project footer. Its linked status pill must reflect accepted current status or an honest unknown/stale state; the mock's static green text is not health evidence.
- Keep working URLs, page anchors, search, API/reference navigation, compatibility and legal links. Make the layout work at desktop, tablet and narrow mobile widths, with keyboard/focus/contrast, semantic landmarks and working copy controls; code scrolling stays inside its block.
- Use actual published package/support facts and real service data. The mock's versions, example output, dates, prices and health percentages are not new release, support, billing or availability authority.
- Return an ordinary draft PR, current-head required checks, built-page screenshots in both themes at representative desktop/mobile widths, functional link/copy/navigation checks, and the actual deployment/live verification through the repository's existing protected flow. Preserve current operating, publication and credential boundaries.
Shared identity lead and canonical token/asset acceptance: durable-workflow/durable-workflow.github.io#483. Match that issue and the supplied identity artboard; report concrete inconsistencies without blocking independent source work.
Activity
rmcdaniel commentedon Nov 5, 2026
Implementation and built-page review are now in #217, current source
dfdea6e. The shared logo/fonts/tokens, landing onboarding/runtime cards and generated API chrome are implemented. The final shared status client is exact Git blob2659eae6410ddbc595c67e414e37ede75074cbc7; all 14 behavioral controls pass.Actual Chrome 156 preview passed 126/126 checks at 1440/1024/390/320 in both themes, including copy, keyboard/focus, SDK and API navigation/search, all local fonts, overflow, action/API-code contrast and synthetic status/expiry. Screenshot review found and fixed mobile footer label inheritance and light API command backgrounds. Eight representative screenshots plus source/build binding are retained. The canonical social PNG is regenerated at 1200×630. Browser/server/profile cleanup and independent absence checks passed.
The existing published-source split is retained: current docs/tooling with SDK 4.12.0 source
4b2440a5618ccc1c98960ea2e1e62127042c3590and approved crate checksum. Current-head normal checks are running; sdk-rust owns their completion, normal merge, original main results and the sole automatic protected Pages artifact/deployment/live receipt. Footer screenshots explicitly use synthetic unknown, not live health. Real cross-origin status acceptance remains dependent on Cloud's existing-feed CORS delivery, already requested from its owner. #191/#192's separate operating/review stops are unchanged.rmcdaniel commentedon Nov 5, 2026
Normal integration and protected styling delivery are complete. Main is
581b1fcfe965d8961d77d4015c2f9acfbb59c207, treec15482767e6a56c87ea6ca616a625b9c4abbd04d, ordered parents[933f5a2164b61861eb63e80162e05722a9c3d9ad, dfdea6e8a45c8a69e9bf8f9d9637f2b69203f096]. The merge tree exactly matches the checked source. Original main CI 42123063866, Sonar, public boundary and all four CodeQL analyses passed; all current main checks are terminal with two intended worker-qualification skips. No original attempt was rerun or relabelled.The sole automatic protected Pages run 42123063811 passed. Deployment
7587195397is success at2026-11-05T22:38:49Z. Pages artifact13460107751is 4,199,657 bytes / SHA-256d6cbc6c4ea8f02dfc72d5ff636194ca5d87e05dd74cb9a2817fb28bc767bd1ee, with 495 regular files. Published identity remains SDK 4.12.0, source4b2440a5618ccc1c98960ea2e1e62127042c3590, approved crate620a8287af73c363dac61f0a91f20971a39f3b8cdc9513fbea85cdbd95a74ba4; tooling is the actual main merge. Candidate-to-Pages differences are the tooling manifest, configured public analytics, rustdoc help/settings' stable-example current-crate context, and the uploader's omitted hidden marker/lock files. Generated API content and checked presentation are preserved.At
22:41:02Z, 14/14 anonymous HTTPS files byte-matched the deployed artifact: build manifest, landing, API root, layout/navigation/status adapter and module, logo/favicon, social PNG, tokens and all three fonts. The live landing and API also passed an actual Chrome 156 readback, with correct stable/source/tooling identities, shared chrome, default light theme and no page errors. Browser/profile cleanup and independent process absence passed. The merged source branch was deleted locally and remotely; remote absence was independently verified.#216 remains open for its real status-feed happy path. At
22:40:11Z, the actual live Rust-origin browser request failednet::ERR_FAILEDand the footer correctly showed “Status unknown.” An earlier anonymous Origin-bearing GET returned HTTP 403/no ACAO. No outage/WAF cause or operational assertion is inferred. The live Rust document has no restrictive CSP header. Synthetic status/expiry controls remain separate from live evidence.Cloud owns delivery/readback of the existing exact-five-origin public GET CORS/read correction, as recorded on shared #483 and Security's canonical-origin finding; its owner has been asked directly. The formerly missing central catalog pin is already merged in central #311. After Cloud returns its actual producer receipt, sdk-rust owns one targeted live-origin status acceptance and #216 closure. This does not select any Cloud production operation or change #191/#192's separate stops.
rmcdaniel commentedon Nov 6, 2026
The independent business replay-clock source PR #218 is normally integrated at actual main
e4d0f3f; its terminal main/automatic stable-docs receipt is complete. Protected run42133925609, deployment7588607265, Pages artifact13464108728(4,199,675 bytes / SHA-2561e221ea59e569ebb52f274b61a92a88f2f73e09f509162f14287c9104d2681c4) are accepted. All 495 paths are preserved; only tooling manifest and help/settings current-example context differ. All presentation/API/status/font/logo bytes remain identical; 16/16 raw HTTPS files matched at2026-11-06T00:07:24Z. Published SDK remains 4.12.0/source4b2440a, with the original checksum. Docs has the exact new tooling/artifact identity.Remaining next action / owner: Cloud must finish the existing public-current GET five-origin source/publishing prerequisite and return its actual protected deployment plus canonical-origin ACAO/read receipt. Cloud #629's current owner record explicitly says the publisher remains disabled and the live predecessor has no five-origin CORS grant; its narrow prerequisite is #630. I read that current record and asked Cloud for the actual receipt/concrete remaining gate, without duplicating source or starting a publication. General retains the distinct effect decision.
sdk-rust owns one targeted actual Rust-origin browser happy-path check and #216 closure after that producer handoff. Existing truthful unknown behavior and synthetic fixture acceptance carry; they do not establish live success. No new status probe/browser matrix or producer operation was launched in this reconciliation. #191/#192's separate policy-access/installed stops remain unchanged.
rmcdaniel commentedon Nov 6, 2026
The independent child-clock source #219 is normally integrated at actual main
ccb1074; terminal main/docs/cleanup receipt. Sole protected docs run42138689802, deployment7589210084, artifact13466489796(4,199,683B / SHA-2565beeec48e1f50fcd6bb59b7f6df84f463c64656fc6c9ef2a2fdc0e4421f3f034) passed. All495 paths are preserved; only tooling manifest and help/settings current-example context differ. Presentation/API/status/font/logo bytes are unchanged; 16/16 live HTTPS matches at2026-11-06T00:44:35Z. Published SDK stays4.12.0/source4b2440awith its approved checksum; Docs received the immutable handoff.Current external next action / owner: Cloud. I reconciled current #630 rather than carrying the old draft/tool blocker: the producer-only source is now normally merged, and the installed-browser prototype is separate. General has identified a concrete producer-side freshness-projection correction that must land before the distinct protected publication decision. Cloud owns that correction/current-head proof and then the actual five-origin GET CORS/publication receipt. I directly asked Cloud for the changed producer/live handoff after those inputs, without duplicating its source or starting an effect. Source integration is not a live ACAO grant.
sdk-rust owns the targeted actual Rust-origin browser happy-path check and #216 closure after Cloud's deployment/read receipt. Existing truthful unknown fallback and synthetic fixture acceptance remain valid, but do not close the live tail. No new status probe/browser matrix, producer publication or change to #191/#192's separate stops occurred in this reconciliation.
rmcdaniel commentedon Nov 6, 2026
Cloud's producer/CORS and freshness-floor source correction is now accepted on merged
0369b7c7e90b458ced5278dc33837f139abdab59; its original main qualification passed118/118 tests and both dry-runs. I reconciled the current owning publication packet rather than retaining the superseded source-fix blocker.Next action / owner: General must confirm the unchanged required inherited protected inputs with an existing authorized metadata reader, or return a separately bounded protected-input disposition, before selecting Cloud's one-original publication. My own bounded read-only organization-metadata request also returned HTTP403; that establishes unavailable metadata for this reader, not absent secrets. No values were read and no authorization scope, credential or configuration was changed.
Cloud owns the original protected publication and actual five-origin GET/CORS/data readback after that decision. The publisher remains disabled and no deployed five-origin receipt exists. sdk-rust owns the targeted actual Rust-origin hydration check and #216 closure immediately after that handoff. The accepted stable4.12 site, canonical shared consumer and truthful fallback are unchanged. No browser/status probe or producer operation was started from this source-only checkpoint.
rmcdaniel commentedon Nov 6, 2026
The independent scalar-signal clock #220 is integrated at actual main
e76ec31; terminal main/docs/live/cleanup receipt. Sole protected run42149116739, deployment7590555265, artifact13471009246(4,199,719B / SHA-2565997ad5dd32f1dc4c114fff3acb4524791dccd56f38b71a702e250a75f3a93b8) passed. All495 paths are preserved, and only tooling manifest/help/settings current-example metadata differ; presentation/API/status/font/logo bytes remain identical.16/16 raw HTTPS matches completed at2026-11-06T02:20:33Z. Published SDK remains4.12.0/source4b2440awith the approved checksum. Docs has the immutable handoff; prior P0 functional/visual acceptance carries.Current upstream next action / owner: Cloud. The previous inherited-input metadata gap has a new concrete source route: General selected a narrow publisher successor that preserves the existing provider alert bindings and validates their metadata using the actual job credential before the first provider write. The producer source/effect packet must prove preservation across its existing deploy stages and unconditional workflow disable/readback, then receive General's distinct one-original publication selection. I read the latest owning #630 decisions and requested the resulting actual producer/data/five-origin CORS receipt from Cloud. I did not repeat organization-secret queries, refresh authorization, change a secret or select a diagnostic/publication operation.
sdk-rust owns the targeted actual Rust-origin browser hydration check and #216 closure immediately after that deployed producer receipt. No deployed five-origin receipt has been returned yet. The current truthful unknown fallback remains correct; fixture/source acceptance and the other SDK's Pages publication do not establish this site's live status success. #191/#192's separate private/installed stops remain unchanged.
rmcdaniel commentedon Nov 6, 2026
The producer dependency has an actual terminal result. I read Cloud #293's current authoritative incident record: the sole selected original publisher42153199012/attempt1 is NONPASS/consumed after deployment, at independent
probe_unverified; final endpoint verification was skipped. The publisher was restored todisabled_manually, with independent readback at2026-11-06T02:57:04Z. This supersedes the earlier pre-publication input wait, without relabelling the original outcome.Next action / owner: Cloud owns urgent monitoring-verification diagnosis, a concrete forward-repair proposal and actual recovery/corrected producer/data/CORS receipt on the existing incident. General owns any distinct next effect decision. No application/workflow-runtime downtime is established by this monitoring gap. Deployed source alone is not live-health or CORS acceptance, and #216 remains open/blocked.
sdk-rust owns the targeted real Rust-origin hydration check and closure after that corrected receipt. Per the incident direction, I started no new browser/status probe, caller workload, publisher retry, host/native operation or scope change. The accepted stable4.12 documentation delivery and truthful fallback remain unchanged; no synthetic operational assertion or duplicate producer action is introduced. #191/#192's separate stops remain intact.
rmcdaniel commentedon Nov 6, 2026
The remaining real published-origin status path passes. #216 is complete.
At
2026-11-06T04:13:50.365Z, the actual published Rust landing fetched the restored public feed and rendered “All systems operational”. This used the deployed page's own unchanged status adapter/module, without fixtures, request interception, substituted Origin or edited DOM.https://rust.durable-workflow.comVary: Origin; no credentials grantdurable_workflow.status_page_snapshot.v1, generated04:13:01Z, checked04:13:00Z, fresh/age50s/900s ceiling, status/alertok/okoperational, validUntil04:28:00Z; linked to the public status page9cd27bea596fdf4ddd2349caffdbd69f3096e100fb0b852bc3b731f50366af8bThe check ran04:13:47.134–04:13:50.660Z on the retained actual Chrome156.0.8078.80 / public Playwright1.62.1, using one fresh anonymous profile/page. Canonical consumer Git blob
2659eae6410ddbc595c67e414e37ede75074cbc7was SHA-verified. The live manifest binds published SDK 4.12.0, source4b2440a5618ccc1c98960ea2e1e62127042c3590, approved crate checksum620a8287af73c363dac61f0a91f20971a39f3b8cdc9513fbea85cdbd95a74ba4, tooling/current maine76ec3164261bd06285b8c4971fb61acf0fb8f6a.This closes the only remaining tail after #217's implemented/qualified design and the current original-main/495-file Pages/artifact/live receipt. The earlier126-check light/dark responsive/keyboard/copy/API baseline, canonical logo/fonts and published-source split remain accepted. No new build, publication, installer, Server/SDK-runtime or broad browser matrix was needed.
Cloud's actual restored-data/CORS handoff supplies the producer prerequisite. The original producer attempt and repair-helper NONPASS outcomes remain preserved; this Rust-origin success does not relabel them or select another effect. Browser/controller exited0 in4.73s, stderr0, no forced cleanup. The temporary profile is removed and an independent exact-owner process scan is empty; the resource claim is released. Live capture SHA-256
a69feb8707f24edd21e8f8174e4fe21d21a7a8f719bfbbb1417934242b9876a3and sanitized resultd25b8af94eb370c7e690eca8fa03a1991f6a5d2e7f036bfb37edbd3e8d37d996are retained for seven days for review. #191/#192 and central replay-clock work remain separate.