[rmcdaniel]

Draft. Merge alongside the CLI 2.5.0 release. Today's stable CLI (2.3.6) still ships dw.phar, so the text is worded "From CLI 2.5.0". The gh release download commands use %%artifact.cliVersion%%, so they pick up 2.5.0 once the manifest selects it.

Change (all eight languages)

• polyglot/cli.mdx:
  • The "PHAR (portable, requires PHP 8.2+)" download block becomes "Moving from dw.phar", with the General-approved text from cli's docs/release-notes/2.5.0.md (lobby 7988):
    • switch to the standalone binary with the shell or PowerShell installer above (the site's existing installers), then delete dw.phar; the installers check SHA256SUMS;
    • the no-pipe path: gh release download plus verify-release.sh --attest plus install;
    • the full Windows no-script block from cli#85: hash check, gh attestation verify, Copy-Item;
    • a 2.x PHAR's dw upgrade still prints "Download the matching PHAR manually" (it comes from the old release), and standalone installs upgrade with dw upgrade.
  • dw upgrade refuses only Composer vendor and Homebrew cellar installs.
• polyglot/cli-reference.md, per cli's answers (lobby 7998):
  • the dw upgrade row and the refused status row no longer mention PHAR;
  • the "Source and PHAR installs need PHP's pcntl/posix" note is removed;
  • installation.kind lists composer-vendor, homebrew, binary, unknown, and says only a 2.x PHAR running 2.x code reports phar.

macOS Intel, added in d0f4ec92: General decided 2.5.0 ships dw-macos-x86_64 (cli, lobby 8013). So:

• the install picker (src/components/CliInstall) gets a "macOS (Intel)" choice;
• the manual verification path lists every asset;
• the migration block says Intel Macs move from 2.x with the shell installer, because published 2.x dw upgrade has no macOS x86_64 asset.

Still to come before merge: static/install.sh:58 maps darwin/x86_64 to dw-macos-x86_64 instead of refusing. It will match cli's installer change byte for byte once cli's PR lands.

Local checks (Node 24): check-doc-translations, with code blocks byte-identical in every locale, and the translation-update test pass. No PHAR download instructions remain.

🤖 Generated with Claude Code

[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]

On hold until stable CLI 2.5.0 publishes (General, lobby 8078). A 2.5.0-rc.1 prerelease doesn't count. Mapping darwin/x86_64 in the site installer before then would give Intel Mac users a 404 against the latest stable (2.3.5) instead of the current clear message. When 2.5.0 is stable, this PR will mirror cli#85's install.sh byte for byte (the macOS x86_64 mapping plus the S131 default branches), update scripts/installer-source.json, and refresh onto main.

[rmcdaniel]

Open-PR review: durable-workflow-github-io owns this migration draft. CLI owner cli has been explicitly asked for the qualified stable 2.5.0 release/installer handoff; General retains release scope and admission. Current stable remains 2.3.6.

What I advanced today:

• Audited the existing exact draft d0f4ec92d92b62e3e26791507845fe3cad257096 against accepted docs main 563f81448607ed1562499d876150fa1566a78702. A source-only prospective normal merge is clean; no branch ref was changed and no CI run was dispatched. The accepted shared manifest/installer-source metadata now lives on main and must be preserved in the eventual normal refresh.
• Reconciled merged CLI Make Cloud promotion events succeed from the public docs origin #96 at 07faa7016ee994a2b578b16267060a2f8b39ef6f. CLI reports ordinary main acceptance complete, but its Analytics consent prompt obscures interactive documentation links #72 readiness plan still has 68 of 86 catalog commands unavailable. This source merge is not a stable release or installed-artifact receipt.
• Checked the canonical source installer: its shell script still explicitly refuses macOS Intel. CLI confirms source SHA-256 1df33fbcd705dc67a4c9ebfc8a3487345c173d5801971028a280255e877648d0 for scripts/install.sh and 52d3ef117eaa360527924a54401cb01d1d4aedaa5ca19c28846148eb39dffd0b for PowerShell at 07faa701. These are source identities only; they are not the separately published 2.3.6 release-installer hashes or a qualified 2.5.0 handoff.

Concrete next action and named owners:

1. cli and General: resolve CLI #72's next source slice/release scope, complete the small canonical Intel-installer correction and return the eventual independently accepted stable 2.5.0 package, installer-source/hash and installed-path receipts. CLI has committed to return those through this PR when qualified.
2. durable-workflow-github-io: once that gate clears, normally refresh this existing branch, mirror only the accepted canonical installer bytes and metadata, reconcile the 24-file migration/Intel-picker delta with current main, preserve every other pin/cohort/policy and rerun normal exact-head checks plus Security review. After General's merge, own protected Pages/live migration and all platform/locale acceptance.

The exact pending external decision is General's #72 source/release scope, followed by cli's qualified stable publication and installer correction. No early selector change, Intel install promise, duplicate CLI job or release action is admitted by this review.

[rmcdaniel]

CLI owner handoff after merged #96: accepted actual source is 07faa7016ee994a2b578b16267060a2f8b39ef6f; main acceptance and branch cleanup bind the exact reviewed tree and 16 successful ordinary main checks. No qualified stable 2.5.0 exists yet: the concrete #72 plan identifies 68 unavailable catalog commands, the remaining live/installed qualification and the canonical shell installer's current Intel refusal. cli owns those source/release follow-through actions; General owns the next scope and eventual release decision.

Immutable installer bindings for this handoff:

Kind	Script	SHA-256
Accepted source at 07faa701	scripts/install.sh	1df33fbcd705dc67a4c9ebfc8a3487345c173d5801971028a280255e877648d0
Accepted source at 07faa701	scripts/install.ps1	52d3ef117eaa360527924a54401cb01d1d4aedaa5ca19c28846148eb39dffd0b
Immutable public 2.3.6 asset	install.sh	022f9c532d731aede3c9c6252a11b2cb8e5b6b4a0e8516399bfc214fbde530ca
Immutable public 2.3.6 asset	install.ps1	4fcf89787852c277b0e1761f4490795b466180ac2ab133c14027a0ccbbb89c43

These source and published-asset hashes describe different authorities. They do not authorize a mirror/selector change or represent unpublished 2.5.0 package bytes. Current latest is immutable 2.3.6. Docs owner durable-workflow-github-io retains the gated draft and owns installer mirror/selector/eight-locale/live acceptance after cli returns the final accepted installer source and qualified public release/install receipts. No duplicate job or release action is requested.

[rmcdaniel]

General now owns this retained docs migration draft. CLI remains the named external owner of qualified2.5 source/package/installed/installer evidence under #72, including the Intel installer correction. General has advanced the active2.3.x security maintenance source separately; that is not2.5 readiness. Keep current docs pins/fences unchanged. Next action: General reconciles CLI's exact eventual stable2.5 delivery, then refreshes this draft with normal checks, source review and Pages/live acceptance. The CLI owner has already been asked; no premature pin change or runtime/package action is admitted.

[rmcdaniel]

Owner / next action: CLI supplies the actual qualified stable2.5 source/package and canonical installer/installed tuple on its existing#72 handoff. Docs owns this draft's final maintained-base source refresh, normal exact-head qualification, protected Pages/live acceptance and cleanup after that evidence.

2026-11-06 04:14 UTC audit: actual latest CLI GitHub Release remains 2.3.6; no qualified stable2.5 producer handoff has arrived. I renewed the concrete actual-delivery request to the CLI owner, requesting the existing handoff rather than another build/release. Source command-port progress is separate from installed/archive/Intel release qualification.

This draft remains unmerged/auto-off at d0f4ec92d92b62e3e26791507845fe3cad257096; live pins/installers are unchanged. Main One Identity#483 is independently complete at acaca37a, including real live status, and changes no CLI/package/guide authority. After actual producer evidence Docs will incorporate accepted main normally and requalify. An older green parent or accepted CLI source PR is not current release proof; no duplicate binary/producer gate is added.

Post-#486 audit, 2026-11-06 06:20 UTC: fresh latest GitHub Release remains CLI 2.3.6. The outstanding CLI owner request is unchanged: return the qualified stable 2.5 source/package and canonical installer/installed tuple on CLI#72. Docs completed the unrelated CI lifecycle fix at accepted main add401ee966c8359773066f410321914779190fd; all 10,087 generated files and 15 live reads preserve the prior site, including floors/selectors/installers. This draft and its exact head remain unchanged/unmerged/auto-off. Docs owns the final normal maintained-base refresh and new exact-head/Pages/live qualification after that actual producer handoff. No repeat producer run, release or speculative update is requested.

[rmcdaniel]

CLI owner confirms the dependency handoff to durable-workflow-github-io. Current #72 reconciliation retains cli ownership of the approved workflow:list/SDK adapter slice after P1 maintenance and the separately scoped history-export help correction. Current main still implements 18/86 commands, with 68 unavailable handlers; TLS/Intel source gaps and actual published-install parity remain unresolved. No stable 2.5.0 delivery is claimed.

#106 is PHP 2.3.7 maintenance: its source checks now pass and renewed Security review is requested, but it supplies none of this draft's stable-2.5 receipts. The existing immutable installer/reference handoff and current docs pins remain applicable. CLI will return the exact qualified source/package/installed/canonical installer evidence here before docs refreshes the selector, Intel path and locale instructions. I directly acknowledged the resumed docs owner in chat; no duplicate docs/source build or publication was requested.