New version: MBrassey.agtop version 2.3.9

[MBrassey]

MBrassey.agtop 2.3.9

Adds agtop, a process monitor for AI coding agents, to winget.

agtop walks /proc on Linux (sysinfo on Windows) plus the on-disk
session transcripts of Claude Code, OpenAI Codex, Block Goose,
Aider, and Google Gemini, and reports per-agent CPU, RSS, status,
current tool, in-flight subagents, token usage, estimated cost,
context-window fill, and loaded skills in a top-style TUI.

Windows-specific notes

• Writable-FD enumeration uses NtQuerySystemInformation
  (SystemExtendedHandleInformation) + DuplicateHandle +
  GetFinalPathNameByHandleW to surface what files each agent
  has open. Source: src/writing_files.rs.
• Per-process IO byte counters come from sysinfo's
  Process::disk_usage().total_*.
• Build matrix runs cargo test --release on windows-latest
  every push; the writable-FD self-test exercises the native
  path against the test process's own open file descriptor.

Source / metadata

• Upstream: https://github.com/MBrassey/agtop
• License: MIT
• Installer: portable zip from the official GitHub Release
• Architecture: x64
• SHA256 verified against the release's SHA256SUMS

Author / Manifest checklist

• I have read the contributing guide
• Manifests follow the v1.6.0 schema
• Installer URL points at the official GitHub Release
• InstallerSha256 matches the release's SHA256SUMS
• Three manifest files: version, installer, locale.en-US
• Maintainer is the upstream author

I'm the upstream maintainer (matt@brassey.io) — happy to iterate
on any review feedback.

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-140-367486-20260501-1

[stephengillie]

Manual Validation ended with:

0.2.1

(Automated response - build 1298.)

[MBrassey]

@microsoft-github-policy-service agree

[stephengillie]

Hi @MBrassey,

It seems that my validation found this PR and ran it without my knowledge. My previous response was the output of either --version or just version. This means that, while the application shows its version number as 0.2.1 instead of 2.3.9:

Manual Validation ended with:

0.2.1

(Automated response - build 1298.)

Is this expected? Should the manifest have a DisplayVersion attribute? Alternatively, could the application be updated?

[stephengillie]

I approved this in too much haste. Please feel free to respond here, or just update in the next PR.

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[MBrassey]

Thanks for the follow-up @stephengillie — no worries on the haste. Just to confirm for the record: the v2.3.9 release binary (agtop.exe from agtop-windows-x86_64.zip) does contain 2.3.9 as its version string, and agtop --version prints agtop 2.3.9 (clap derives from CARGO_PKG_VERSION, which matches the tag). I suspect the 0.2.1 came from a different invocation. Either way, a manifest for 2.4.15 is on the way which will supersede this entry.