…#181)

When --trackcomputercalls is enabled, the RegistrySessions CSV status
was incorrectly checking privSessionResult instead of registrySessionResult,
causing it to report the NetWkstaUserEnum status instead of the actual
registry enumeration result.

…h collection methods that don't enumerate computers (#182)

fix: Prevent NullReferenceException in CompStatusWriter when no status data collected

When --trackcomputercalls is used with collection methods that don't
enumerate computers (e.g., dconly), CompStatusWriter.FlushWriter() crashes
with NullReferenceException because _streamWriter is never initialized.

CreateFile() is only called when the first status object is accepted via
the BaseWriter pattern, but collection methods like dconly don't generate
any computer status messages, leaving _streamWriter as null.

Added FileCreated check in FlushWriter() to gracefully handle the no-data
case, consistent with the pattern used in JsonDataWriter.

Fixes crash when running: SharpHound.exe -c dconly --trackcomputercalls

* Revert "Revert "feat: AdminSDHolder updates - BED-6221 (#165)" (#173)"

This reverts commit 34b27df.

* fix: Use concurrent dictionary for async operations

* chore: move to AddOrUpdate for ConcurrentDictionary

---------

Co-authored-by: anemeth <[email protected]>

* chore: Adding ObjectId to CompStatus

* fix: Add ObjectID Header to CompStatusWriter

* fix: Add ObjectID Header to CompStatusWriter

* chore: update SHC version

Co-authored-by: Michael Cuomo <[email protected]>