diff --git a/.memory-bank/activeContext.md b/.memory-bank/activeContext.md index c0ca8f4..ae5df9a 100644 --- a/.memory-bank/activeContext.md +++ b/.memory-bank/activeContext.md @@ -9,7 +9,7 @@ source: current task evidence ## Current focus -State at 2026-10-20 12:40 UTC: 5.0.0-rc8 is published and accepted. The +State at 2026-10-20 14:55 UTC: 5.0.0-rc8 is published and accepted. The maintainer merged #126 (the decisions of 2026-10-19) and #127 (`c719197`: the fix of the false "no access" of `Get-NTFSEffectiveAccess`, the known limit of the hard-link cmdlets in the pages and the CHANGELOG, and the label `rc8`) and @@ -20,10 +20,12 @@ passed. The lab acceptance of the published bytes passed in one detached driver six machine classes, the first lab 245/0/1 per edition, every end state CLEAN (record `Tests/Lab/Acceptance-2026-10-20-published-rc8.md`, #128). The boundary of the new error, a computer name of 32,718 characters, holds on Server 2019, -2022, 2025, and Windows 11 26H1. Open before the stable pull request: the -tests-only round for the plain gaps (until 2026-11-02), the maintainer's #34 -decision on that date (no reply to his follow-up of 2026-10-19), and his check -of `PSGALLERY_API_KEY`. The stable build is new bytes that no lab has run; the +2022, 2025, and Windows 11 26H1. The tests-only round for the plain gaps ran +the same afternoon (Next step 6; branch `ai/tests-round-1`, not pushed). Open +before the stable pull request: its pull request and the CI on the runner, the +maintainer's #34 decision on 2026-11-02 (no reply to his follow-up of +2026-10-19), and his check of `PSGALLERY_API_KEY`. The stable build is new +bytes that no lab has run; the procedure accepts the last prerelease, so the stable change touches only the label, the CHANGELOG, and `$publishedVersions`. Any other product change needs rc9 and the same acceptance, about 70 minutes with the chain script. @@ -180,12 +182,15 @@ Decisions 22 and 24 on 2026-10-19 and decides 23 on 2026-11-02. about a domain account still gets "Access is denied". 6. Handoff 5 is done and merged (Evidence). Decided on 2026-10-19 (Decision 21): the hard-link names under another root stay a known limit; the pages - and the CHANGELOG say so since rc8. The plain test items (68 `budget` - mentions in the 57 sets that are not closed) are closed in a tests-only - round until 2026-11-02: four implementers, one per `ParameterSets.*` test - file, work in worktrees from `master`; their commits go into one branch - with the report and the ParameterSets table updated, and what is left is - listed. A defect that a test finds needs his decision and rc9. Still his: the - silent default scope for a piped `AppliesTo` that PowerShell cannot convert - (a design change), the 8 getters of pipeline parameters, and the audit paths. + and the CHANGELOG say so since rc8. The tests-only round for the plain items + (68 `budget` mentions) ran on 2026-10-20: four implementers, one + `ParameterSets.*` file each, integrated on `ai/tests-round-1` (`d28c7a0`, not + pushed): 89 `It` blocks, 121 cases, the suite 1,494 to 1,615 per + configuration, 0 failed; 38 of 64 sets closed, 26 with a leftover (16 + Limit, 7 MaintainerDecision, 3 would-pin), no defect; report + `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`. The GitHub runner + has not run the tests yet. A defect that a test finds needs his decision and + rc9. Still his: the silent default scope for a piped `AppliesTo` that + PowerShell cannot convert (a design change), the 8 getters of pipeline + parameters, and the audit paths. 7. Do not release stable 5.0.0 or equate a percentage with gate closure. diff --git a/.memory-bank/debugging-insights.md b/.memory-bank/debugging-insights.md index 8fa93c5..053c132 100644 --- a/.memory-bank/debugging-insights.md +++ b/.memory-bank/debugging-insights.md @@ -2,7 +2,7 @@ status: current last-verified: 2026-10-20 owner: software-engineer -source: Handoff 5 (the coverage unknowns) and the rc8 fix: probes, red and green runs, and the independent reviews +source: Handoff 5 (the coverage unknowns), the rc8 fix, and the tests-only round: probes, red and green runs, and the independent reviews --- # Debugging insights @@ -115,3 +115,16 @@ fails without it (Decision 16). !OperationFailed`); the tests assert its absence next to the error. - A word in the CHANGELOG is a claim: "an overlong name" suggested 256 characters, where 1722 still falls back. The entry names the probed length. + +## A helper that waits for a child that never started + +- The helper that ran a test file in the four CI configurations passed the + Pester name filter to the basic-user run through `runas /trustlevel:0x20000 + "…"`. A filter with spaces (`*treat a path with brackets*`) broke the nested + quotes, the child never started, and the helper waited for its whole timeout + (30 minutes). An implementer blamed the load of four agents at once; a call + alone with the same spaced filter showed the helper. +- The filter now travels as base64 (`-FullNameBase64`), and a basic-user run + gives up after 60 seconds when its runner never started (about 6 seconds + normally). Before you blame the load for a stall, repeat the call alone with + the same arguments. diff --git a/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md b/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md index 5897cc8..20cfbb4 100644 --- a/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md +++ b/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md @@ -78,8 +78,14 @@ check, three matrix cells 1,374/0/12, the suite in 24 runs, the first lab `Tests/Lab/Acceptance-2026-10-20-published-rc8.md`). The fix of the swallowed initialization errors went in with a review (one Minor, the warning before the error, fixed), and the hard-link known limit is in the pages and the -CHANGELOG. The exit criterion "matrix on published bytes" is met for rc8; open -are the tests-only round (until 2026-11-02), #34 (2026-11-02), and the key -check. The stable build is new bytes: the stable change may touch only the +CHANGELOG. The exit criterion "matrix on published bytes" is met for rc8. The +tests-only round ran the same afternoon (report +`Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`): 89 `It` blocks, 121 +cases, the suite 1,494 to 1,615 per configuration with no failure, 38 of 64 +parameter sets closed, 26 with a leftover (16 Limit, 7 MaintainerDecision, 3 +would-pin), no defect. It is on `ai/tests-round-1` and has not run on the +GitHub runner. Open are that pull request, the leftovers until 2026-11-02, #34 +(2026-11-02), and the key check. The stable build is new bytes: the stable +change may touch only the label, the CHANGELOG, and `$publishedVersions`; any other product change needs rc9 and the same acceptance. diff --git a/.memory-bank/progress.md b/.memory-bank/progress.md index a2791fc..5a0f0b2 100644 --- a/.memory-bank/progress.md +++ b/.memory-bank/progress.md @@ -129,8 +129,13 @@ After 5.0.0, archive in favor of WindowsAccessControl (Decision 18). configuration); the first lab 245/0/1 per edition; every end state CLEAN. A probe on four operating systems showed the boundary of the new error (a name of 32,718 characters). Record - `Tests/Lab/Acceptance-2026-10-20-published-rc8.md` (#128). The tests-only - round for the plain gaps started the same day. + `Tests/Lab/Acceptance-2026-10-20-published-rc8.md` (#128). +- 2026-10-20: tests-only round (Decision 21). Four implementers, one + `ParameterSets.*` test file each; integrated on `ai/tests-round-1` + (`d28c7a0`, not pushed): 89 `It` blocks, 121 cases, the suite 1,494 to 1,615 + per configuration, 0 failed in four configurations; 38 of 64 sets closed (7 + before), 26 with a leftover (16 Limit, 7 MaintainerDecision, 3 would-pin); no + defect. Report: `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`. ## Stable capabilities @@ -145,8 +150,9 @@ After 5.0.0, archive in favor of WindowsAccessControl (Decision 18). 1. Decision 21 gate: the published rc7 and rc8 are accepted in the matrix and the first lab (records); stable follows rc8 (Decision 21, "Closing the - gate"). Do not release 5.0.0 until the other gates close: the tests-only - round, #34 on 2026-11-02, and the key check. Release steps: + gate"). Do not release 5.0.0 until the other gates close: the tests PR (CI + on the runner) and the rest of the plain gaps, #34 on 2026-11-02, and the + key check. Release steps: `Docs/Contributing/05-Releasing.md`; remove the prerelease label, date `[5.0.0]`, add the last prerelease (rc8) to `$publishedVersions` (never the version of the manifest), tag through CI.