docs(windows): add explicit PowerShell setup and report recipes

[viktar-b]

Why

Windows users need copyable PowerShell 5.1 and 7 commands for setup, calculation reports and generated projects. Keep those instructions aligned with the workflow that tests installed archives and a Python wheel.

Scope

• Add PowerShell recipes to the six owning guides with one executable PYTHON path, native command status checks, and UTF-8/LF file writing.
• Compare all ten published blocks with the actual Windows driver, allowing only line endings and common indentation to differ.
• Run the equality check through test:ci and both native hosts before setup, so owning documentation-only changes cannot skip it.
• Document the Windows selectors and retained evidence. The existing five required protection contexts remain unchanged.

Verification

Local checks pass: 43 CI tests, five initializer archive tests, focused lint, TypeScript, whitespace, and guide links/fences. Sixteen isolated checks without node_modules confirm command/quoting changes and missing, duplicate, unpaired or unexpected markers fail, including numeric and underscore IDs in both formats. Current-head CI passed, including both native PowerShell hosts and all Ubuntu gates. Each native qualification records 12 successful command blocks, with the documentation equality check before dependency installation. Downloaded artifact hashes, reference agreement, browser/API reports and process restart evidence also pass.

The launcher locator preserves Unicode paths through ASCII JSON, with six retained legacy-encoding probe cases. Windows 11 foreground Ctrl+C and human PDF inspection remain separate qualifications.

Blast Radius

Documentation, generated template guides and verification tooling. Calculation formulas, expected values and numerical policy are unchanged.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
calculation-source-object	Ready	Preview	Sep 30, 2026 11:18am UTC

[viktar-b]

Independent review: ISSUES, pinned to 8586a41f7c700eed802d39faa90e41e9ecf0d5c2, stable patch ID 50e1bf97932265f802d9f03865e2b02682c63fcb.

P2: fix the launcher-only locator in docs/development.md:28 and create-cs-object/README.md:43. Captured print(sys.executable) depends on Python's pipe encoding. Python 3.11 uses the Windows ANSI code page for pipes by default, so a Unicode installation path outside that code page can fail before setup. Python documentation.

I reproduced the failure with an actual temporary virtualenv under cso locator café 梁 ..., LC_ALL=en_US.ISO8859-1, PYTHONUTF8=0, and no PYTHONIOENCODING: raw output exited 1 with UnicodeEncodeError; ASCII JSON output exited 0 and matched a UTF-8 control. This is local legacy-locale evidence, not a Windows run. A small repair is:

$env:PYTHON = py -3.11 -c 'import json,sys; print(json.dumps(sys.executable))' | ConvertFrom-Json

Independent checks passed: all five initializer archive tests, diff whitespace, six-guide fence/link checks, and exact agreement of ten marked blocks with the owner's command manifest. Both marked JSON capture blocks already configure console UTF-8; the reference writer preserves the independent expected value and writes BOM-free UTF-8/LF.

The planned committed equality test against the executed CI script and the final exact-head native PowerShell 5.1/7 matrix remain required gates. Current GitHub quality/isolation/installed jobs were skipped for this docs snapshot. This initial review does not authorize merge or claim Windows 11 foreground Ctrl+C or human PDF inspection.

[viktar-b]

Independent review: PASS+NOTES, pinned to 8477eab357baf28d95c462456490d74c1db72200, base fb857cd805e8b2e3d66a0f4ae22d4fd54aa1def6, stable patch ID 1b7950f702df0244b6c3de3a9521206424ad66e1. This supersedes my earlier ISSUES review: the Unicode locators and unknown-marker parser defect are repaired.

The committed gate compares all ten owning-guide blocks with the actual executed driver. My independent dependency-free mutation probe rejects command/quotation drift, missing/duplicate/unpaired markers and unknown numeric/underscore IDs, while accepting CRLF/common indentation. Local 43 CI tests, lint, types, whitespace and five initializer archive tests pass.

Exact-head CI 36707670892 passes both native hosts and all Ubuntu gates. Both native logs explicitly show the documentation gate passing before setup; qualification records contain 12 successful stages. I downloaded both artifact sets and verified 12 recorded file hashes plus all 11 uploaded binding source/stub files per host, UTF-8/LF writes, unchanged canonical expectations and raw reference hashes, source closure, independent agreement, installed interpreter paths, browser/API/PDF evidence, actual owned-tree termination, same-port restart and expired-run 404.

Notes: archive binaries and empty py.typed remain represented by hash/manifest receipts. Hosted Windows Server evidence does not establish foreground Windows 11 Ctrl+C or human PDF inspection; the guides state those limits.

Final live checks confirm this head/base, every check green, CLEAN/MERGEABLE, and no review threads. No unresolved correctness findings remain. Root retains merge authorization.

[viktar-b]

Root verification PASS at 8477eab357baf28d95c462456490d74c1db72200 against main fb857cd805e8b2e3d66a0f4ae22d4fd54aa1def6.

The independent non-author final verdict is recorded above. The current stable patch ID is 1b7950f702df0244b6c3de3a9521206424ad66e1. All ten PowerShell blocks in six owning guides match the actual maintained Windows driver. The dependency-free gate runs before setup in both native hosts, so owning Markdown-only changes remain checked when Ubuntu quality is skipped. Root independently reproduced the numeric-marker omission at the prior head and confirmed that the repaired current gate rejects unknown numeric and unpaired underscore markers. Command text and quoting remain significant; common indentation and CRLF are the permitted normalization.

Current-head CI passes every Ubuntu job and both native shells. Root separately downloaded both native artifacts and rehashed 12 retained files per host plus every uploaded binding/stub. All 12 stage statuses are zero. Actual bindings are BOM-free UTF8/LF and byte-identical across hosts. Canonical reference content and native before/after/copy hashes are unchanged. Execution retains source closure efd06bb6a77b704d0d342d465602659d8c2e81a45dd3d1239797be711035f0bd. Independent rectangle agreement, installed project-local Python, browser/API/checked HTML/PDF and same-port restart with expired-run404 pass. Earlier legacy-encoding locator probes and initializer archive checks cover unchanged inputs.

The CI guide matches the actual selector and five existing protection contexts. No numerical expectations, tolerance policy, required protection contexts or release behavior changed. Dependency-review, PR-title and all CodeQL analyses pass. GitHub reports the exact head/base, CLEAN/MERGEABLE and zero review threads. Windows Server2025 testing covers Desktop PowerShell5.1 and Core PowerShell7. Windows11 foreground Ctrl+C and human report inspection remain separate qualification steps. Normal protected merge is authorized for this exact head only.