KofTwentyTwo/AppKit
2
0 Fork 0
Code Issues 22 Pull Requests 4 Actions Packages Projects Releases 1 Wiki Activity

test: add a repeatable foundation and template readiness audit #20

New Issue
Open
opened 2026-10-10 16:58:50 +00:00 by KofTwentyTwo · 21 comments
KofTwentyTwo commented 2026-10-10 16:58:50 +00:00 (Migrated from github.com)
Copy link
Copy source

Problem

Automated repository conformance misses coding/policy gaps and the starter's stale content hashes. Current evidence is manual and ignored local artifacts.

Acceptance criteria

Automate clean-package restores, CLI/no-CLI generation, format, coverage and UI gates; review manual requirements and exceptions; run library mutation testing before the next minor release; produce scoped evidence rather than blanket compliance claims.

Scope

AppKit and starter quality/release checks.

This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.

## Problem Automated repository conformance misses coding/policy gaps and the starter's stale content hashes. Current evidence is manual and ignored local artifacts. ## Acceptance criteria Automate clean-package restores, CLI/no-CLI generation, format, coverage and UI gates; review manual requirements and exceptions; run library mutation testing before the next minor release; produce scoped evidence rather than blanket compliance claims. ## Scope AppKit and starter quality/release checks. This issue is part of the user-requested AppKit readiness remediation. Local work is not completion until the applicable published/runtime state and checks are verified. Substantial AI assistance: Codex.
KofTwentyTwo commented 2026-10-10 17:42:34 +00:00 (Migrated from github.com)
Copy link
Copy source

Template publication is prepared locally: shared NuGet release caller for the source template, separate Velopack workflows for generated CLI/no-CLI apps, package readme and committed build lock, and a source CI gate that installs the actual nupkg and exercises both variants. Both packaged variants build and format cleanly, with 54 combined unit tests / 100% core and CLI coverage / 14 UI tests passing when sequenced. An initial CLI UI timeout occurred while another suite shared the desktop; the sequential full rerun passed. Package inspection excludes generated reports/binaries and includes the template metadata/readme.

The template repository/package are not published. Inventory, protected GitHub settings, a NuGet trusted-publishing policy and live CI/attestation verification remain. All changes are uncommitted; no publication or certification is claimed.

Template publication is prepared locally: shared NuGet release caller for the source template, separate Velopack workflows for generated CLI/no-CLI apps, package readme and committed build lock, and a source CI gate that installs the actual nupkg and exercises both variants. Both packaged variants build and format cleanly, with 54 combined unit tests / 100% core and CLI coverage / 14 UI tests passing when sequenced. An initial CLI UI timeout occurred while another suite shared the desktop; the sequential full rerun passed. Package inspection excludes generated reports/binaries and includes the template metadata/readme. The template repository/package are not published. Inventory, protected GitHub settings, a NuGet trusted-publishing policy and live CI/attestation verification remain. All changes are uncommitted; no publication or certification is claimed.
KofTwentyTwo commented 2026-10-10 17:52:28 +00:00 (Migrated from github.com)
Copy link
Copy source

Readiness regression infrastructure is committed locally: AppKit 4cea46bb1dbb3a0d38011fafef0b2443c6d0e53d and 36886cbaae8810bf9c9a3c85867a2cee51d0ba3d; starter a5cbc98cd72e7223a0f61c5c4a237afc0de60efe.

AppKit passed 119 unit tests, 12 UI tests and 100% core/updates coverage. The actual packaged template passed both renamed variants: 54 unit tests, 14 UI tests when run sequentially, 100% core/CLI coverage, zero-warning builds and formatting. New CI repeats the pack/install/generate checks. Coverage-gate Pester tests pass four per repository; script and workflow checks pass.

Remaining: the complete readiness acceptance set, including installed stable/dev upgrades, live repository checks and mutation testing, is not yet verified. Keep the ticket open. All commits are signed, signed off, and local. AI assistance: Codex (GPT-6).

Readiness regression infrastructure is committed locally: AppKit `4cea46bb1dbb3a0d38011fafef0b2443c6d0e53d` and `36886cbaae8810bf9c9a3c85867a2cee51d0ba3d`; starter `a5cbc98cd72e7223a0f61c5c4a237afc0de60efe`. AppKit passed 119 unit tests, 12 UI tests and 100% core/updates coverage. The actual packaged template passed both renamed variants: 54 unit tests, 14 UI tests when run sequentially, 100% core/CLI coverage, zero-warning builds and formatting. New CI repeats the pack/install/generate checks. Coverage-gate Pester tests pass four per repository; script and workflow checks pass. Remaining: the complete readiness acceptance set, including installed stable/dev upgrades, live repository checks and mutation testing, is not yet verified. Keep the ticket open. All commits are signed, signed off, and local. AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 18:27:37 +00:00 (Migrated from github.com)
Copy link
Copy source

Additional verified progress saved in signed commit b2f0686ac0d9edccda15541bf115efaa2a79a203: huge-log cases now exercise both sample apps and prove that the newest entry is visible while the bounded-input notice remains visible. All 14 UI tests pass, whole-solution formatting verification passes and the x64 build has zero warnings.

Diagnosed initial crash-net input timeouts and misaligned captures on a scaled desktop: UIA coordinates were physical while the test thread was DPI virtualized. The harness now uses a scoped per-monitor-v2 context, restored even when construction or cleanup fails. This is a repeatability correction, not an unexplained rerun. UI suites must still run sequentially on the shared desktop.

Current library evidence: 146 unit tests and 100% core/updates line coverage. Template pack/install/CLI-no-CLI generation evidence remains 54 combined unit and 14 UI tests; public-source lock repairs are committed in the starter. Remaining acceptance work includes library mutation testing, published-output smoke checks, live CI rollout and the repository provisioning/distribution tasks. No blanket compliance or installed-channel-readiness claim is made. Substantial AI assistance: Codex (GPT-6).

Additional verified progress saved in signed commit `b2f0686ac0d9edccda15541bf115efaa2a79a203`: huge-log cases now exercise both sample apps and prove that the newest entry is visible while the bounded-input notice remains visible. All 14 UI tests pass, whole-solution formatting verification passes and the x64 build has zero warnings. Diagnosed initial crash-net input timeouts and misaligned captures on a scaled desktop: UIA coordinates were physical while the test thread was DPI virtualized. The harness now uses a scoped per-monitor-v2 context, restored even when construction or cleanup fails. This is a repeatability correction, not an unexplained rerun. UI suites must still run sequentially on the shared desktop. Current library evidence: 146 unit tests and 100% core/updates line coverage. Template pack/install/CLI-no-CLI generation evidence remains 54 combined unit and 14 UI tests; public-source lock repairs are committed in the starter. Remaining acceptance work includes library mutation testing, published-output smoke checks, live CI rollout and the repository provisioning/distribution tasks. No blanket compliance or installed-channel-readiness claim is made. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 18:52:16 +00:00 (Migrated from github.com)
Copy link
Copy source

Verified and saved in signed/DCO-signed-off commit ed19eaf69ef3ad3add74c1d42da87011e95afc0e:

  • Repository-local Stryker.NET 5.0.0 (Apache-2.0, development only) and one runner for both complete library projects; NuGet repository signature verified.
  • A trusted Windows mutation workflow retains HTML/JSON evidence and runs before package publication; tool errors and failing baseline tests block the release.
  • 161 unit tests now pass with 100% core/updates line coverage. Added genuinely asynchronous context tests and stronger settings/log/identity/secret/update assertions.
  • Core mutation score improved from 90.17% to 96.27% (284 killed / 11 survivors); updates from 77.92% to 89.61% (69 killed / 8 survivors). No uncovered mutations or timeouts. Recorded all 19 survivor decisions, including four native-boundary limits, in docs/testing/mutation-testing.md. No mutation exclusions or score overrides were added.
  • Whole-solution format verification, PSScriptAnalyzer and applicable hooks including actionlint/zizmor pass. The native dotnet executable is explicitly resolved to avoid a casing-analyzer command-metadata exception; no lint rule was disabled.

This completes local mutation execution/triage, not every issue criterion. Published-output smoke checks, live CI rollout and remaining template acceptance work are still pending. The new signing request is tracked in #12. Substantial AI assistance: Codex (GPT-6).

Verified and saved in signed/DCO-signed-off commit `ed19eaf69ef3ad3add74c1d42da87011e95afc0e`: - Repository-local Stryker.NET 5.0.0 (Apache-2.0, development only) and one runner for both complete library projects; NuGet repository signature verified. - A trusted Windows mutation workflow retains HTML/JSON evidence and runs before package publication; tool errors and failing baseline tests block the release. - 161 unit tests now pass with 100% core/updates line coverage. Added genuinely asynchronous context tests and stronger settings/log/identity/secret/update assertions. - Core mutation score improved from 90.17% to 96.27% (284 killed / 11 survivors); updates from 77.92% to 89.61% (69 killed / 8 survivors). No uncovered mutations or timeouts. Recorded all 19 survivor decisions, including four native-boundary limits, in `docs/testing/mutation-testing.md`. No mutation exclusions or score overrides were added. - Whole-solution format verification, PSScriptAnalyzer and applicable hooks including actionlint/zizmor pass. The native dotnet executable is explicitly resolved to avoid a casing-analyzer command-metadata exception; no lint rule was disabled. This completes local mutation execution/triage, not every issue criterion. Published-output smoke checks, live CI rollout and remaining template acceptance work are still pending. The new signing request is tracked in #12. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 19:35:33 +00:00 (Migrated from github.com)
Copy link
Copy source

Signed local AppKit commit a8d9cf7efe5a3ca03c88442d776765ad4de9bc41 adds signing and Azure-administration regression gates: 31 combined Pester checks pass, including 21 signing/distribution cases and six identity/tenant/scope/federation safeguards. Signing failure, verification failure, missing Azure configuration, or an unsigned shared builder blocks the next release preflight; no unsigned fallback is permitted. The signing-enabled shared builder is prepared in an isolated standards branch, not published yet.

Relevant quality gates and commit hooks pass; no .NET runtime code changed in this commit. Existing latest AppKit evidence remains 161 unit tests, 100% core/updates line coverage and 14 UI tests. Real Azure signing and live CI remain pending; a Microsoft-signed tool verification is not AppKit signing proof. Details and remaining actions are tracked in #12 and docs/release-signing.md. No push, merge or new release occurred; keep this ticket open for live acceptance evidence.

Signed local AppKit commit `a8d9cf7efe5a3ca03c88442d776765ad4de9bc41` adds signing and Azure-administration regression gates: 31 combined Pester checks pass, including 21 signing/distribution cases and six identity/tenant/scope/federation safeguards. Signing failure, verification failure, missing Azure configuration, or an unsigned shared builder blocks the next release preflight; no unsigned fallback is permitted. The signing-enabled shared builder is prepared in an isolated standards branch, not published yet. Relevant quality gates and commit hooks pass; no .NET runtime code changed in this commit. Existing latest AppKit evidence remains 161 unit tests, 100% core/updates line coverage and 14 UI tests. Real Azure signing and live CI remain pending; a Microsoft-signed tool verification is not AppKit signing proof. Details and remaining actions are tracked in #12 and `docs/release-signing.md`. No push, merge or new release occurred; keep this ticket open for live acceptance evidence.
KofTwentyTwo commented 2026-10-10 19:55:58 +00:00 (Migrated from github.com)
Copy link
Copy source

Implemented and saved locally in starter commit 3dd5adf89d4f07cd40092151eef9cc44c5a0a969 on fix/template-onboarding. No push, repository creation, settings mutation, merge or publication has been performed.

  • Added offline preview, explicit apply and read-only validation for generated repository controls, with thirteen non-secret API requests.
  • Apply requires the current head of an open bootstrap PR and every required GitHub Actions check to succeed. Rulesets bind contexts to the observed Actions app; main has no bypass; release permits only v* tags. Existing conflicting rules/environment policies are preserved and rejected before writes.
  • Propagated the human-acknowledged current-commit review validator, locked JavaScript tools, lint/signature gates and CodeQL coverage to generated apps. Custom owner/reviewer substitution passes in both CLI variants.
  • Template packages exclude node_modules and worktree Git metadata. Added a complete owner bootstrap/runbook and threat-model boundaries.

Validation: 13 setup boundary tests plus four coverage tests pass; seven Node tests, PowerShell analysis, ESLint, workflow/security/documentation lint and all commit hooks pass. npm verified 83 signatures and 20 attestations. Packed template generation with owner Example produces correct setup/review identities; both CLI/no-CLI generated solutions pass locked restore and zero-warning build.

Remaining acceptance: authorized disposable live repository creation/push, hosted CI, real apply/readback and failing-PR enforcement; inventory/public template publication and human review acknowledgement. The issue remains open for that evidence. Substantial AI assistance: Codex (GPT-6).

Implemented and saved locally in starter commit `3dd5adf89d4f07cd40092151eef9cc44c5a0a969` on `fix/template-onboarding`. No push, repository creation, settings mutation, merge or publication has been performed. - Added offline preview, explicit apply and read-only validation for generated repository controls, with thirteen non-secret API requests. - Apply requires the current head of an open bootstrap PR and every required GitHub Actions check to succeed. Rulesets bind contexts to the observed Actions app; main has no bypass; release permits only v* tags. Existing conflicting rules/environment policies are preserved and rejected before writes. - Propagated the human-acknowledged current-commit review validator, locked JavaScript tools, lint/signature gates and CodeQL coverage to generated apps. Custom owner/reviewer substitution passes in both CLI variants. - Template packages exclude node_modules and worktree Git metadata. Added a complete owner bootstrap/runbook and threat-model boundaries. Validation: 13 setup boundary tests plus four coverage tests pass; seven Node tests, PowerShell analysis, ESLint, workflow/security/documentation lint and all commit hooks pass. npm verified 83 signatures and 20 attestations. Packed template generation with owner Example produces correct setup/review identities; both CLI/no-CLI generated solutions pass locked restore and zero-warning build. Remaining acceptance: authorized disposable live repository creation/push, hosted CI, real apply/readback and failing-PR enforcement; inventory/public template publication and human review acknowledgement. The issue remains open for that evidence. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 20:09:19 +00:00 (Migrated from github.com)
Copy link
Copy source

Optional distribution presets implemented in signed local starter commit 53eecfc8d54b8f51cda1ba11595c596430fc6f69 (not pushed).

  • Stable-only Scoop/Chocolatey generation for CLI or GUI portable releases; actual final-byte SHA256, validated archive identity/layout and traversal rejection; correct generated package IDs and metadata.
  • Opt-in protected release job verifies ZIP checksum and GitHub provenance, generates manifests, and packs candidates for review. No feed is updated automatically. GUI-only projects explicitly reject CLI distribution selection.
  • winget remains optional/stable-only; configured missing tokens now fail. The pinned v1.12.13.0 client's TokenHelper was inspected: WINGET_CREATE_GITHUB_TOKEN is supported, so credentials now stay in the job environment instead of argv.
  • Documentation explains manager-owned portable upgrades, selected-feed setup and disposable installation tests; threat model updated.

Validation: 24 combined Pester tests pass (7 distribution, 13 setup, 4 coverage), including execution of the generated Chocolatey installation callback with a download test double and helper-shim exclusions. PowerShell/workflow/security/documentation lint and all hooks pass. Both presets generate from provenance-verified published gclo 1.0.1 CLI and portable ZIPs and pass the installed official Scoop schema. Fresh packed CLI/no-CLI templates substitute owner/app/executable identities correctly.

Remaining: no Chocolatey feed/package publication or disposable real package-manager install/upgrade/uninstall has been performed; hosted candidate-job/choco-pack verification is pending. Presets are deliberately optional; source generation is not a live-feed readiness claim. Issue stays open for selected-integration acceptance. Substantial AI assistance: Codex (GPT-6).

Optional distribution presets implemented in signed local starter commit `53eecfc8d54b8f51cda1ba11595c596430fc6f69` (not pushed). - Stable-only Scoop/Chocolatey generation for CLI or GUI portable releases; actual final-byte SHA256, validated archive identity/layout and traversal rejection; correct generated package IDs and metadata. - Opt-in protected release job verifies ZIP checksum and GitHub provenance, generates manifests, and packs candidates for review. No feed is updated automatically. GUI-only projects explicitly reject CLI distribution selection. - winget remains optional/stable-only; configured missing tokens now fail. The pinned v1.12.13.0 client's TokenHelper was inspected: WINGET_CREATE_GITHUB_TOKEN is supported, so credentials now stay in the job environment instead of argv. - Documentation explains manager-owned portable upgrades, selected-feed setup and disposable installation tests; threat model updated. Validation: 24 combined Pester tests pass (7 distribution, 13 setup, 4 coverage), including execution of the generated Chocolatey installation callback with a download test double and helper-shim exclusions. PowerShell/workflow/security/documentation lint and all hooks pass. Both presets generate from provenance-verified published gclo 1.0.1 CLI and portable ZIPs and pass the installed official Scoop schema. Fresh packed CLI/no-CLI templates substitute owner/app/executable identities correctly. Remaining: no Chocolatey feed/package publication or disposable real package-manager install/upgrade/uninstall has been performed; hosted candidate-job/choco-pack verification is pending. Presets are deliberately optional; source generation is not a live-feed readiness claim. Issue stays open for selected-integration acceptance. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 20:57:43 +00:00 (Migrated from github.com)
Copy link
Copy source

Current signed local heads: AppKit 8cbd3d1, isolated starter 90af2f7, isolated signing standards 7bd3cfe (17 local commits total; original sibling checkouts preserved). None pushed, merged or newly released.

New evidence: actual stable/dev installations upgraded and restarted with isolated feed requests; 19 published/installed UI checks passed. AppKit direct startup changes pass the zero-warning build, formatting and all 14 sample UI tests. Starter tooling passes 30 Pester tests, changed-file PowerShell analysis and all hooks. The new required CI job includes payload-byte checks before installation.

Acceptance remains incomplete: subsequent archive comparison exposed altered dependency bytes (#22), and the fresh GUI-only run fails closed. Public/hosted flow, AppKit UI live updater, feed installation, signing, owner attestations and final deployment remain pending. Azure authentication retries remain deferred as requested. Earlier review packet for b2f0686 is stale and must be regenerated before publication approval.

Current signed local heads: AppKit `8cbd3d1`, isolated starter `90af2f7`, isolated signing standards `7bd3cfe` (17 local commits total; original sibling checkouts preserved). None pushed, merged or newly released. New evidence: actual stable/dev installations upgraded and restarted with isolated feed requests; 19 published/installed UI checks passed. AppKit direct startup changes pass the zero-warning build, formatting and all 14 sample UI tests. Starter tooling passes 30 Pester tests, changed-file PowerShell analysis and all hooks. The new required CI job includes payload-byte checks before installation. Acceptance remains incomplete: subsequent archive comparison exposed altered dependency bytes (#22), and the fresh GUI-only run fails closed. Public/hosted flow, AppKit UI live updater, feed installation, signing, owner attestations and final deployment remain pending. Azure authentication retries remain deferred as requested. Earlier review packet for b2f0686 is stale and must be regenerated before publication approval.
KofTwentyTwo commented 2026-10-10 21:47:08 +00:00 (Migrated from github.com)
Copy link
Copy source

Committed locally: starter 2c8816b187b3a9a540f28daea20e0b1b061e8c5b on fix/template-onboarding. Six starter commits now; 21 signed/DCO commits total across AppKit, starter and shared builder. No pushes or new releases.

Verified GUI-only evidence: four actual self-contained publishes, 532 preserved files in each portable/full package, loose/portable checks, real stable 0.1.0 -> 0.4.0 and dev 0.3.0-beta.1 -> 0.3.0-beta.2 installs/upgrades, same-channel feeds, restart, target assembly SHA256 and 19 UI tests. Evidence remains in artifacts/starter-finish/artifacts/temp-stage-no-cli/artifacts/installed-temp-stage/.

CLI evidence: four single-file versions execute and all package byte checks pass; seven published UI checks and stable upgrade/restart pass. Two installed suites exposed different input timeouts, tracked in #23. Focused greeting tests (five) and the complete six-case sequence against the exact failed published 0.4.0 binary pass, without establishing the original cause. The candidate now focuses physical input and waits before clicking; its published seven UI cases pass. Its latest full attempt stopped on disk exhaustion while extracting portable assets, before any installation. Retained the failed runs; no test was skipped or timeout increased.

The smoke harness now parses source PE headers, copies only four probe files, isolates system-temp build/packer staging and refuses to start below 8 GB free on the artifact volume. Moved completed diagnostic fixtures to the approved cache without deleting them; workspace now has about 9.4 GB free. The candidate's complete CLI installed acceptance still needs a fresh run.

Current source validation: 31 Pester tests, changed-file PowerShell analysis, zero-warning UI-test build, scoped C# format, Markdown lint and commit hooks/signature verification pass. Source and prepared shared-builder worktrees are clean. AppKit head is 146138957506b79459a6d811a1e70a626e006699; shared head is 4dfde0976a59f3a2b07b974444e837574310c083.

Live AppKit UI updater/public hosting, signing, hosted CI and source/template rollout remain acceptance requirements. Keep this issue open. Substantial AI assistance: Codex (GPT-6).

Committed locally: starter `2c8816b187b3a9a540f28daea20e0b1b061e8c5b` on `fix/template-onboarding`. Six starter commits now; 21 signed/DCO commits total across AppKit, starter and shared builder. No pushes or new releases. Verified GUI-only evidence: four actual self-contained publishes, 532 preserved files in each portable/full package, loose/portable checks, real stable `0.1.0 -> 0.4.0` and dev `0.3.0-beta.1 -> 0.3.0-beta.2` installs/upgrades, same-channel feeds, restart, target assembly SHA256 and 19 UI tests. Evidence remains in `artifacts/starter-finish/artifacts/temp-stage-no-cli/artifacts/installed-temp-stage/`. CLI evidence: four single-file versions execute and all package byte checks pass; seven published UI checks and stable upgrade/restart pass. Two installed suites exposed different input timeouts, tracked in #23. Focused greeting tests (five) and the complete six-case sequence against the exact failed published 0.4.0 binary pass, without establishing the original cause. The candidate now focuses physical input and waits before clicking; its published seven UI cases pass. Its latest full attempt stopped on disk exhaustion while extracting portable assets, before any installation. Retained the failed runs; no test was skipped or timeout increased. The smoke harness now parses source PE headers, copies only four probe files, isolates system-temp build/packer staging and refuses to start below 8 GB free on the artifact volume. Moved completed diagnostic fixtures to the approved cache without deleting them; workspace now has about 9.4 GB free. The candidate's complete CLI installed acceptance still needs a fresh run. Current source validation: 31 Pester tests, changed-file PowerShell analysis, zero-warning UI-test build, scoped C# format, Markdown lint and commit hooks/signature verification pass. Source and prepared shared-builder worktrees are clean. AppKit head is `146138957506b79459a6d811a1e70a626e006699`; shared head is `4dfde0976a59f3a2b07b974444e837574310c083`. Live AppKit UI updater/public hosting, signing, hosted CI and source/template rollout remain acceptance requirements. Keep this issue open. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 21:59:09 +00:00 (Migrated from github.com)
Copy link
Copy source

Generated-application signing preflight is committed locally as signed/DCO commit 34d7543a3ce7434dcda6545ad9ab33b5b1426a02 in the isolated starter worktree.

Both CLI and GUI-only release callers now bind the configuration check to the protected release environment. Publication is blocked unless signing is explicitly enabled, the owned-file catalog is nonempty, and all seven signing variables are present. Client/tenant/subscription identifiers must be nonempty GUIDs; the endpoint must be HTTPS on the Artifact Signing domain. Modern variable names and the documented legacy fallback are supported. The content-only source-template NuGet workflow remains separate.

Validation: packed the actual template, generated renamed custom-owner CLI and GUI-only projects, and passed all 40 script boundary tests in source and each generated variant. Changed-file PSScriptAnalyzer checks passed in fresh processes after its intermittent internal exception. Source/generated workflow syntax, offline workflow security checks, documentation lint and required hooks passed. Commit signature verified.

The guide covers repository/environment-bound OIDC, profile-scoped signer permission, exact publisher verification, third-party signature preservation and final-byte verification. It explicitly requires a published reviewed shared builder supporting the owned-file catalog before enabling signing; published standards v1.0.0 does not expose that interface. No unpublished builder has been pinned.

This proves configuration guards, not Azure access or valid AppKit signatures. Actual deployed profile lookup, AppKit CI identity/federation/role, representative signed artifacts and hosted rollout remain acceptance requirements. Azure retry remains deferred by the owner. No push, merge, release or live settings/Azure change was performed. Substantial AI assistance: Codex (GPT-6).

Generated-application signing preflight is committed locally as signed/DCO commit `34d7543a3ce7434dcda6545ad9ab33b5b1426a02` in the isolated starter worktree. Both CLI and GUI-only release callers now bind the configuration check to the protected `release` environment. Publication is blocked unless signing is explicitly enabled, the owned-file catalog is nonempty, and all seven signing variables are present. Client/tenant/subscription identifiers must be nonempty GUIDs; the endpoint must be HTTPS on the Artifact Signing domain. Modern variable names and the documented legacy fallback are supported. The content-only source-template NuGet workflow remains separate. Validation: packed the actual template, generated renamed custom-owner CLI and GUI-only projects, and passed all 40 script boundary tests in source and each generated variant. Changed-file PSScriptAnalyzer checks passed in fresh processes after its intermittent internal exception. Source/generated workflow syntax, offline workflow security checks, documentation lint and required hooks passed. Commit signature verified. The guide covers repository/environment-bound OIDC, profile-scoped signer permission, exact publisher verification, third-party signature preservation and final-byte verification. It explicitly requires a published reviewed shared builder supporting the owned-file catalog before enabling signing; published standards v1.0.0 does not expose that interface. No unpublished builder has been pinned. This proves configuration guards, not Azure access or valid AppKit signatures. Actual deployed profile lookup, AppKit CI identity/federation/role, representative signed artifacts and hosted rollout remain acceptance requirements. Azure retry remains deferred by the owner. No push, merge, release or live settings/Azure change was performed. Substantial AI assistance: Codex (GPT-6).
KofTwentyTwo commented 2026-10-10 22:24:51 +00:00 (Migrated from github.com)
Copy link
Copy source

Fresh committed-template CLI attempt df40b60 completed all four 532-file portable/full byte comparisons, CLI executions, both installed stable/dev upgrades/restarts, channel isolation and exact target assembly checks. Published UI passed 7/7; installed stable passed 6/6; installed dev passed 5/6, failing the theme-save check with app alive. Guarded cleanup completed. Retain the failure; full harness exit was failure, not success.

Evidence: artifacts/starter-finish/artifacts/guarded-with-cli/artifacts/installed-guarded/, including published-ui.trx, installed-stable-ui.trx, installed-dev-ui.trx, stable-after.json, dev-after.json, process-34.log and build-directory.txt. AppKit reported installed versions 0.4.0/stable and 0.3.0-beta.2/dev; only each channel's feed was requested.

Starter menu/control input was missing the foundation sample's existing foreground step. Signed local commit 7eef2a489cb8a1924cb46f4c08e2593a532d930d aligns those paths, applies the observed point-ownership guard to every physical fallback, and captures invocation kind/settings/logs for theme failures. Product code and timeouts remain unchanged.

Three focused theme checks and all six feature checks passed on the exact failed dev publish payload. These are clearly identified same-identity diagnostic tests, not a fresh complete installed acceptance run. Evidence: sibling artifacts/input-diagnostics/theme-foreground-{1,2,3}.trx and dev-feature-foreground.trx. Source and diagnostic zero-warning builds, formatting, hooks and Markdown passed. The earlier crash occlusion trace remains separate evidence; this does not prove every prior failure had the same cause.

Keep #23/#11/#20 open for a complete current packed-template CLI/GUI-only run and hosted acceptance. Current R: capacity is below the 8 GB start gate after retaining fixtures; preserve evidence in the approved cache before launching another full run. No signing or publication occurred.

Fresh committed-template CLI attempt `df40b60` completed all four 532-file portable/full byte comparisons, CLI executions, both installed stable/dev upgrades/restarts, channel isolation and exact target assembly checks. Published UI passed 7/7; installed stable passed 6/6; installed dev passed 5/6, failing the theme-save check with app alive. Guarded cleanup completed. Retain the failure; full harness exit was failure, not success. Evidence: `artifacts/starter-finish/artifacts/guarded-with-cli/artifacts/installed-guarded/`, including `published-ui.trx`, `installed-stable-ui.trx`, `installed-dev-ui.trx`, `stable-after.json`, `dev-after.json`, `process-34.log` and `build-directory.txt`. AppKit reported installed versions 0.4.0/stable and 0.3.0-beta.2/dev; only each channel's feed was requested. Starter menu/control input was missing the foundation sample's existing foreground step. Signed local commit `7eef2a489cb8a1924cb46f4c08e2593a532d930d` aligns those paths, applies the observed point-ownership guard to every physical fallback, and captures invocation kind/settings/logs for theme failures. Product code and timeouts remain unchanged. Three focused theme checks and all six feature checks passed on the exact failed dev publish payload. These are clearly identified same-identity diagnostic tests, not a fresh complete installed acceptance run. Evidence: sibling `artifacts/input-diagnostics/theme-foreground-{1,2,3}.trx` and `dev-feature-foreground.trx`. Source and diagnostic zero-warning builds, formatting, hooks and Markdown passed. The earlier crash occlusion trace remains separate evidence; this does not prove every prior failure had the same cause. Keep #23/#11/#20 open for a complete current packed-template CLI/GUI-only run and hosted acceptance. Current R: capacity is below the 8 GB start gate after retaining fixtures; preserve evidence in the approved cache before launching another full run. No signing or publication occurred.
KofTwentyTwo commented 2026-10-10 22:33:37 +00:00 (Migrated from github.com)
Copy link
Copy source

Fresh actual packed-template acceptance from signed starter commit 7eef2a489cb8a1924cb46f4c08e2593a532d930d completed successfully. Published UI passed 7/7, installed stable 6/6, installed dev 6/6: 19 checks, zero failures/skips. All four 532-file portable/full payload comparisons passed before runtime acceptance. Stable 0.1.0 -> 0.4.0 and dev 0.3.0-beta.1 -> beta.2 downloaded, applied, restarted and passed installed version/target hash/channel isolation checks. Guarded uninstalls completed.

Evidence: artifacts/starter-finish/artifacts/foreground-with-cli/artifacts/installed-foreground/: results.json, published-ui.trx, installed-stable-ui.trx, installed-dev-ui.trx, stable-after.json, dev-after.json, and build-directory.txt. This is generated from the committed package, not manually synchronized diagnostic files. Earlier failing runs remain retained.

The harness uses real Velopack installed upgrades with an offline GitHub transport. It does not prove live public feeds, the AppKit UI check/apply flow, production signatures, deltas or hosted CI. Current-head GUI-only acceptance is next; no test process remains live. Keep the applicable remaining criteria open. No push, PR, merge, new release, settings change or Azure login retry occurred. Twenty-eight signed local commits remain prepared across AppKit, starter and shared signing.

Fresh actual packed-template acceptance from signed starter commit `7eef2a489cb8a1924cb46f4c08e2593a532d930d` completed successfully. Published UI passed 7/7, installed stable 6/6, installed dev 6/6: 19 checks, zero failures/skips. All four 532-file portable/full payload comparisons passed before runtime acceptance. Stable `0.1.0 -> 0.4.0` and dev `0.3.0-beta.1 -> beta.2` downloaded, applied, restarted and passed installed version/target hash/channel isolation checks. Guarded uninstalls completed. Evidence: `artifacts/starter-finish/artifacts/foreground-with-cli/artifacts/installed-foreground/`: `results.json`, `published-ui.trx`, `installed-stable-ui.trx`, `installed-dev-ui.trx`, `stable-after.json`, `dev-after.json`, and `build-directory.txt`. This is generated from the committed package, not manually synchronized diagnostic files. Earlier failing runs remain retained. The harness uses real Velopack installed upgrades with an offline GitHub transport. It does not prove live public feeds, the AppKit UI check/apply flow, production signatures, deltas or hosted CI. Current-head GUI-only acceptance is next; no test process remains live. Keep the applicable remaining criteria open. No push, PR, merge, new release, settings change or Azure login retry occurred. Twenty-eight signed local commits remain prepared across AppKit, starter and shared signing.
KofTwentyTwo commented 2026-10-10 22:48:13 +00:00 (Migrated from github.com)
Copy link
Copy source

Both actual packed-template variants from signed starter head 7eef2a489cb8a1924cb46f4c08e2593a532d930d now complete the installed smoke: CLI 19/19 UI checks and GUI-only 19/19, all four 532-file portable/full comparisons per variant, stable 0.1.0 -> 0.4.0 and dev 0.3.0-beta.1 -> beta.2 real downloads/apply/restarts, exact installed version/target hashes and no cross-channel requests/offers. Guarded cleanup completed.

Current GUI-only evidence: C:/Users/james/.cache/AppKit-acceptance/2026-10-10/foreground-no-cli/artifacts/installed-reserved-desktop/{results.json,published-ui.trx,installed-stable-ui.trx,installed-dev-ui.trx,stable-after.json,dev-after.json,build-directory.txt}. Current CLI evidence remains in artifacts/starter-finish/artifacts/foreground-with-cli/artifacts/installed-foreground/.

The first current GUI attempt is retained in sibling installed-foreground/: published UI 6/7, crash-log timeout, app alive. Its trace owned the target before clicking but afterward reported a distant pointer position over a gclo process. The owner then reserved the desktop; the unchanged fixture passed the complete run. This supports desktop input interference for that observed failure, without proving every earlier timeout had the same cause. Completed older guarded-with-cli evidence moved intact to C:/Users/james/.cache/AppKit-retained-fixtures/2026-10-10/guarded-with-cli with all seven TRX reports; no evidence deleted.

Foundation AppKit bbf7efd freshly passes locked restore, zero-warning full build, format verification, 161 unit tests/100% core-update coverage, 14 WinUI/WPF UI tests, seven review-validator tests and ESLint. Current exact-commit review and rollout packets are prepared. Two additional signed shared-rollout commits (helper 3334d02, builder 5887a83) start from published standards v1.0.0; 35 tests and workflow/docs/hooks pass. Thirty signed local preparation commits total; original checkouts are preserved.

Remaining criteria stay open: actual hosted gates/review bootstrap, public starter/package/feed rollout, AppKit's live check/apply integration, final Azure identity/role/resource/signature proof, owner badge attestations and age reassessment. Offline GitHub transport is not hosted or signing evidence. No push, PR, merge, new release, live settings change or Azure retry occurred.

Both actual packed-template variants from signed starter head `7eef2a489cb8a1924cb46f4c08e2593a532d930d` now complete the installed smoke: CLI 19/19 UI checks and GUI-only 19/19, all four 532-file portable/full comparisons per variant, stable `0.1.0 -> 0.4.0` and dev `0.3.0-beta.1 -> beta.2` real downloads/apply/restarts, exact installed version/target hashes and no cross-channel requests/offers. Guarded cleanup completed. Current GUI-only evidence: `C:/Users/james/.cache/AppKit-acceptance/2026-10-10/foreground-no-cli/artifacts/installed-reserved-desktop/{results.json,published-ui.trx,installed-stable-ui.trx,installed-dev-ui.trx,stable-after.json,dev-after.json,build-directory.txt}`. Current CLI evidence remains in `artifacts/starter-finish/artifacts/foreground-with-cli/artifacts/installed-foreground/`. The first current GUI attempt is retained in sibling `installed-foreground/`: published UI 6/7, crash-log timeout, app alive. Its trace owned the target before clicking but afterward reported a distant pointer position over a gclo process. The owner then reserved the desktop; the unchanged fixture passed the complete run. This supports desktop input interference for that observed failure, without proving every earlier timeout had the same cause. Completed older guarded-with-cli evidence moved intact to `C:/Users/james/.cache/AppKit-retained-fixtures/2026-10-10/guarded-with-cli` with all seven TRX reports; no evidence deleted. Foundation AppKit `bbf7efd` freshly passes locked restore, zero-warning full build, format verification, 161 unit tests/100% core-update coverage, 14 WinUI/WPF UI tests, seven review-validator tests and ESLint. Current exact-commit review and rollout packets are prepared. Two additional signed shared-rollout commits (helper `3334d02`, builder `5887a83`) start from published standards v1.0.0; 35 tests and workflow/docs/hooks pass. Thirty signed local preparation commits total; original checkouts are preserved. Remaining criteria stay open: actual hosted gates/review bootstrap, public starter/package/feed rollout, AppKit's live check/apply integration, final Azure identity/role/resource/signature proof, owner badge attestations and age reassessment. Offline GitHub transport is not hosted or signing evidence. No push, PR, merge, new release, live settings change or Azure retry occurred.
KofTwentyTwo commented 2026-10-10 22:55:34 +00:00 (Migrated from github.com)
Copy link
Copy source

The authorized topic branches are now pushed and draft PRs are open:

Shared signing run 38093017631 completed successfully, including Windows signing tests, conformance, docs, CodeQL, security and PR gates. These are preparation tests, not proof of Azure authentication or real signatures.

AppKit's initial hosted run passed build-test, UI, JavaScript and security checks. It exposed a pinned analyzer recursive-analysis crash and uri-js development-license policy rejection, now tracked in #26. A signed, reviewed correction checks all nine PowerShell files separately with unchanged rules; all pass locally, and current-head hosted validation is running. The license failure remains enforced pending a recorded policy exception.

Both PRs remain drafts. Owner review acknowledgement, review-gate/settings bootstrap, shared publication/consumer adoption, public starter rollout and actual AppKit signing remain required where applicable. Push/draft approval did not authorize merge, release, repository creation, settings or Azure login retry.

The authorized topic branches are now pushed and draft PRs are open: - AppKit #25: https://github.com/KofTwentyTwo/AppKit/pull/25 (current signed head 09f9e0777e14043403de350477097ec212cbe61a) - Shared signing #31: https://github.com/KofTwentyTwo/standards/pull/31 (5887a839b23a405aa6b8148af61361e19da07643) Shared signing run 38093017631 completed successfully, including Windows signing tests, conformance, docs, CodeQL, security and PR gates. These are preparation tests, not proof of Azure authentication or real signatures. AppKit's initial hosted run passed build-test, UI, JavaScript and security checks. It exposed a pinned analyzer recursive-analysis crash and uri-js development-license policy rejection, now tracked in #26. A signed, reviewed correction checks all nine PowerShell files separately with unchanged rules; all pass locally, and current-head hosted validation is running. The license failure remains enforced pending a recorded policy exception. Both PRs remain drafts. Owner review acknowledgement, review-gate/settings bootstrap, shared publication/consumer adoption, public starter rollout and actual AppKit signing remain required where applicable. Push/draft approval did not authorize merge, release, repository creation, settings or Azure login retry.
KofTwentyTwo commented 2026-10-10 23:02:38 +00:00 (Migrated from github.com)
Copy link
Copy source

Final hosted checkpoint:

  • AppKit draft #25, head 09f9e0777e: build-test, format, WinUI/WPF UI, PowerShell (40/40), JavaScript/review tests, title/DCO, security and all three CodeQL language checks succeed. CodeQL run 38093181044 is completed SUCCESS. The only failed check is dependency-review's uri-js tooling-license policy rejection.
  • Shared signing draft #31, head 5887a83: run 38093017631 completed SUCCESS, all applicable checks.
  • Proposed tooling-license draft #32, head cd20e94: run 38093461441 completed SUCCESS, all applicable checks.

No CI job is still pending. License-policy acceptance remains unresolved: EX-0009 is Proposed, not Open/approved, and no caller exemption is enabled. Both the exact-version exception and any eventual caller correction need the normal reviewed process and updated current-head acknowledgement. No gate was weakened to obtain these results.

All three branches were pushed with explicit approval and remain drafts. No merge, release, starter creation/push, settings or Azure mutation/login retry occurred. Hosted results do not prove actual AppKit Azure signing, production feeds or full standards compliance. Scoped implementation/tests are verified; broader acceptance tickets remain open.

Final hosted checkpoint: - AppKit draft #25, head 09f9e0777e14043403de350477097ec212cbe61a: build-test, format, WinUI/WPF UI, PowerShell (40/40), JavaScript/review tests, title/DCO, security and all three CodeQL language checks succeed. CodeQL run 38093181044 is completed SUCCESS. The only failed check is dependency-review's uri-js tooling-license policy rejection. - Shared signing draft #31, head 5887a83: run 38093017631 completed SUCCESS, all applicable checks. - Proposed tooling-license draft #32, head cd20e94: run 38093461441 completed SUCCESS, all applicable checks. No CI job is still pending. License-policy acceptance remains unresolved: EX-0009 is Proposed, not Open/approved, and no caller exemption is enabled. Both the exact-version exception and any eventual caller correction need the normal reviewed process and updated current-head acknowledgement. No gate was weakened to obtain these results. All three branches were pushed with explicit approval and remain drafts. No merge, release, starter creation/push, settings or Azure mutation/login retry occurred. Hosted results do not prove actual AppKit Azure signing, production feeds or full standards compliance. Scoped implementation/tests are verified; broader acceptance tickets remain open.
KofTwentyTwo commented 2026-10-10 23:14:29 +00:00 (Migrated from github.com)
Copy link
Copy source

Committed starter d8cea35cdf971ae327d69adc7ab222a1e7d891e3 (signed/DCO): the bootstrap plan now requires GitHub's actual standalone job names installed-updates, powershell and javascript; the template source additionally requires template. Generated apps omit that source-only packaging gate.

A new regression reads standalone job names from the actual ci.yml/scripts.yml workflows. It failed against the old plan (13 passed, one failed), then passed after correction. The source and both renamed, custom-owner variants generated from the real packed template each pass all 41 script tests. No manual synchronization of generated files. Source/generated workflow syntax and offline security, docs, Node seven-case review tests/ESLint and applicable commit hooks pass. Generated policies contain 16 actual contexts; source has 17.

Propagated AppKit's full-rule file-by-file analyzer workflow. Individual source/generated checks pass, but the pinned analyzer still occasionally crashes internally before emitting findings; file-by-file execution is not a proven complete cure. No rule/error suppression or retry wrapper is added. #26 remains open for that tool stability and license acceptance. Earlier complete installed runtime evidence covers unchanged UI/application code; this commit changes only administration/tests/docs and the analysis job.

Live disposable-repository setup and hosted starter gates still require public rollout/settings authorization. #10 remains open against that deployed acceptance requirement. Original sibling checkout is preserved; starter topic branch has no origin and has not been pushed.

Committed starter d8cea35cdf971ae327d69adc7ab222a1e7d891e3 (signed/DCO): the bootstrap plan now requires GitHub's actual standalone job names installed-updates, powershell and javascript; the template source additionally requires template. Generated apps omit that source-only packaging gate. A new regression reads standalone job names from the actual ci.yml/scripts.yml workflows. It failed against the old plan (13 passed, one failed), then passed after correction. The source and both renamed, custom-owner variants generated from the real packed template each pass all 41 script tests. No manual synchronization of generated files. Source/generated workflow syntax and offline security, docs, Node seven-case review tests/ESLint and applicable commit hooks pass. Generated policies contain 16 actual contexts; source has 17. Propagated AppKit's full-rule file-by-file analyzer workflow. Individual source/generated checks pass, but the pinned analyzer still occasionally crashes internally before emitting findings; file-by-file execution is not a proven complete cure. No rule/error suppression or retry wrapper is added. #26 remains open for that tool stability and license acceptance. Earlier complete installed runtime evidence covers unchanged UI/application code; this commit changes only administration/tests/docs and the analysis job. Live disposable-repository setup and hosted starter gates still require public rollout/settings authorization. #10 remains open against that deployed acceptance requirement. Original sibling checkout is preserved; starter topic branch has no origin and has not been pushed.
KofTwentyTwo commented 2026-10-10 23:23:01 +00:00 (Migrated from github.com)
Copy link
Copy source

Progress at signed starter commit c2b7b8c8c2c1e5007079907ca3c4f50735f52576:

  • The installed probe now calls the shipped AppKit 0.1.0 public CheckAsync and DownloadAndApplyAsync methods. Previously it called Velopack directly for those operations.
  • Only the HTTP downloader is replaced in test code. The actual AppKit backend, Velopack manager/locator, installed channel and entry-assembly prerelease selection remain intact. The pinned private-symbol adapter fails closed if attachment fails; no production API change or network fallback.
  • Evidence records public check errors, apply calls and target asset requests before apply exits. Existing target-manifest, exact application SHA256, restarted-window, byte-preservation and UI requirements remain enforced.
  • Source and both actual packed/renamed CLI and GUI-only probes build with zero warnings and produce the correct unsupported loose-build result with zero network requests. Probe format verification, harness full-rule analysis and 41/41 starter script tests pass. Signed/DCO commit hooks pass.
  • Fresh CLI full installed acceptance is running on the owner-reserved desktop; GUI-only acceptance follows sequentially. These results are pending. Existing complete tests exercised the earlier Velopack-direct probe and do not establish this new public AppKit path.

No closure or production-signing/public-feed claim. AppKit draft #25 still passes all hosted checks except uri-js license policy; shared drafts #31/#32 pass their applicable checks. Azure access remains deferred and no merge/publication/settings change is authorized.

Progress at signed starter commit c2b7b8c8c2c1e5007079907ca3c4f50735f52576: - The installed probe now calls the shipped AppKit 0.1.0 public `CheckAsync` and `DownloadAndApplyAsync` methods. Previously it called Velopack directly for those operations. - Only the HTTP downloader is replaced in test code. The actual AppKit backend, Velopack manager/locator, installed channel and entry-assembly prerelease selection remain intact. The pinned private-symbol adapter fails closed if attachment fails; no production API change or network fallback. - Evidence records public check errors, apply calls and target asset requests before apply exits. Existing target-manifest, exact application SHA256, restarted-window, byte-preservation and UI requirements remain enforced. - Source and both actual packed/renamed CLI and GUI-only probes build with zero warnings and produce the correct unsupported loose-build result with zero network requests. Probe format verification, harness full-rule analysis and 41/41 starter script tests pass. Signed/DCO commit hooks pass. - Fresh CLI full installed acceptance is running on the owner-reserved desktop; GUI-only acceptance follows sequentially. These results are pending. Existing complete tests exercised the earlier Velopack-direct probe and do not establish this new public AppKit path. No closure or production-signing/public-feed claim. AppKit draft #25 still passes all hosted checks except uri-js license policy; shared drafts #31/#32 pass their applicable checks. Azure access remains deferred and no merge/publication/settings change is authorized.
KofTwentyTwo commented 2026-10-10 23:28:06 +00:00 (Migrated from github.com)
Copy link
Copy source

Follow-up at signed starter commit e93f7ca9a5602355b5ac37d02313326f10227109:

The first fresh CLI acceptance stopped before installation because the harness required a space after the version, accidentally requiring SourceLink metadata. The valid output outside a Git checkout was Public API true 0.1.0. Fixed the assertion to require the complete version token at line end with optional parenthesized metadata. The old assertion fails the retained no-metadata regression; the fixed suite passes 46/46 with zero failures/skips. Incorrect/extended version tokens still fail. Original failed fixture/logs remain retained; a fresh final CLI template is generated for sequential acceptance after the GUI run.

Analyzer limitation: captured an actual PSScriptAnalyzer 1.25.0 / PowerShell 7.6.6 exception in CommandInfo.get_Parameters called by UseCorrectCasing.AnalyzeScript. The pinned upstream rule source has a runspace-affinity fallback for InvalidOperationException; our captured exception is NullReferenceException. This narrows the failure but does not establish its complete cause or a cure. Pre-initializing command metadata did not prevent it. Failed diagnostic processes were scoped and stopped; no CI retry, disabled rule or suppressed error. The initial public-probe harness analysis passed before this follow-up; current changed-script full-rule analysis remains unverified because of the engine crash.

GUI-only acceptance is running on the reserved desktop and has passed the first three 532-file portable/full byte gates. Public AppKit installed check/apply outcomes and final UI results remain pending. No issue closure, merge, release, Azure retry or live setting change.

Follow-up at signed starter commit e93f7ca9a5602355b5ac37d02313326f10227109: The first fresh CLI acceptance stopped before installation because the harness required a space after the version, accidentally requiring SourceLink metadata. The valid output outside a Git checkout was `Public API true 0.1.0`. Fixed the assertion to require the complete version token at line end with optional parenthesized metadata. The old assertion fails the retained no-metadata regression; the fixed suite passes 46/46 with zero failures/skips. Incorrect/extended version tokens still fail. Original failed fixture/logs remain retained; a fresh final CLI template is generated for sequential acceptance after the GUI run. Analyzer limitation: captured an actual PSScriptAnalyzer 1.25.0 / PowerShell 7.6.6 exception in `CommandInfo.get_Parameters` called by `UseCorrectCasing.AnalyzeScript`. The pinned [upstream rule source](https://github.com/PowerShell/PSScriptAnalyzer/blob/1.25.0/Rules/UseCorrectCasing.cs) has a runspace-affinity fallback for InvalidOperationException; our captured exception is NullReferenceException. This narrows the failure but does not establish its complete cause or a cure. Pre-initializing command metadata did not prevent it. Failed diagnostic processes were scoped and stopped; no CI retry, disabled rule or suppressed error. The initial public-probe harness analysis passed before this follow-up; current changed-script full-rule analysis remains unverified because of the engine crash. GUI-only acceptance is running on the reserved desktop and has passed the first three 532-file portable/full byte gates. Public AppKit installed check/apply outcomes and final UI results remain pending. No issue closure, merge, release, Azure retry or live setting change.
KofTwentyTwo commented 2026-10-10 23:34:52 +00:00 (Migrated from github.com)
Copy link
Copy source

Completed fresh public AppKit installed acceptance for both actual packed template variants:

Variant Published UI Installed stable UI Installed dev UI Updates
GUI-only 7/7 6/6 6/6 AppKit stable 0.1.0 -> 0.4.0; dev beta.1 -> beta.2
CLI 7/7 6/6 6/6 AppKit stable 0.1.0 -> 0.4.0; dev beta.1 -> beta.2

The real shipped AppKit 0.1.0 public CheckAsync and DownloadAndApplyAsync drive these upgrades. Only offline transport is injected; actual backend/manager/locator/channel selection remains intact. Both results record successful public checks, apply calls, the target full-package URL, exact installed application SHA256, target manifest, a restarted window, and no remaining update offer. Stable/dev requests stay isolated. Both portable and full archives preserve all 532 original non-PDB publish files for each of four versions. Loose-build rejection and portable behavior pass. Both installations and each unique uninstall registry entry are confirmed removed.

Retained evidence is in ~/.cache/AppKit-acceptance/2026-10-10/{public-api-false,public-api-final-cli}/artifacts/installed-public-appkit: results.json, three passing TRX files each, channel before/after JSON, installer/process logs and package byte evidence. GUI runtime source is c2b7b8c; CLI uses e93f7ca. Current signed starter head 49df4902d91d8e4c5e8f29cce9b4f6a2ba5c1a74 adds only the updated acceptance guide after those runtime tests. Source and final packed/renamed CLI script suites pass 46/46. Original metadata-free CLI failure and regression evidence remain retained.

Desktop reservation has ended. No build/test process remains intentionally active.

Remaining limits: this proves offline public AppKit service integration, not a public GitHub release feed, interactive update-dialog check/apply, hosted starter CI, production Authenticode signing, deltas or non-x64 runtimes. No broad issue closure or complete compliance claim.

The analyzer exception is now matched to the still-open upstream PSScriptAnalyzer #1708. Latest published release is still 1.25.0. Current follow-up script analysis remains unverified; no error suppression, disabled rule or retry gate was introduced. AppKit #25 remains green except the enforced license policy; standards #31/#32 are green, and EX-0009 remains Proposed. Azure retry stays deferred; no merge/publication/settings/Azure change.

Completed fresh public AppKit installed acceptance for both actual packed template variants: | Variant | Published UI | Installed stable UI | Installed dev UI | Updates | | --- | --- | --- | --- | --- | | GUI-only | 7/7 | 6/6 | 6/6 | AppKit stable 0.1.0 -> 0.4.0; dev beta.1 -> beta.2 | | CLI | 7/7 | 6/6 | 6/6 | AppKit stable 0.1.0 -> 0.4.0; dev beta.1 -> beta.2 | The real shipped AppKit 0.1.0 public `CheckAsync` and `DownloadAndApplyAsync` drive these upgrades. Only offline transport is injected; actual backend/manager/locator/channel selection remains intact. Both results record successful public checks, apply calls, the target full-package URL, exact installed application SHA256, target manifest, a restarted window, and no remaining update offer. Stable/dev requests stay isolated. Both portable and full archives preserve all 532 original non-PDB publish files for each of four versions. Loose-build rejection and portable behavior pass. Both installations and each unique uninstall registry entry are confirmed removed. Retained evidence is in `~/.cache/AppKit-acceptance/2026-10-10/{public-api-false,public-api-final-cli}/artifacts/installed-public-appkit`: results.json, three passing TRX files each, channel before/after JSON, installer/process logs and package byte evidence. GUI runtime source is c2b7b8c; CLI uses e93f7ca. Current signed starter head 49df4902d91d8e4c5e8f29cce9b4f6a2ba5c1a74 adds only the updated acceptance guide after those runtime tests. Source and final packed/renamed CLI script suites pass 46/46. Original metadata-free CLI failure and regression evidence remain retained. Desktop reservation has ended. No build/test process remains intentionally active. Remaining limits: this proves offline public AppKit service integration, not a public GitHub release feed, interactive update-dialog check/apply, hosted starter CI, production Authenticode signing, deltas or non-x64 runtimes. No broad issue closure or complete compliance claim. The analyzer exception is now matched to the still-open upstream [PSScriptAnalyzer #1708](https://github.com/PowerShell/PSScriptAnalyzer/issues/1708). Latest published release is still 1.25.0. Current follow-up script analysis remains unverified; no error suppression, disabled rule or retry gate was introduced. AppKit #25 remains green except the enforced license policy; standards #31/#32 are green, and EX-0009 remains Proposed. Azure retry stays deferred; no merge/publication/settings/Azure change.
KofTwentyTwo commented 2026-10-10 23:46:51 +00:00 (Migrated from github.com)
Copy link
Copy source

Completed the focused onboarding fix in signed/DCO starter commit bb310f3208c9e4203ad42c007bf1671933a843be (local fix/template-onboarding; not published).

Apply and read-only Validate now resolve the official GitHub Actions app and require its ID on every required context. Missing/wrong bindings and another bootstrap producer fail before writes. The reviewed caller plan stays unchanged and reusable. Existing conflicting rules are preserved.

Evidence: retained RED reproduces wrong/missing bindings and input mutation (3 failures); full source and both actual packed/generated CLI and GUI-only variants each pass 54/54 Pester cases, zero failures/skips. Both changed PowerShell files pass the configured full analyzer rules; both docs pass Markdown lint; diff checks and signed-commit hooks pass. The generated-test processes ended exit 0. Official app lookup was read-only (github-actions, owner github, ID 15368).

This proves the local tool behavior, not a live repository bootstrap. No GitHub settings were changed and the starter has no public remote. Live apply/readback, whole-starter review, owner acknowledgement and publication remain outstanding. No release/signing claim or broad issue closure.

Completed the focused onboarding fix in signed/DCO starter commit bb310f3208c9e4203ad42c007bf1671933a843be (local fix/template-onboarding; not published). Apply and read-only Validate now resolve the official GitHub Actions app and require its ID on every required context. Missing/wrong bindings and another bootstrap producer fail before writes. The reviewed caller plan stays unchanged and reusable. Existing conflicting rules are preserved. Evidence: retained RED reproduces wrong/missing bindings and input mutation (3 failures); full source and both actual packed/generated CLI and GUI-only variants each pass 54/54 Pester cases, zero failures/skips. Both changed PowerShell files pass the configured full analyzer rules; both docs pass Markdown lint; diff checks and signed-commit hooks pass. The generated-test processes ended exit 0. Official app lookup was read-only (github-actions, owner github, ID 15368). This proves the local tool behavior, not a live repository bootstrap. No GitHub settings were changed and the starter has no public remote. Live apply/readback, whole-starter review, owner acknowledgement and publication remain outstanding. No release/signing claim or broad issue closure.
KofTwentyTwo commented 2026-10-11 00:06:06 +00:00 (Migrated from github.com)
Copy link
Copy source

New publication/setup evidence under the owner's explicit commit/push/configure authorization:

  • Created public KofTwentyTwo/windows-app-template, initial main bb310f3 and signed onboarding topic now 758e773. Draft PR #1: https://github.com/KofTwentyTwo/windows-app-template/pull/1.
  • Marked as a template; applied 13 restrictive repository/security/Actions/environment/ruleset requests. Official GitHub Actions producer IDs bind all 17 required contexts. Read-only Validate returned SettingsVerified=true; release allows only v* tags; NUGET_USER is set to KofTwentyTwo.
  • Hosted initial-main CI run 38096509791 passed build/core coverage, format, UI, actual template generation and installed stable/dev updates. PR fac10a7 CI 38096578936 also completed SUCCESS. Current 758e773 scripts run 38097053573 passes.
  • Live selected-actions policy initially rejected the two digest-pinned scanner containers. Fixed the plan/tests/guide in 758e773 and configured only the exact published Gitleaks/Trivy references. Source and generated Windows application each pass 55/55 script cases; changed files pass full analyzer rules, guide lint and signed hooks. Current security run 38097053934 and dispatch 38097129462 succeed, all three security jobs. Earlier startup failures retained; no policy broadening to arbitrary containers.

The required-check readback defect (#27) is implemented and published on starter main; its scoped acceptance is complete. Broader #10/#20 acceptance still includes owner review acknowledgement, remaining hosted bootstrap/negative-PR evidence, inventory and publication conditions. No merge, tag/release, NuGet template publication, signing proof or claim of full standards compliance.

The owner explicitly cleared the old all-AppKit-issues goal and set a new goal: build MarkdownViewr.Windows using AppKit. The new public GUI-only scaffold is at https://github.com/KofTwentyTwo/MarkdownViewr.Windows; its build has zero warnings, 20 core tests pass at 100% coverage and the feature plan is recorded. Its greeting remains scaffold content, not a finished Markdown viewer. Azure retries remain deferred.

New publication/setup evidence under the owner's explicit commit/push/configure authorization: - Created public KofTwentyTwo/windows-app-template, initial main bb310f3 and signed onboarding topic now 758e773. Draft PR #1: https://github.com/KofTwentyTwo/windows-app-template/pull/1. - Marked as a template; applied 13 restrictive repository/security/Actions/environment/ruleset requests. Official GitHub Actions producer IDs bind all 17 required contexts. Read-only Validate returned SettingsVerified=true; release allows only v* tags; NUGET_USER is set to KofTwentyTwo. - Hosted initial-main CI run 38096509791 passed build/core coverage, format, UI, actual template generation and installed stable/dev updates. PR fac10a7 CI 38096578936 also completed SUCCESS. Current 758e773 scripts run 38097053573 passes. - Live selected-actions policy initially rejected the two digest-pinned scanner containers. Fixed the plan/tests/guide in 758e773 and configured only the exact published Gitleaks/Trivy references. Source and generated Windows application each pass 55/55 script cases; changed files pass full analyzer rules, guide lint and signed hooks. Current security run 38097053934 and dispatch 38097129462 succeed, all three security jobs. Earlier startup failures retained; no policy broadening to arbitrary containers. The required-check readback defect (#27) is implemented and published on starter main; its scoped acceptance is complete. Broader #10/#20 acceptance still includes owner review acknowledgement, remaining hosted bootstrap/negative-PR evidence, inventory and publication conditions. No merge, tag/release, NuGet template publication, signing proof or claim of full standards compliance. The owner explicitly cleared the old all-AppKit-issues goal and set a new goal: build MarkdownViewr.Windows using AppKit. The new public GUI-only scaffold is at https://github.com/KofTwentyTwo/MarkdownViewr.Windows; its build has zero warnings, 20 core tests pass at 100% coverage and the feature plan is recorded. Its greeting remains scaffold content, not a finished Markdown viewer. Azure retries remain deferred.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
accessibility
Barrier affecting people with disabilities
 bug
Something isn't working
 deferred
Agreed follow-up, unscheduled
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 needs-owner
Blocked on the owner
 priority
Work this first
 quality
Tests, gates, and code quality
 question
Further information is requested
 refactor
Internal restructuring, no behavior change
 release
Release and packaging
 wontfix
This will not be worked on
No labels quality
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/AppKit#20