[rmcdaniel]

The PHP portal and generated API currently use separate dark themes and a competing mark. This applies the supplied One Identity design in the existing Eleventy/phpDocumentor components: unchanged canonical logo, shared light/default and dark/opt-in palette, canonical self-hosted fonts, keyboard SDK switcher, PHP entry cards, runtime ownership panels and four-column footer.

The footer reuses Docs #484's exact shared public-status reducer/watch module with bounded labels, freshness expiry and lifecycle cleanup. Cloud owns live CORS acceptance; source browser fixtures do not assert service health. The mock's versions and success/health claims are not publication authority.

Stable docs can select an exact accepted-main presentation commit while API code, examples, contracts, support floors and guide bodies remain on the published SDK source. Both rendering engines share the presentation shell; the artifact records selected/published SDK, presentation and workflow revisions. A build-only dispatch qualifies that tuple before a separately authorized deployment through the existing Pages environment. No package/runtime/credential or release operation is added.

Validation: actual local portal + 386 API pages generated; 404 rendered pages/18 guide destinations and contract-derived commands/examples/links checked; 56 current and 28 historical browser theme/viewport cells passed; 19 existing release-channel + seven presentation-isolation/binding + 14 shared status + four link tests pass; canonical logo/fonts/licenses verified. API search interaction passed locally; fresh normal current-head CI is running against the consolidated shared known-UTC contract. Screenshots are emitted as normal CI artifacts. Initial failed documentation/quality findings are corrected in the successor and are not counted as passes.

Remaining acceptance: current-head required checks, stable 3.9.4 rendered tuple, affected publication-path acceptance, protected deployment and actual live readback. Unpublished 3.10/combined-minor gates, #219 exclusion and #267 separation are preserved.

Refs #315; shared identity durable-workflow/durable-workflow.github.io#483. Publisher input/effect record: #315 (comment)

[rmcdaniel]

The source successor now adopts the shared strict calendar correction from Docs #484 at a0e8e8e392e49cac9341cf44a9417517d7c76611 without a local reducer fork. 13/13 shared status controls pass, including impossible dates, 24-hour normalization, offsets/subseconds, freshness expiry and request cleanup. The logo and three WOFF2/font-license pairs match the canonical hashes.

Local qualification passed 56 current-design browser cells plus 28 historical-layout cells, actual API search/open/close, exact clipboard copying, keyboard SDK switching and three browser-evidence controls. Rendered contrast samples on the home page and Client API page passed in both themes: minimum 4.977:1 across the sampled text. Desktop/mobile screenshots cover home, first workflow and API in both themes. These are source previews; their unreleased-source badge is not published SDK authority. Stable 3.9.4 rendering remains an explicit publisher check.

Normal CI exposed and fixed actual source/tooling defects, including legacy mobile check order and the preview server's filesystem boundary. Browser serving now selects only preloaded bytes from the fixed build/site inventory; request paths cannot perform filesystem reads or metadata probes. The predecessor's direct Sonar read reached zero; fresh checks are running for the calendar successor.

Actual publishing remains separate. CLI confirms the central setup interface exists at .github 18783be6bef737cc778e4c7282a8797e39daa61a, but its first qualification stopped in the existing pip predecessor, before PHP/PHAR setup. CLI owns the central correction (current dependency); no per-repository repair is selected. The next allowed SDK action is normal source integration after fresh required checks, then the exact build-only stable tuple. No deployment/tag/release has occurred.

[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 head 6acfa418885dd0b1e7ee8697f04c5193e1903196 has one runner-blocked historical compatibility cell, not a rendered-page failure. Job 127573855719 reached its existing 15-minute bound at 22:41:34Z while Playwright's dependency installation downloaded 21.1 MB of Ubuntu font packages from the runner's configured Azure archive mirror. The 7.5 MB CJK font download stalled/repeated; the browser tests never started. Other source/current and published-tag documentation cells succeeded on the same head.

I am making one normal failed-job rerun on that unchanged head and workflow, including its dependent required qualification. The original cancelled attempt remains recorded; there is no local-provider substitution, waived check, changed timeout, mirror override or publication operation. If acquisition fails again, I will retain both nonpasses and escalate the hosted infrastructure dependency rather than loop retries.

[rmcdaniel]

Source integration is accepted on actual main a4315bc, tree 7ce9a26c7d30f0bb67199b83f615d5fc5667cfc7, ordered parents 3716c192 + reviewed 6acfa418. Git/GitHub agree; product source, examples, resources, configuration and Composer identity are unchanged from the prior main.

The PR has 42 terminal checks: 41 success + one intended connected skip. Its first historical cell was runner-blocked by font acquisition; the one unchanged-head failed-job rerun passed, with the original cancellation retained. Resulting main has 42 terminal checks: 40 success + two intended skips. Main CI passed. Portal preview built successfully and deployment was skipped. Direct Sonar has no open findings.

Current-head visual artifact 13460175484, SHA256 9e4cc46a2f67878ab2ac5e32ce52a493fb40d307a3abbe2f9e1d08d04587cd4c, was downloaded/hash-verified. It contains the representative desktop/mobile, light/dark screenshots. The canonical shared status source is f8198fa2, with 14 targeted controls. Main's automatic preview remains source preparation, not a 3.10 publication. Live audit still selects 6a821568, SHA256 43c0159fc3ee9317a32e644e20d61d47d2fbf64d23194efe7b8e1f2b86514cd1.

The exact owned branch was clean, fully merged, unchanged remotely and had no dependent PR; remote/local cleanup is complete and GitHub absence verified. The detached accepted checkout is retained.

Next is one build-only stable presentation candidate using the existing workflow at main a4315bcd: stable_tag=3.9.4, unchanged-product stable_source=6a821568db5c72983bd3990fe27c7990f092db12, presentation_source=a4315bcdf62b4a8466c25bd007a9a9d6b06d1f45, build_only=true. Its effects are source rendering/checks and review artifacts; Pages deployment is disabled by that input. Local cached-tool rendering already passed 393 page/link/metadata checks and retained 3.9.4's badge/install contract with 3.10 onboarding absent. This is not installed-SDK or publication evidence. Actual deployment remains held on the named central #297 qualification/adoption boundary; no tag, release, runtime or credential effect is selected.