11 KiB

Raw Blame History

status	last-verified	owner	source
current	2026-10-09	active-agent	repository and validation evidence

Progress

Current status

5.0.0-rc6 is published on the Gallery and GitHub; its failed Release job recovered in attempt 2 on 2026-10-09. #116 (rc7, d25647d, base master) is open and green, not merged or published. Further quality-gate work is ai/quality-gate-coverage (#117) and ai/quality-gate-paths (draft #118), which classifies every remaining unvisited path; the open items are the maintainer's decisions. The local branch ai/quality-gate-lab-matrix (stacked on #118, not pushed) holds the operating-system matrix, three fixes of the module found by it, and the controller changes (Decision 24, proposed). Stable Gallery version: 4.2.6. After 5.0.0, archive in favor of WindowsAccessControl (Decision 18).

Recent milestones

2026-10-02 to 2026-10-06: documentation/help aligned with source, CI and wiki moved to GitHub Actions, versioning/release automation established, and prereleases rc1 to rc4 published. Earlier detail is in git, CHANGELOG.md, Docs/Version-History.md, and Decisions 1 to 19.
2026-10-07: lab comparison of rc2/rc4 reproduced #34 over SMB and proved changed-section writes preserve the owner. Remote effective-access fallback returned no result; fixed test-first for rc5 (Decision 20).
2026-10-08: #114 merged (fcb370e), rc5 published and live-tested. Decision 21 established the quality gate. Corrected four-run coverage: rc5 58.1% sequence points/38.0% branches, not the initial one-run result.
2026-10-08: rc6 Phase 2 added basic-user CI, parameter-set/error tests, expanded domain/SMB cases, and fixes for privilege cleanup, path resolution, ownership retries, item conflicts, output equality, and inherited flags. Suite: 677; coverage 68.14% sequence/44.32% branches. Lab acceptance of 7b0781f passed; two independent review passes.
2026-10-08: rc7 implemented proposed Decision 22, including breaking link binding/error changes, SimpleAccess traversal, cross-volume folder preservation, and named effective-access warnings. Suite: 712, no failures or test skipped everywhere. One review: no Blocker/Major. Lab candidate dc6e9f5: 326 passed, 2 skipped, cleanup verified.
2026-10-08: #115 merged (b51d970) and tagged rc6. Release run 37839669028 failed with HTTP 409 after Gallery publication. The log does not establish the previously assumed initial timeout/retry cause. Published rc6 live tests differed only in rc7's warning expectation.
2026-10-09: release attempt 2 succeeded; rc6 GitHub prerelease and zip appeared at 07:01:34 UTC. #116 passed CI on d25647d.
2026-10-09: autonomous follow-up on ai/quality-gate-coverage, through 3442194, adds 202 cases above rc7: deletion/owner failures, all 13 scopes, inheritance transitions, enumeration, forced replacement, descriptor failures, and offline CI recovery. Reproduced/fixed rooted result-path handling and first-hidden-item omission. Publication recovery verifies exact SHA-512 identity, not merely version existence.
2026-10-09: final uninstrumented suite: 914 per configuration, zero failures; coverage: 2,641/3,559 sequence points (74.21%) and 974/1,933 branches (50.39%), aggregate of four runs without AltCover --save. All skipped templates have executed counterparts. Mutation guards were proved and production source restored; Release build/checks pass.
2026-10-09: live comparison, 09:20 to 09:51 UTC: candidate 330 passed, zero failed, two expected skips; published rc6 four expected Hidden/ warning-text failures only. Independent cleanup probes verified fixture absence; raw host-verifier failures retained with corrected verification. Lab guards/acceptance committed in 7594e0c. One independent code review approved with no significant finding (custom model unavailable; built-in fallback). All 11 tested files match the ZIP. OS/path gates stay open.
2026-10-09: Handoff 1 on ai/quality-gate-paths (28 local commits, no push): suite 914 to 1,310 per configuration, zero failures; coverage 3,192/3,634 sequence points (87.84%), 1,273/1,978 branches; all 231 unvisited methods classified (223 explained, 8 open). Eleven defects fixed, ten with a guard that is red before the fix and green after it (a red/green matrix over ten states of the branch: 76 rows red at the base, none after the last fix), among them a later command's exception that cmdlets swallowed (a throw made Remove-Item2 remove the next item; also through the error stream) and a privilege left enabled. Nine static passes of the built-in code-review agent: no Blocker or Major. Report in Tests/Coverage.
2026-10-09: lab acceptance of those fixes, 83149ee against its base f11ff41 with the same 244 tests per edition (78 new, case 10): candidate 486 passed, 0 failed, 2 expected skips; baseline 338 passed, 148 failed, all 148 green on the candidate; fixture removed and verified clean on six machines. Record: Tests/Lab/Acceptance-2026-10-09-quality-gate-paths.md.
2026-10-09 to 10: handoffs 2 to 4 under the maintainer's delegation (decisions D1 to D46 in the night log of the session files). The matrix lab NtfsSecurityOsMatrixLab (Server 2019, 2022, and 2025 file servers, Windows 11 Enterprise 22H2 client, Windows 11 26H1 suite only) found three defects of the module, fixed in 962887a and fdd7a8b: audit inheritance by descriptor, Get-NTFSEffectiveAccess -ServerName '', and the same cmdlet for a user who isn't an administrator on a domain member. The final candidate passes the module's suite on every machine (24 runs, no failure) and the live controller in three cells (1,374 passed, 0 failed, 12 skipped) and in the first lab with case 9 (245 passed, 0 failed, 1 skipped per edition). The failures of the effective-access tests in the Server 2022 cell were not a defect of the module: in a replay of the same cells the baseline failed two of three and the final candidate one of three (not counting the warm-up cell), and one model (the remote authorization managers answer for an account name for about ten minutes after the account was created again) fits all 43 Admin-role runs of 27 cells; the Windows mechanism is unknown. The controller names the account of case 3 anew for each fixture (1dec389). A read-only built-in review of the kit and the fixes approved with Minor findings, fixed in db04ef2. A second review of the later commits found one Major (the record called the cause settled without a baseline replay), addressed by the replay, 9344ff7, and ab0d8e1; a follow-up review of those fixes found no Blocker or Major and five Minors, corrected in e2384e5 and 70f494a; a second follow-up review (the first-lab run and the cleanup changes) found no Blocker or Major and four Minors, corrected in b78784d and dbb4bd6; the built-in security-review agent found no exploitable vulnerability and two LOW items that are not changed (record, Limits). Record: Tests/Lab/Acceptance-2026-10-10-os-matrix.md; nothing was pushed.

Stable capabilities

36 cmdlets: access, audit, inheritance, owners/descriptors, privileges, long-path items, links, hash, and disk space.
Windows PowerShell 5.1 and PowerShell 7; RIPEMD160 and MACTripleDES are available only in Desktop. Both editions run elevated/basic-user in CI.
Pester fixtures use Tests/TestHelpers.psm1 TEMP sandboxes. Live tests are excluded from CI and run only on approved lab client/server targets.

Open work

Decision 21 gate: review Decision 22, integrate reviewed quality-gate follow-up, publish the next candidate, and test the published package. Do not release 5.0.0 until the remaining-path and OS-matrix gates close. Release steps: Docs/Contributing/05-Releasing.md; remove prerelease label, date [5.0.0], update $publishedVersions, tag through CI.
Issues: #110's seven items were addressed by rc6, but #115 deliberately used no closing keyword. #34 stays open for non-Windows owner feedback or maintainer acceptance. #16, #21, #45, #89 await reporters. #68 tracks ShouldProcess for security cmdlets; enhancements #22/#49/#68/#77/#87 are not planned for 5.0.0. Labels follow Decision 17.
Deferred reviews (not silently accepted): rc3 extra DACL read/SDDL snapshots/duplicate SACL check; rc4 findings listed in #113, including library-only RemoveAll account filters; rc5 unchecked Authz errors and lab-controller hardening; rc6 failed privilege-disable retry (not reproduced); rc7 audit missing-path error IDs declined in Decision 22.
Architecture/cmdlet design: Decision 22 remains proposed; two link changes are breaking. Keep unused classes/helper overloads until a maintainer decision; do not remove them to improve coverage percentages.
ARM64 workstation: PowerShell 7.6.1 crashed under x64 emulation without module frames; native-x64 CI did not reproduce it.
Optional maintainer cleanup: obsolete AppVeyor/Read the Docs access, wiki editing restrictions, test/transfer, and old lab checkpoints when no longer needed. No remote changes or snapshot restores here.
Remaining-path inventory at the final frozen commit of Handoff 1: 442 unvisited sequence points in 231 methods, all classified (Tests/Coverage): 223 explained from source with evidence, 8 open (FileSecurity conversions, RemoveAll account filters). Other open decisions: lazy path overloads, abandoned PrivilegeEnabler, dot patterns of Get-ChildItem2 -Filter, 17 owner-restore handlers that do not pass on what a later command raises (a rare combination), unused classes. An audit write's ownership retry cannot run on a local volume and is covered only by the lab. A conditional ACE display remains a .NET representation limit, not evidence of unconditional permissions.
Publication recovery is implemented locally in 95b827e, with 14 offline tests and exact artifact SHA-512 verification. Original upload errors remain errors for missing/different/unverifiable outcomes. Not deployed until the maintainer merges/pushes; no publication was performed here.
Operating-system matrix (Decision 24, proposed): the lab and the cells exist and the final local candidate passes them. Open: the acceptance of the published rc7 in every cell, keeping or replacing the VMs (about 60 GB) and the evaluation client (it shuts down every hour), which module fixes go to rc7, and a domain cell for Windows 11 26H1. #34 has no new reply since 2026-10-06.
Lab rollback evidence: new checkpoints exist but report Standard even after a successful temporary ProductionOnly probe. Classification is unresolved; original VM policy restored, no checkpoint restored. Do not represent these as verified Production snapshots.