OEL
/
NTFSSecurity
mirror of https://github.com/raandree/NTFSSecurity
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
103 Commits
6 Branches
10 Tags
12 MiB
 
 
Tree: 14799fb465
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '14799fb465'
${ noResults }
NTFSSecurity/.memory-bank/activeContext.md

1.6 KiB
Raw Blame History

status last-verified owner source
current 2026-10-02 active-agent current task evidence

Active context

Current focus

Work packages 1 and 2 are pushed; the maintainer opens their PRs: ai/housekeeping into master, and ai/ship-help into ai/housekeeping. The work packages and their order are in progress.md.

Evidence

  • AppVeyor 54834155 (ai/housekeeping, 74abb0b) passed. AppVeyor 54834154 (ai/ship-help, fba3a7d) passed all four test_script steps; Pester passed 218 of 218 tests in Windows PowerShell 5.1, including the Get-Help -Online tests.
  • The same build listed 870 tests on the Tests tab: the NUnit import files each Pester 5 test under every enclosing block (Pester, file, Describe, Context), so 216 tests appear four times and 2 three times. The follow-up commit on ai/ship-help reports the results through the build worker API instead (POST api/tests/batch), one entry per test; a local run of step 04 against a sample test file sent 11 entries for 11 tests.
  • The AppVeyor job log API returns application/octet-stream; decode the bytes as UTF-8 before searching it.
  • Merging work package 1 with a merge commit keeps ai/ship-help valid; after a squash merge it needs git rebase --onto origin/master ai/housekeeping ai/ship-help.
  • PR descriptions for both work packages are in the session folder (files/pr), outside the repository.

Next step

The maintainer pushes the follow-up commit on ai/ship-help, opens both PRs, and checks that AppVeyor lists 218 tests; then work package 3 (Read the Docs).