[hcoona]

Summary

Replaces the completed Delivery Wave entry "Windows Portable Package, Local Build and Test" with a new entry, "Windows 0.1.0-alpha Prereleases". This PR changes only docs/delivery-wave.md.

Authorization and Governing Records

Owner-approved, Wave-only change under AGENTS.md "Start". The repository owner approved in chat on 2026-10-29: merge #548, clean up the host test state, end the completed entry and open the new one, with these decisions:

• the symbols zip is published as a release asset alongside the package;
• no local verification of a downloaded draft (Mark-of-the-Web, SmartScreen or Smart App Control behavior is not evaluated or claimed);
• the entry covers the whole 0.1.0-alpha series.

Work carriers: #506 (packaging and release), #482 (release gates).

Scope and Non-Goals

• Removed entry: its outcome is complete: packaging and records merged in feat: build azureauth-unofficial as a Windows portable package #543 and feat(windows): write the package symbol files into a symbols zip #546, protocol in docs(research): add the portable package host test protocol #547, test evidence and owner disposition in docs(research): record the portable package host test results #548. The host root, launchers, roles.json and ledger were deleted on 2026-10-29 after docs(research): record the portable package host test results #548 merged; WAM state is retained as declared.
• New entry: .github/workflows/release.yml (manual, main-v2 only, windows-latest, scenarios, package.ps1, attestation, draft prerelease with both zips); record updates; a release review per prerelease before the owner publishes; corrections.
• Exclusions: no real-account execution, signing, installers, other channels, product or dependency change, or releases outside v0.1.0-alpha.* from main-v2.

Record-System Impact

`docs/delivery-wave.md` only. The entry delegates later updates to `project.md`, `operational-identities.yaml`, the Windows design (package section and build-chain pinning sentence), the validation strategy (CI, release readiness, Primary Journey Gate), `user-stories.md`, the threat model, `controls.yaml`, the READMEs, `CONTRIBUTING.md`, and the conversion of the completed host-test record and its family.

Evidence and Reasoning

• The GitHub-hosted Windows runner reaches nuget.org (the existing windows-scenarios CI job restores in locked mode), so the release build needs no restore route or -DisableNuGetAudit.
• The release build is a public-release build: workflow_dispatch on main-v2 checks out refs/heads/main-v2; the existing package.ps1 refuses anything else.
• The repository is public, so GitHub build-provenance attestations are also logged in the public Sigstore transparency log; this is declared as an external effect.

Identity and Security Effects

Public distribution of unsigned executables, the bundled Visual Studio Profile (decision 0003 prerelease exception) and symbol files; accepted by the owner in the entry.

Validation

hk check --all passed.

Review and Disposition

Accepted target-branch authorities used: `origin/main-v2` (`a7ece22`) AGENTS.md, governance policies and catalogs, the domain records named below, and both review Skills.

• Independent review (rv_wave_pkg) on fe9344d: removal of the old entry verified complete (items 1–6 merged in feat: build azureauth-unofficial as a Windows portable package #543, feat(windows): write the package symbol files into a symbols zip #546, docs(research): add the portable package host test protocol #547, docs(research): record the portable package host test results #548). Findings: RS-1 to RS-5, RE-1 to RE-3.
• Independent triage (tr_wave_pkg):
  • RS-1 (completed host-test record still reads as an active protocol): true positive (6/10) — conversion delegated in item 2.
  • RS-2 (`windows-latest` vs the design's pinned build chain): true positive, blocking (8/10) — owner disposition: float with recorded versions; design sentence amended under item 2.
  • RS-3 (primary journey first-release blocker vs prereleases): true positive, blocking (7/10) — owner disposition: prereleases exempt; strategy and user stories clarified under item 2.
  • RS-4 (threat model CI-token row): true positive (7/10) — delegated in item 2.
  • RS-5 (`controls.yaml`): true positive, low (4/10) — release control delegated in item 2.
  • RE-1 (public workflow artifacts): true positive (6/10) — owner disposition: one-day artifacts accepted and declared.
  • RE-2 (draft tag target and uniqueness): false positive at Wave level (5/10); bound anyway in the workflow decision and release review.
  • RE-3 (`WindowsHostTiming` on hosted runners): true positive (6/10) — excluded.
• Fixes: 2fc3624. Owner dispositions: comment.
• Rechecks (2026-10-29): RECHECK-007 fires now (public distribution of the bundled Profile): source unchanged (`f7bd73f`), evidence remains bounded existing-state (docs(research): record the portable package host test results #548), the external Client Profile gate stays open under decision 0003's exception; no conclusion changes. All entries with a `release` trigger (001, 002, 003, 004, 006, 007, 008, 009, 010) fire at each prerelease and are evaluated by item 3's release review; sources unchanged today. RECHECK-005 does not fire.
• Re-review on 2fc3624: all earlier findings resolved; one advisory: deleting workflow artifacts needs actions: write, which no job receives. Triage: true positive (8/10), option (a), no new owner decision. Fixed in 380c130: artifacts use retention-days: 1 and expire; no job deletes them. For the owner's merge approval: this drops the earlier wording "deleted once the draft exists", so exposure lasts the full day already accepted.
• Re-review on 380c130: resolved; no material findings under either Skill.
• Owner decision needed: merge (Record-System Gate), including the artifact-retention wording change above.

Upstream Provenance

None.

[hcoona]

Repository-owner dispositions (posted by the authoring agent through the owner's hcoona session on the owner's instruction; the owner gave these decisions in chat on 2026-10-29).

• RS-2 (native build chain): accept the floating GitHub-hosted runner image for the 0.1.0-alpha series. Each run records the MSVC, Windows SDK, link.exe and .NET SDK versions and the runner image version, the release review checks them, and the Windows design's pinning sentence is amended accordingly. Rationale: tracks security updates with low maintenance; a versioned image label would still change monthly.
• RS-3 (primary journey): the first-release blocker applies to the first supported, non-prerelease release. 0.1.0-alpha prereleases are exempt and remain unsupported; the validation strategy and user stories are clarified under item 2.
• RE-1 (workflow artifacts): accept that each run's unreviewed outputs are downloadable by signed-in GitHub users as workflow artifacts for at most one day; they are deleted once the draft exists.
• Earlier decisions in this PR: publish the symbols zip as a release asset; no local verification of downloaded drafts; the entry covers the whole 0.1.0-alpha series.